Don’t really remember the previous version that I had when this issue started (if was 2.7 or 2.8) but my existing file crashes after being open for a few minutes. This file never crashed while I used D5 Render for a whole year. It crashes without an error and after freezing for some seconds. I already tried to update to 2.9.0.0500 and it still happens.
Do not know what I can do more. Updated all the drivers after and still the same. Starting to be stressed because I really need to deliver work and I’m not being able to do so .
Hi there. I apologize for the inconvenience this issue has caused. Does this issue persist in other files? Or is it specific to this file only? Can you also provide the following information?
I start a random project, change materials and add models without any problem, but sometimes I start adding renders to the render queue or start right away rendering and it freezes, from that point forward I can’t do anything in the program or in my computer and I have to restart it
Hi there; I apologize for the inconvenience this issue has caused. Currently, there seems to be a known stability issue for AMD Graphics Card users. A user previously reported and shared that their D5 Render 2.8 version only works with AMD Driver 24.5.1, and anything that is much more updated than the said driver does not work with D5. Various problems with version 2.9 - Get Help - D5 RENDER FORUM
Can you send us your log files? You may refer to this link for further instruction: How to use Support Tool? | User Manual You may send it to support@d5techs.com and have it titled as “AMD Clov-Forum” or you can directly share the downloadable link here (if it is convenient or possible for you)
We are currently investigating this problem and working on a probable fix. I will let you know about any updates. Thank you for your understanding.
Can you also send this specific scene file to the same address? You can use a Wetransfer link. We’ll test it with various versions in our environment, which would help us investigate this issue further. We really appreciate any help you can provide.
Hello @Leah_Li ,
Already sent the log files to that email you shared , and now will also send to you the specific scene file to the same email.
Thanks for the help!
Please delete the ‘f2’ folder under your WorkSpace path and then reopen the archive. Once opened, please do not update the assets until you lighten your scene file by deleting some assets including procedurally generated vines to prevent it from crashing again due to bursting video memory.
Additionally, we kindly request that you provide us with a new WeTransfer link for the scene file you previously sent, as the original link has expired. Our team needs to recheck your file. Thank you for your cooperation.
Hello,
Regarding the first step I already deleted the f2 file , but the rest of the step I didn’t really understood, I have to avoid procedurally generated vines and other assets? That might be a weird thing since I have a powerful enough to use D5 render.
Hi @filipaa.fontes, Deleting the f2 folder will allow you to regain access to your file. However, after opening the file, you will receive a notification to update the assets affected by the deletion of the f2 folder.
Some of these assets, particularly the procedurally generated vines, consume significant VRAM resources. Therefore, it is advisable to delete these vines or hide them in your scene, as well as to implement other optimization measures before updating the assets again.
Does the problem persist even after deleting the f2 (pak files) folder? Please let us know.
In addition to what @Anthony_D5 has said, there is currently a known issue regarding the use of Procedurally Generated Vine Assets which has an increase in VRAM Consumption in the 2.9 Version. We want to assure you that we’ve resolved this issue and the fix will be included in the next D5 Render update.
In the meantime, to help manage VRAM usage, we recommend grouping these assets and hiding them when they’re not visible in the scene. This simple optimization can make a big difference. We sincerely apologize for this inconvenience and appreciate your patience and cooperation.
.
