Quote - > Quote - For the image above, i created a texture containing a 100x100 perlin noise between 0 and 1, offset by a value of 1000, which is just at the limit of the representation of the 10 bits precision, and plugged it into the bump channel. The image on the left is rendered with blender (which supports 32 bit floating point textures), it looks like one would expect. The image on the right is from Poser 8, the texture is basically gone. You can recognize an overall noise added to the image, as well in the lower left an artifact, where the texture caching process probably switched from one value to the next.

Aha. Now that is good data acquisition.

I just confirmed it with PP2012. The EXR file I saved was 1000 + Spots_Node.

Loading that back and attempting to render EXR - 1000, I see a quantized version of the original spots pattern.

I'm tired of this sort of silliness in Firefly. Sigh.

Dang it - had to look at this some more. The file I saved from Poser - it was 16-bit float - the "half" float format.

So, it's no wonder it came up short. Poser doesn't let me say what I want it to store.

 

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)