I might do that lol I did buy a house last year and I need to fix some things.
I just gave up and reset my PC. SketchUp’s up and running again - ran it as Admin this time and didn’t run into any of the firewall issues since they patched it recently. Hopefully this solves any issues on my end. Thanks for all the info!
I was getting Bugsplat errors - sent a few of them in via the window. Don’t remember any of the numbers now but hopefully this is fixed for now
Good luck!
Yeah. That problem went away with the fix made by Windows.
When you do that make sure you include your e-mail address so the Splat reports can be linked to you.
Keep on truckin’
I have been having the exact same issue as you´ve described. Quite frustating!
I notice that if you, after doing the first export, manually “move” or “orbit” or in any other way change the current view and then choose the next scene, SketchUp doesn’t crash - at least for me. It’s not a good fix, but it’s at least better than to keep on reopening the app after every export…
I have been trying to run the installation file again as administrator and doing a repair. That didn’tt change anything. Well, it fixed another bug I’ve been having, where the tool tray was black upon opening a file. But anyway…
Have you been able to fix the issue yet?
Yes - moving around afterwards does not cause the crash. I reinstalled sketchUp after having to reset my PC because the MSI file was missing from the registry. Even SketchUp support told me to just reset my pc. It’s all working now I think - at least I haven’t had any crashes since
I stand corrected. SketchUp is still crashing. Might have to revert to 2022 if this keeps up
I’m having the exact same issue. Extremely frustrating!
Win11, SketchUp ver. 23.0.419 64-bit.
Share a SketchUp file that causes you problems.
Please correct your forum profile.
That tip actually works, move or orbit before changing scenes after an export. I tested it several times and it didn’t crash at all but as soon as I didn’t move or orbit after an export, it crashed. Thanks for the work around.
Glad it’s working. I’m not sure when a patch will be available but the support email said they were officially tracking it as a bug so hopefully they’ll resolve it in the next build.