Hi D5 team, it appears that when adjusting new sun caustics settings in D5 2.10, they’re not taken into account when updating the scene and switching to another scene and going back to the previous scene. We need to re adjust manually before rendering the specific scene and we can’t really use “add to render queue” because the setting is not taken into account for all renders.
Hi @tom.ya
I apologize for the inconvenience this issue has caused. Just to clarify, the issue that you have experienced is: When you modify the Sun Caustic in Scene 1, then proceed to modify the Sun Caustics in Scene 2, going back to Scene 1 will reset the Sun Caustic Parameters?
If this is the case, I tried to replicate it on my end, and it seems that the issue is evident. I’ll provide a video recording, and please let me know the process so I can replicate it (if mine is wrong)
Hi @clovisbolasco14
Here’s a link to the video record that I made :
So to be more precise, scene 1 shows a swimming pool and I want to show water caustics.
Scene 2 is another part of the project.
If I adjust the sun caustics settings in scene 1 then save my settings by updating scene 1, and I switch to scene 2 when I go back to scene 1 caustics settings that I just saved are gone. They haven’t been saved.
The only way to render my caustics settings is by not switching scene and render it right away after I set it up. I can’t set several scenes with sun caustics and add them to render queue. Caustics settings are not taken into account.
In your demo video, do you have any material that has caustics on ?
I hope it helps !
Hi @clovisbolasco14, here’s another interesting record :
If I set caustics intensity and softness to 1 each they are saved.
But if I set intensity to 2, softness to 0.2 and save
when I go back to scene 1, it’s been inverted :
Intensity has been saved to 0.2 and softness to 2 !
Thanks for your feedback on this !
Hi @tom.ya
Thank you for the thorough description and the helpful video recordings. We’ve reviewed the additional information you provided and have successfully replicated the issue. This confirms the bug, and we’re prioritizing a fix. Our team is actively working on a solution, and we’ll keep you updated on our progress. We appreciate your detailed report.
1 Like