I’m encountering an issue in D5 Render where the final output appears significantly overexposed compared to the real-time preview. In the attached image, the left side shows the preview, which looks balanced and natural. The right side shows the exact same frame after rendering — with blown-out lighting and a strong white cast on the interior and curtains.
This occurs during a day-to-night animation sequence, mostly at dusk. I’ve already checked camera exposure, emissive materials, and lighting setup, but the problem persists. Screenshots/Videos Description:
Thanks! I actually just saw there’s a new GPU driver update available. I’ll install it now and run a new test render. I’ll let you know if the issue is resolved after that.
Thanks for the follow-up. I’ve recorded two short screen captures to better illustrate the issue.
In the first video, I move quickly through the timeline. You can clearly see a strong white overexposure appear inside the house (especially on the curtains and furniture). The glow slowly fades out and the lighting stabilizes.
In the second video, I scrub the timeline slowly, and the lighting remains correct — no overexposure appears.
Note: In the first video, I had disabled the linear lights on the terraces to test if they were causing the issue. In the second video, those lights are enabled — yet the overexposure still happens in both cases. So the problem does not seem to be related to those specific lights.
This suggests that the lighting (perhaps GI or exposure) needs time to re-calculate after fast timeline jumps. However, the overexposed state is what ends up getting rendered in the final video — not the corrected frame that appears later. Another detail that catches my attention is that the curtains, which are D5render assets, look very white. They are very bright.
Here are the two screen recordings:
Let me know if you’d like the full project file or a sample render.
I have seen the two videos, you are right, in the camera movement it is well noted that the loading of the light beam starts from a glow and then it is attached, even if you have a RTX 3060 card is good indeed and powerful, perhaps it is the memory that is little. I am not doing video for the exposure for customers, but only render, because I have a laptop GTX 1070 from 16g Intel i7 as a processor with another 16g.
And I tell you that, the D5 program does it to me too when I load the image to another this glow, and then reset our settings. Maybe it depends on the super resolution that my card does not have. Instead your 3060 there, perhaps activating it can improve or worsen.
Can you send us this specific D5 File so we can also test it on our end? Please send it to support@d5techs.com and have it titled ‘Clov-Forum Interior Spaces appear Overexposed in Final Render’
Note: Please zip the D5 File first then provide the link.
Good morning, Ricardo.
Don’t apologise for your English. I use a translator.
I have the Super Resolution option enabled. I’ll try disabling it. I’ll let you know the results as soon as I have them. Thank you very much for following up.
Hi, look at the team’s CLOV forum, given a suggestion to an high user, I put the link below, tells you to deactivate D5 SR Beta widgets to see if the final rendering is closer to the preview screen.
Good morning, Clov.
As far as I can remember, nothing like this has ever happened to me before. This is the first time I’ve gone from day to night in a video. Right now, I’m testing what Ricardo Fortelli (ricardofortelli) told me about Super Resolution. I had it enabled, and I disabled it to do the test.
Regarding sending the file, I have a problem because I have some large files in the ‘asset’ folder. In total, the folder takes up 15.5 GB. I’ll see if I can fix it.
Thank you for your help.
Following my recent post in the D5 Forum, Clov recommended that I send the files directly to this support email.
The issue I’m experiencing involves a strong white overexposure or glowing effect in the final rendered video — particularly inside the house during a day-to-night animation, mostly at dusk. This overexposure does not appear in the real-time preview, only in the final render.
I’ve already tested the following:
Updated my GPU drivers (RTX 3060)
Enabled and disabled Super Resolution (currently ON)
Tried disabling some linear terrace lights (no change)
Recorded two screen captures showing the issue:
When scrubbing slowly through the timeline, the lighting is correct.
When scrubbing quickly (or in the final render), a bright flash appears and slowly fades.
I also noticed something else. If I move the timeline from a darker point toward the end of the animation (when it’s already more night), the overexposure is less intense or doesn’t appear at all.
This suggests the issue might be related to how the global illumination or exposure is recalculated during fast timeline movements or transitions.
To help you investigate further, I’ve compressed the project file using 7-Zip and split it into four parts. Please find the .7z.001 to .7z.004 files attached.
We are unable to access your files normally after extracting with 7-zip file; they cannot be opened. We prefer zip files using WinRAR. Additionally, please do not separate the contents of your D5 Folder separately just proceed to zip the entire project folder instead of zipping the subfolders.
I just tested your file. Enabling Path Tracing will significantly improve the final output. Generally, path tracing is more physically accurate than traditional ray tracing.
Thank you very much for your support and for taking the time to test my file in detail.
I sincerely apologize. The issue was not a bug in D5 Render, but simply a result of my own inexperience. I didn’t realize that Path Tracing needed to be properly enabled in order to achieve the correct lighting in the final render.
Now that I’ve activated it correctly, the results are exactly as expected.
I really appreciate your guidance and your patience, it has been very helpful to understand how D5 Render works more deeply.
Thanks for the update and your cooperation. No worries, Path Tracing does improve your scene significantly because it offers a more accurate light calculation compared to Ray Tracing. But this feature will surely consume more VRAM and will make your file heavy, so it’s best to use it wisely~
Thanks again for your detailed explanation and for confirming how Path Tracing works behind the scenes.
I completely understand now why it made such a difference in my scene, and I’ll definitely keep your advice in mind when using it, especially for animations with high lighting complexity.
I really appreciate your support and responsiveness throughout this process. It’s been very helpful.
