When I upgraded to macOS 26, overall SketchUp and Enscape still ran normally. However, I encountered some strange issues.
For example, it is difficult to select a component with a mouse click. What I mean is that sometimes a click selects the component, but other times it doesn’t work and requires multiple clicks. Additionally, the model window keeps shaking left and right. Moreover, SketchUp has crashed several times; I’ve made some notes about this.
Crash #81169 17/9/25,18:00,When I stretch a Enscape light.
Crash #81172 17/9/25,18:02,When I open this SKP file, it prompts that the file is read-only and then crashes.
Crash #81627 18/9/25，8:45，After I double click a SKP file.
Crash #83509 22/9/25，13:45，After I double click a SKP file.
Crash #84939 24/9/25，8:23，After I double click a SKP file.
Crash #84942 24/9/25，8:29，After I purge unused items in the model information.
Crash #85666 25/9/25，9:05，After I double click a very small SKP file.
Crash #85667 25/9/25，9:08，I opened the small SKP again and It crashed again.
Crash #88312 30/9/25，8:15，After I double click a SKP file.
as usual, like every year and mac os release, sketchup isn’t technically marked as compatible.
this means that if you want or need to upgrade mac os, you’ll do it at your own risks.
compatibility comes with the next sketchup update.
Second rule of mac os, a version of mac os is considered actually stable around it’s third update. so until mac os 26.3 you can expect bugs that will have an effect on other software.
these I get in Sequoia, and after some experimentation, I noticed that when I open a sketchup file and immediately click on another application (to change the music while the file starts for example), it crashes. it doesn’t like loosing the focus while booting. it’s coherent with the other focus issues we’ve had in the last few years on macos.
@colin can have a look at your crash codes, maybe he’ll see something specific.
In the next update from us there are changes on Mac to do with how it handles being sent to the background and foreground again. Issues caused by that would affect Sonoma and Sequoia, not just Tahoe.
One thing occurred to me, with Enscape, and starting a new document, Enscape does come to the front, so could trigger more focus issues than you would get if you didn’t have Enscape. I have Enscape in SketchUp 2025, but couldn’t trigger a crash.
I will come back to this topic when I can give a date for the next update from us.
Just updated to Sketchup 2026 on MacOS Sequoia and discovered my 3Dconnexion SpaceMouse-Pro does not work at all …. nada. Under Sketchup 2025 the SpaceMouse-Pro works fine…. well it has issues, because the 3Dconnexion drivers are substandard in my opinion, but it does move my model around. I have the latest 3Dconnexion drivers for MacOS Sequoia.
I tried upgrading to SU 2026 because I am getting crashes with SU 2025 after about 3 hours of modeling. Symptom is spinning beachball of death in the SU application. MacOS activity monitor says SU memory usage has ballooned to 10gigs on my 64-gig RAM Mac. Have to Force-Quit SU to recover.
Will follow this thread to glean suggestions to recover 3D mouse functionality.
You always have to reinstall the proper drivers for the 3dConnexion accessories when a new major SKP release comes out. It’s been like this since… as long as I can remember. It’s not a snarky feature as you point out, it’s a reality.
You can try manually copying the files from the plugins folder from 2025 to 2026 - it might work. It might not.
Otherwise you have to wait until 3dConnexion updates:
Most of the issues I encounter seem to be related to plugins. Any version of SketchUp runs fine if I don’t install any plugins. But who can work without plugins? Fortunately, I don’t have an expensive mouse like yours; I’m just using a regular three-button mouse. When I upgraded to macOS 26.1, SketchUp 2025 worked fairly well. I’ve been working with large models over the past few days, and although there’s frequent waiting involved, at least it hasn’t crashed. Today, I also upgraded to SketchUp 2026, and unfortunately, SketchUp 2025 is still present in the system, and some plugins require me to set them up again. Custom templates can be manually copied over; however, custom toolbar icons are completely lost even when I copied some old version plist files.
But what about my Enscape? It’s really frustrating! macOS, SketchUp, and Enscape have interdependent version relationships!
I believe 3D Connextion has a beta program with a new driver they are working on. Youll likely need to sign up for their insider program to access it though. That said, I am in contact with their team and will post the link to their drivers as soon as they become available.
We are also busy behind the scenes building an new UI for Mac that will release in the future. Ill send you an invite to our private labs to test it out. Would love to hear feed back about it. The real problem is the Cocoa architecture our Mac SketchUp UI is built on is showing its age.
EDIT: After an internal discussion with the team (QA, Dev, Product), we’re going to add official support Mac Tahoe, keep an eye on the Hardware/Software requirements for that update. We are also dropping support for Monterey in this release. This doesn’t mean SketchUp wont work, it just means we wont be addressing any Monterey specific bugs in this and future versions. - @ahmay I’ll work with Colin on tracking those bug crashes you’re seeing.
Because the official version released a little less than a month ago (Sep. 15th), we’re still internally testing against the release version, and while the automated testing we do shows no big red flags, we still have some tests to run through. I won’t discourage users from upgrading to it, and it does run on Tahoe, we don’t currently officially support it today. That is likely to change in the very near future and we’ll be making a note about that in the hardware documentation.
Same as is true for other extensions, there is a separate copy of the 3dConnexion extension for each version of SketchUp (on Mac 3DC puts it in the system’s /Library/Application Support, not your personal ~/Library/Application Support). Their installer detects installed versions of SketchUp and copies their extension into the folder for each during the install process for the 3DC drivers. So, a new version of SketchUp isn’t discovered until you re-run the 3DC installer after installing SketchUp. This has always been the case with 3DC, though recent installers appear to find new versions of SketchUp whereas the older ones were hard-wired to stop at the last known compatible SketchUp.
I don’t remember whether I re-ran the 3DC installer or manually copied the extension, but it is working fine with my 3D mouse and SketchUp 2026 on macOS 26.
Same situation for Enscape and V-Ray and a bunch of others - you have to have SketchUp installed before you install it for them to install to the latest SketchUp.
The existing 2025 3DX files do work with 2026 on Mac (if you copy the files over from the 2025 folders). For Windows they don’t work, but there is a beta build for Windows that does work. Hopefully they will release a new installer that works for Mac and Windows.
This seems to happen every year, and when I do a search for 3dConnexion or Space Mouse and its derivatives I don’t find anything relevant or mentioning these issues.
I can confirm that after upgrading from 2025 to 2026, and using the migration tool… the 3dConnexion extension did not port over. After updating the driver to the most current one available on their website, still no use. This update included, removing the previous driver with the software’s UnInstaller, then installing the new Driver.
In previous incarnations one would have to go through application support and copy and paste the extension from one version to the next. It appears there is no extension available in previous years to accomplish this. This was the support recommendation by 3dConnexion in 2023.
I am pleased that 2025 still works with the Space Mouse. So that does indicate that the problem is specific to 2026 SketchUp.
Apologies for being “snarky”, admittedly born out of frustration: my SU-2025 is crashing after a couple hours (requiring obsessive SAVEs) and installing SU-2026 with transfer of plugins was not useful because 3D mouse ignored. Edited my previous post.
There are a non-trivial number of SU subscribers who use a 3D mouse including Aaron previously of Skill-Builder (on a Mac).
In 1977 I started coding in assembly and designed embedded control systems for industrial machinery. At our company we took version release testing very seriously, otherwise machinery operators could be seriously injured, or even killed. The only software friend I knew with even more obsessive dedication to testing worked for Physio-Control designing defibrillators - electronic equipment that sits on a shelf for months/years then must work flawlessly in 30 seconds to save a human life…. no pressure.
Did Trimble not give Aaron early versions of SU-2026 for testing, including his 3D mouse ? Others have mentioned new versions of SU have had “issues” with 3Dconnexion 3D mice not porting over to the new SU version. This leads to user frustration, but snarky does not help and will be avoided in the future.
Thank you. Your suggestion for a dedicated thread to address and review 3D mouse issues in SU, I think is an excellent one. The info provided regarding the procedure you used: the migration tool … etc also helpful. My upgrade process was similar, however I have not tried manually copying any 3Dconnexion extensions found. Will see if that is possible.
