Hey guys,
I’ve updated to the newest release of RC. When I open a previously created project which uses 16bit TIFFs, and try texturing (with the same settings) in the new release, I get a substantial difference in colour in the resulting texture. Ive attached two photos, the first was the normally created texture in the old version. The second is the texture generated in the new version, and you can see its much more saturated.
Any thoughts as to why?
Thanks
Hello Scott,
We have integrated custom HDR/16bit to 8bit tone mapping algorithm for better alignment and meshing (so far in experimental version). In previous version a default conversion provided by your CodecPack was used that was often not optimal for alignment and meshing.
That means that you need to convert your 16bit images to 8bit in your preferred way outside of RC and use them for texturing. HDR/16bit texturing is not supported yet, but it is planned.
Ok thanks for the information. Another question. if I use 16bit TIFFs as inputs on a new project with the new algorithm, would there be a big advantage now over just using Jpegs of the same resolution? Like generally will the new algorithm give say 5% better meshing, or is it greater than that?
What I want to know is, is it now always worth using 16bit TIFFs as input? If I don’t convert down to 8 bit, can I expect this colouration issue using 16bit on a new project?
https://80.lv/articles/full-photogrammetry-guide-for-3d-artists/
Vlad claims that 100% JPGs can also be used for 16 bit textures.
My bet is that it mainly affects the texture. I can’t imagine that there would be much gain if you made sure that your 8 bit images have no artifacts and if you remove the shadows as much as possible. But that’s just a very un-scientific gut-feeling…
How does one remap to the directory with the 8bit at texture time?
Hello Montrose Edmonds,
you can replace source images in the folder with the ones you wish to use for texturing. Images names have to be identical.