As far as I can tell it’s just a specific model. Suddenly started happening. I thought it might have been a corrupted Sketchup model but fixing it didn’t help. I’m going to try some other things.
Nothing changed in my Windows OS or bios setting. No other model is exhibiting this behavior. I’m going to try more things to see if it helps.
Thought I had it nailed down again by copying and pasting the same model to a new SU file. Then I “zapped” the FlexTools assets. Etc. Poof! Crashed again while I was on the phone. Going to see if this is happening with any other D5 models.
Thanks for reaching out and providing details about the crash.
From what you described, it seems the issue is specific to this model. I recommend trying the following:
Import smaller parts of the model individually to identify any problematic geometry.
Export sections as separate files or .d5a assets and import them piece by piece.
Monitor your system’s GPU and RAM usage while importing, as crashes can occur if resources are exceeded.
If the problem persists, please share the model file and your D5 log file with support@d5techs.com, tag me, and include a link to this forum thread for reference.
Well, it just crashed with another Sketchup model. This hasn’t happened in over a year and started after a recent update (not sure yet) but I did recently update Livesync.
The other model that just crashed D5 got stuck updating the D5 model from Sketchup which also never happened before.
To recap. I made no changes to my computer’s OS or BIOS. This has to be related to D5’s recent updates. I use D5 for my work and frankly I’m tired of having to spend time troubleshooting D5 like this in what seems to be an annual event.
Once they are available, please send them to our email as well so we can further investigate the issue. Thank you, and I look forward to your response.
It just crashed using a different model. I spent a lot of months without any crashes happening at all and then after what appears to be recent update the notorious D5 crahses started coming back. I just lost a lot of work because I wasn’t saving every five minutes like I should.
Wouldn’t you know it. I managed to find a backup to recover and saved some work. I went back and covered my tracks and saved it a few time and then, boom. Crashed again. This is getting ridiculous.
I’ve received your email, but it looks like there is a permission issue with the Google Drive link, so I’m unable to view or download the files.
Could you please reupload the files to WeTransfer and share the download link with me? That would allow me to access them without any permission issues. Thanks so much for your help.
Crashed twice this morning. I’m trying to earn a living here. I asked in a previous post about access to a previous version of LiveSync and got no answer. I need to figure this out ASAP because I’m not using this as a hobby. It’s crashing with another model and both models now are not showing any errors.
Well, I thought I solved it with a fresh install but it’s come back. I’m not getting any answers here nor any answers or response from D5 support. I’m still waiting to find out where I can get an older copy of LiveSync but that may or may not be the issue. Bottom line is that it’s gone back to crashing like it was a few years ago. This is new and I have not changed any CPU or BIOS settings. I would appreciate hearing from D5 support officially but so far I haven’t heard anything from them yet. I’m disappointed with how this has progressed.
Not ready to declare victory but there have been no crashes for the last 24 hours. Not 100 percent confident yet but here’s what I did:
Checked BIOS - all default settings.
Deleted Nvidia GLCache.
Uninstalled latest Nvidia driver.
Ran Display Driver Uninstaller in safe mode.
Installed Nvidia game driver 576.80.
Uninstalled D5 Render.
Deleted all D5 directories.
Clean install of D5 Render
Installed latest Microsoft Visual C++ Redistributable v14 x64 and x86.
Ran D5 Launcher as administrator - directly restarted.
Turned off Super Resolution in D5.
Events viewer indicated a crash in D5 pointing to a ucrtbase.dll which led me to install the latest Visual C++.
I suspect it was related to the Visual C++ but given all that I’ve done to prevent these crashes it’s hard to tell.