To get a more stable workflow, I work on the old graphic engine. I do like the Ambient Occlusion look so sometimes, switch back to the new engine but experience several crashes a day in that mode. The Old engine is very stable on my machine.
NVIDIA drivers for my GeForce RTX 4080 are up to date.
Are there known extensions, drivers or settings that causes the new engine to crash? I’d love to stay in that mode (new engine) so any input to make my workflow more stable would be greatly appreciated.
I submitted several bugsplats in the past few days so maybe something transpire from them?
I’ve read that the Lumion plugin causes constant crashes, but there could be more reasons for it. If you post the crashing code numbers it will be easier for the developers to detect was going on.
I looked at the 20 bugsplats you sent in, thanks for those.
Most of them are the same issue, which some number of other people have seen, though only with SketchUp 2025. I don’t see the same crashes with 2026, or any 2026 bugsplats from you.
There is a crash I have seen in 2026, that could also happen in 2024 and 2025, where you start to draw something (for me it was a Medeek Wall section), and before you move your cursor, you Space Mouse orbit the scene. We have a fix for that in internal builds, so hopefully that will be included in the next update, whenever that is.
Thanks Colin, I installed 2026 but as it was crashing, I went back to 2025 (hence the codes you are getting are 2025). I do not use Medeek wall but do use a Space Mouse so maybe that is part of the issue. I have the latest model and am pretty sure I have the latest driver for it but will doublecheck.
By all means, any comments or recomendations pointing to a potential issue are welcome and so will be the next update. Will that be only for 2026 or will there be a 2025 update as well?
The crash that can happen with Space Mouse isn’t their fault, I wouldn’t expect a driver update to help. SketchUp starts to draw something, which in all normal cases would be followed by a cursor movement, to give the object some dimensions. The special case of a brief click, followed by an orbit where the cursor has not moved, leads to a situation where something with no dimensions is drawn, and that leads to a crash. You could for example do the click, then shift-Z to zoom extents, and that too could crash.
There is a good chance it’s extension related, and could happen to extensions other than the Medeek ones.
The underlying issue could affect a lot of use cases. It may be that if an extension waited for the cursor to move before drawing, a crash may not happen. But there was something that needed fixing.
Thanks y’all for looking into this - I will keep the splatbug coming (hopefully less and less) and will switch back to 2026 as soon as my workload permits. Anything I can do on my end to help y’all figure out the issue? It may be of help to others so I’ll do the best I can. Cheers!
following up on my revious posts, still crashing several times/day. Running now SU version 26.2.243 64 bit now and I still get constant crashing with the new engine on. Less without, but still. I am sending all my crashes but no longer write the conditions (hapenning so many times a day…) Is there maybe a graphic card setting you can see on your end that is causing that? maybe an extension or a driver?(runing the latest Studio driver from NVIDIA) Any help would be greatly appreciated
I looked at several of them, and the crashing for each one was when ExtrudeTools was being loaded. I notice that you are using ExtrudeTools 5.0, and @TIG has a 6.0 to be more compatible with newer versions of SketchUp. Perhaps you could try that? :
Colin, thanks for you help - I just instealled the 6.0 from TIG so hopefully that will help.
Also I am running on the old graphic engine to limit crashes - When I switch to the new graphic engine: more crashes… Just made sure both NVDIA and Intel are set to NVIDIA High Performance process. Anything else I should do to hopefully be able to use the new engine?
Still crashing on startup - I found that sometimes, starting by opening one of the default templates helps I can then open the model I am working on. Still sending bugsplats and trying to make sense of them and how to understand what they say but above my pay grade As usual, any help is greatly appreciated, I so much would love to be able to work using full potential and capabilities of SU 26 without constant crashes…
Today’s crashes are happening when LibFredo6 is loading. I’m guessing that if that initializes when there is a model that uses Fredo6 features, that something goes wrong. Getting it to initialize with an empty template, could be why your model then opens ok.
One thing to note, if you’ve opened a fresh document, and then double-click on your working model file, that may effectively be a fresh start. Try opening your working model from the File menu.
Thanks Colin - I will try to disable Fredo’s plugins just to see if that changes. Will also see if opening from menu works smoother!
Quick note I created a support ticket about my issues and was told, on my machine, there was maybe an older version of Microssoft C++2015 and above Distributables. Was to remove, de-install SU26, the reinstall from an offline link (including the C++ latest) and that seems a bit more stable now… but still crashes here and there… Hop tha helps anybody. Again, that was support, from reading my crash reports so may not work for everybody .
Thanks again for your response!