Hi there, I noticed some weird behavior when I am trying to import an EXR file.
I am trying to save the position information of a point cloud as a texture.
So, I am saving a 32bit EXR file with a resolution of 8096x1173, but when I import the file the pixels are slightly different.
I compared the two textures with a ‘‘difference’’ top and I saw this weird banding artifact.
Not sure if the problem is in the moviefilein or in the moviefileout.
Windows 10, Build 2020.23680
Hey, can you post your .toe file so we can see the example more directly? You can likely just Lock a TOP before the Movie File Out TOP you are using to save the image (we don’t need everything upstream used to generate it).
Should be able to get to the bottom of the issue then.
Thanks for the report.
Hi Malcolm,
Thanks for your reply.
I can easily replicate it with just a “Moviefile in-out” and a difference TOP.
I have attached a .toe file that shows the problem.
all the best
Thanks for this. The error was very subtle. Basically an error introduced by texture coordinates imperfection on large textures resulting in a very slight pixel interpolation when doing vertical flips (which I need to do due to GL/EXRs difference in holding scanlines).
The fix won’t make it into the build that’s coming out this week, but it’ll make it into the next one.
That is great Malcom! The problem is indeed very subtle but becomes visible when you 're trying to save the position data of a point cloud as a texture.
Thanks for fixing this!
