I just tried to start very new skp2026 but it goes bugsplat al the time and it wouldn´t open at all.
can anybody help?
thanks int advace Miro
What is your GPU?
Nvidia 2060
Please correct your profile. GPU is ok . When you installed SU, did you right click on the downloaded file and choose “run as administrator”?
No i did no I runed it from update in skp2025 i havent noticed that. i will try reinstall later as admin.
2 Likes
After the right-click choose “run as administrator” then choose the repair option.
The crash seems to have happened while an extension, TRAVAIL_DU_BOIS, was loading. If you used the Extension Migrator to carry over extensions, you might want to delete that extension from the plugins folder, and do a fresh install of the extension.
The extensions are in here:
%AppData%\SketchUp\SketchUp 2026\SketchUp\Plugins\
1 Like
Thank you @colin for having a look at the problem. I give it a try in the morning.
The first time I ran it after install via update it gave me a BugSplat but worked fine after that.
thank you @colin and @RLGL . deleted wms up extension and also repaired sketchup as admin and all is up now ready for testing.
thank you
1 Like
I ran the update from 2025 as well and had ZERO issues. Only 1 plugin that was migrated did not work but it is a rendering plugin and I expected it not to work.
1 Like
Can we get the popup crash box to show these relevant stats instead of having to reach out through the forum or find hidden logs?
The main file I look at to see at what point SketchUp crashed is the SketchUpLog file. On Windows it is written into the temp folder. You can open a File Explorer window and type in:
%temp%
to get to that folder. View the folder as a list, and choose the date modified column, to quickly find the latest copy of that file.
Open the file in Notepad, and scroll to the bottom, to see the last successful action that had occurred.
From the look of it, TRAVAIL_DU_BOIS that I mentioned appears to have successfully loaded, and it was the extension after that one that had issues. Normally the extension that had problems would have shown “Loading extension: extension name (extension version)” in the log, and no further lines. In this case even that line had failed to be written to the log file.
Instead of making people chase these hidden window log files, can it just be placed into the already existing bugsplat popup? This make the bugsplat useful instead of always having a generic popup that doesn’t lead anywhere or tell the user any actual useful information.
I’ll have to test when I next get one. It may be smarter to put this button above the send button since it will disappear once you send the report.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.