I’m reaching out for some help please. We’re failing in getting the texture colours right. Can someone shed some light what I’m missing with these settings please:
Below is the resulting RC texture colours and the post-processed with dng/lightroom photo, exported as tiff sRGB:
Unwrap, Texture Settings and post-texturing results are shown below: Note this last test we removed “Recolor model after texturing” but the result is very much the same. I played with different Texel size settings including optimal but the color results is very much the same.
As a side question, what does Texture quality result 874% mean?
If you use 16bit inputs your images are tonemapped to 8bit and during this process colors may change - this is bug on our side.
We have integrated custom HDR/16bit to 8bit tonemapping algorithm for better alignment and meshing (experimental).
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. We always recommend to do that as 8bit images are much smaller and RC can process them faster.
There are no color settings withing RC.
Your texture is calculated based on colors from your input images.
Therefore it is the best to edit your images before processing within RC. (Some users use color checker targets to calibrate images before processing)
Apologies for the late reply, we wanted to make a few tests before responding. Yes we had processed the images before loading them to RC.
Instead of using Optimal Texel Size at Unwrap and Texture, we used Custom at 0.002 (the model in RC is 21 units wide by 41 long). We are very pleased with the result, but of course it took 4x to bake.
Can we please ask for your invaluable help to clarify our result , this helps us speed up our future baking results:
what does a resulting texture quality 689% mean? If I understand correctly, 100% is 100% resolution, how can we get >100% res?
And if the result shows Optimal Texel Size =0.137 units per texel, what does this tell us if we were to bake again, does it mean we would be wasting computer resources if we bake at a texel size below 0.137?
Unwrap Maximal texture resolution: we used 4k maps and ended up with 48 textures. Is our understanding correct that if we increase map res to say 16k that would not hamper our results, it would just reduce the number of textures we’ll have?
Thanks for reaching out. I’ll go back to the vast well of wisdom to regather on these discussions, if you have any particular links you think is clear is of course much appreciated.
We didn’t reprocess them, that’s why reached out to ask. We used the existing processed images, but this time instead of using Optimal Texel Size (0.13782) at Unwrap and Texture, we used Custom at 0.002 (in both cases Fixed Texel Size style) though it took 4x to bake (resulting count of textures increased from 2 to 48).
We reprocess these final textures so the extra unused texture space (0.13782/0.02=689% is the texture space and computer processing power we’re wasting right? ) hopefully doesn’t affect the final render.
It’s early days for me with RC and I may have taken a misstep somewhere. Else I’m quite sure this will come up again in future scans would come back to the community with findings
