I would like to share my concern regarding the ongoing crash issues with D5. In the support forum, the team often asks the same questions repeatedly, and even after providing the requested information and log files, we still have not received a clear fix or solution.
These issues are now seriously affecting project timelines. As professionals using D5 for client work, stability is very important. Even after paying for and using the Pro version, many of us are still dealing with frequent crashes and unresolved problems.
It would really help if the team could provide a stable solution or patch soon. Alternatively, is it possible for users to roll back to a stable version such as D5 2.9 or 2.10, which worked reliably before?
Another concern is that with each new version, the lighting settings and scenes change, forcing us to rework our projects almost from scratch. This adds a lot of extra time and uncertainty during production.
We appreciate the development of new features, but stability and reliability are equally important for professional workflows.
The way this is beeing handled is turning into a tell tale sign of “you get what you pay for” i fear. paying the extra for D5’s major competitor before i made the switch, at least you had a team of tech guys in support that would go out of their way to help you, no matter what time it was.
I am running wild and losing my nerves with my deadline tomorrow. paying for a pro subscription for a program that crashes every five minutes is unacceptable.
please just give us a link to an earlier version befor this started happening. I can only find a link to version 2.9 which basically lacks all the AI features like inpainting or effects that I would desperately need. It must surely be possible to just provide us with a link to 2.9.5 or 2.10 somehow?
your help would be greatly appreciated, Thank you.
edit: just found the old versions here, in case anyone might still need them:
I’m not sure but if you’ve been working on a D5 file from 3.0.0 or 3.0.1 wouldn’t reverting back to a previous version open up another can of worms in addition to adding a new set of problems to fix including lighting, materials, atmosphere, etc?
Today I got two random crashes already. This last one was while rendering and working on a model in Sketchup at the same time. I still suspect there might also be a problem with LiveSync.
I don’t know what’s going on. I’ve grown to like D5 Render but with all these crashes with no end in sight that’s come into question. At the same time I really don’t want to have to go through the learning curve of replacing it with Twinmotion or at this point even Lumion. In any case, I need to do something about these crashes because I am in no position to have to deal with this on a daily or hourly basis.
I don’t want to revert to an older version. I’m a monthly subscriber and expect to get the latest software from D5 and not have to go back to a used car. These crashes need to be fixed soon because this is not sustainable and will also harm D5’s reputation.
What you just mentioned is so true, paying for pro version and rolling back to older version and again dealing with latest version files in older version is a tedious and time consuming task.
Hi! i already answered those questions in the previous topic i opened before you merge it here. About point 7, which hadn’t been mentioned before: in the file I was talking about, which is very big, yes, I’m probably exceeding 80%. I have an RTX 5080 with 16 GB. That said, I’ve always exceeded that and have never had these kinds of problems.
On the other hand, I was just working with a very small file and it also crashes, so no, it’s not because of that. Needless to say, this didn’t happen in previous versions.
I think I may have found what is causing the crashes. As I suspected, I believe it is related to an internet connection issue.
I used D5 all day without any crashes and couldn’t understand why, until I realized that I was using it without being logged in. As soon as I logged in, it crashed again almost immediately.
If this is indeed the cause, I hope this information helps the developers fix the issue. As a recommendation for others experiencing the same problem, I suggest trying to log out and work that way to see if the crashes stop.
I know that users with the Pro version will see “Pro only” watermarks on some objects, but I think it’s still preferable to work with those watermarks rather than having the program crash unexpectedly every five minutes. If needed, you could simply log back in when it’s time to render.
Until an official fix or patch is released, this might be worth trying. Internet connections are never perfectly continuous; there are always tiny micro-interruptions lasting milliseconds, and it would make sense if that could cause crashes at random moments, which might vary depending on the day or time.
I hope this helps. It has worked for me throughout yesterday and today.
Reinstalling a lower version of D5 should not cause you to lose your library, favorites, or custom materials. However, if your project uses features available only in version 3.0, you may encounter limitations when opening it in an older version.
In such cases, a prompt window may appear notifying you that certain features are not supported in that version. Alternatively, those features may simply disappear. Additionally, assets introduced in newer versions may not display correctly in older versions and could appear as white boxes.
It’s definitely Turbo Mode on my end. I’ve been working crash free for a couple of days with it off but this morning I updated my BIOS and it turned on Turbo Mode. I thought to give it a shot but it crashed D5 within 5 minutes. Trying to tune other things like tweaking XMP settings for RAM. Won’t make that much a difference. As for the cause of what appears to be a Turbo Mode bug on my end with D5 is unknown to me at this time. Same thing happened years ago.
Turbo Mode is like an easy form of overclocking where it raises the CPU speed within limits above its rated speed. My CPU (i9 10900K) is rated at 3.7 GHz and with Turbo Mode off it stays planted below that rated speed. With it on it will rise belod 5.0 GHz depending on load. The only issue with Turbo Mode on on my machine is with D5 Render.
@gusrobatto 100% true, if you have a Intel processor or certain motherboards it’s called “Intel turbo boost” I did what you said and it’s been 2 days without crashes so far. “THANK YOU”
There appears to be quite a few bugs with version 3.0.1 - while I’ve not recently experienced silent crashes, I’ve noticed a distinct drop in D5’s ability to handle large complex models (circa 8B faces) which is no different to what I was working on when version 3.0.0 was released and previous 2.11 and earlier versions. Some key things I’ve noticed and some momentary (yet less ideal work arounds).
When syncing large linked models from Revit into the D5 workspace there is a functional limit to the size of models its able to sync before crashing, however if you export the model(s) as a .d5a file I’ve managed to load all models without crashes occurring, this is less than optimal as in version 2.11 I was able to load all the same models flawlessly.
As mentioned earlier in the thread, materials have been appearing as white after reopening the D5 project (in my specific use case Grassland 03 was one of the main offenders which still hasn’t resolved - Base colour map icon was displaying initially as a white square, recently its reverted to a duotone grey square but unfortunately as far as I’m aware there is no way to reload the missing D5 base colour map.
Stability when rendering videos at 30fps, 1080p and approx 1min in length have on occasions crashed when rendering the full video (not an image sequence) - my assessment on this may in part be due to the complexity of the scene being rendered at the time of the crash (high poly count, lots of vegetation etc) the fact still remains this is a significant downgrade from version 2.11 which was much more stable from my experience.
This has significantly impacted deadlines and output for jobs I’m working on and would hope to see a more stable hotfix published soon.
I wanted to provide an update regarding my recent experience with D5 crashes.
After extensive communication with D5 support and a review of my project files, their final assessment was that my current GPU (RTX 3060 Ti 8GB) lacks sufficient VRAM to handle the project’s complexity. They recommended upgrading to a GPU with minimum 12GB of VRAM, which currently costs approximately €1,000+.
I found this assessment unsatisfactory, especially since many users with more powerful hardware are facing the same issues.
Before committing to an upgrade, today I decided to test the “Turbo Mode-off” settings suggested by Gus (I am also using an Asus Z490M-Plus motherboard with a I9 109000@2,80GHz CPU). I am happy to report that I have worked for nearly 5 hours straight without a single crash (both actively working in D5 and leaving in stand-by).
While it may be too early to claim a permanent fix, this adjustment seems to be working for me effectively so far, so I highly recommend others facing similar issues try this setting before investing in new hardware or try anything else.
Gus, man, I’m not sure how you discovered this, but thank you—you’ve been a lifesaver!
Thanks Daniele. Something I figured out about 3 years ago with D5. Right now I’m experimenting with Turbo Mode on but I set Asus Multicore Enhancement to Disabled - Enforce All Limits. Just fired up D5 Render and I’ll see if it crashes. Looking for a workaround to keep Turbo Mode on.
Setting
ASUS Multi-Core Enhancement (MCE) to "Disabled - Enforce All Limits" forces your CPU to adhere strictly to Intel’s official power, current, and thermal guidelines. This prevents the motherboard from automatically overriding manufacturer specifications, typically resulting in lower power consumption, reduced heat output, and standard factory performance levels. It is the recommended setting if you prioritize system stability and longevity over maximum benchmark scores.
Took 10 minutes longer to render 6 scenes with Turbo Mode on with Disabled - Enforce All Limits than with Turbo mode off with MCE on Auto. I didn’t test overall performance like running Sketchup and D5 at the same time.
I’m trying it now with ASUS Multi-Core Enhancement (MCE) set to Disabled - Enforce All Limits with Turbo Mode enabled to see if I get any crashes. Since I discounted any GPU issues I installed the latest Nvidia driver for my RTX 5070.
24 hours later:
Crashed this morning after a whole 24 hours of no crashes and I put it through some ropes including opening random files and rendering.
Crashed after a rendering. Just random after closing the rendering window. Tried the same file and scene again. Another crash. Tried it a third time. Crashing stopped. Then I thought it might be from watching a Youtube video and while running the video there was no crash. GPU and GPU temperatures are nominal at the time.
These came back after creating a new scene using a section plane. I’m now fiddling with a previous version of the file and scene(s) to see what happens.
This is with Turbo Mode on with Disabled - Enforce All Limits.
Went back several times. Totally random. No crash at the moment.
You can bipass the Turbo Mode BIOS setting in Windows through Power Plan with " Maximum processor state to 99%."
