I want to know why, when exporting a multi-tile displacement map from Mudbox, one of the tile displacement EXR is extremely under-exposed, compared to the other tile, of the two tiles I exported ?
I ran the OpenEXR EXRDisplay utility in hopes I could fix the exposure, but the utility failed, even after adjusting the exposure in within the tool, it did not increase the exposure.
are baking 16bit EXRs..?
have you tested them with sculpt mesh with map in mud..?
normalize to search distance turned off.?
Check the normals. It think if they are longer in one region then the maps will differ even if the geo looks the same.
Also, please let us know how to reproduce this issue.
In my case, the color/exposure of the map on the UV that is in the 0-1 space is the same as the UV islands that are out.
Can you send a sample Maya scene with it's UVs to the case you logged with us.
I'll be glad to test that in Mudbox.
I can send the scene. Tile 1_2 when viewed in Photoshop levels is under exposed, Tile 0_1 could be better but it's not as extreme as Tile 1_2.
could you import the dispmaps as diffuse layer in mudbox and show us some images...
I had to exaggerated the color in Mudbox otherwise you would see nothing.
Tile 1
Tile 2
looks strange yes...
but if you say sulpt using disp is working fine... than it should be fine...
if the naming conventions are right... like texturename_u1_v1 and texturename_u2_v1
mudbox will read both uv tiles...
Hi.
these are my tests with your scene, previewed with the Softimage flipbook [my preferred viewer]
The 32bit ones are consistent, but they are both darker and the details seem to be on the red channel.
As for the darker .32bit with details in red...
I don't know if this is a previewing issue (also nothing logged on the issue),
it's possible that the 32bit data would get picked up corrrectly from the displacement inside the renderer.
These are 16bit .exr(FP):
These are 32 bit.exr(FP)
Hi.
The question here is that when the displacement is applied inside a 3D program [that can properly parse the 32bit.exr],
does that yield bad results?
From my understanding, 32bit images contain data that we can't necessarily preview with a typical viewer because it contains a range of data larger than a monitor can display.
From docs:
"A 32 bit image, also referred to as a high dynamic range image (HDRI), records all of the positive and negative distance values beyond the 0 to 1 range, so it contains much more information than can be displayed on your computer monitor. To view this full range of values you need a utility that displays HDRI images such as the Image Browser in Mudbox."
Also, I don't use this software: "Photoshop".
For me, when viewing with the Mudbox "image browser" all seems good.
If you still feel like it's a defect.
I will have to log the issue so that QA/Dev can take a closer look.
Thanks for reporting,
and let us know.
Can't find what you're looking for? Ask the community or share your knowledge.