I’m using
One new thing : It seems (but not very sure) that kernel panic appears when I close or hide Enscape window. If I keep the Enscape window opened/visible, no kernel panic occurs at this time. I’ll confirm that behavior in next days as I’m not really working on sketchup today 
Hi !
I can confirm after some tests this week end and this morning that the kernel panic occurs ONLY when using enscape (I also reproduce with Twinmotion, but as it doesn’t support sketchup 2024 it’s complicated to reproduce):
So that means that whenever I use Enscape plugin, I have to keep its window opened, and worst : I just can’t quit sketchup and start it again because of kernel panic. In this case, I must do myself a reboot to ensure no kernel panic.
There is something wrong with plugin window closing (maybe bad resource release or something like this).
I can’t try with other renderer plugin as I have not, so I’m not able to confirm if the problem comes from Sketchup or plugin. Maybe the two BUT this problem does not occurs with “legacy GPU engine”, so I think it’s sketchup related.
At the end, I can also confirm that sketchup 2024 on Sonoma v14.4.1 and “new GPU engine” works fine without any renderer plugin.
So I also have started to comment the Enscape thread talking about their new release of April 2024: Enscape for Mac Service Pack 4.0.1 - Mac Exclusive Discussions & Feedback and Error | Bug Reports - Enscape
Any help from Sketchup team would be appreciated
The latter. Basically SU24 Mac is incompatible with Sonoma 14.4+. It has not been updated for the slew of security changes Apple made (and posted the CVEs) on 3/7/24.
My understanding based solely on comments made by you and Barry is Trimble’s engine developer(s) could reproduce faults, and were debugging – stepping through the Metal code looking for any out of bounds memory/buffer read/writes, any faults in: low-level kernel to GPU or swapchain to the WindowServer, etc. and an update was in the works. Is this the correct status?
What @Tigrou is describing with the Enscape window - a modal window that takes and controls focus until ‘userClick’ - is an out of bounds fight between the graphics engine and WindowServer. This is also what causes the blackening/freeze/crash of the main window behind, say, the modal make component window.
Security changes in Sonoma 14.4 broke a lot of apps. Read anywhere and you’ll find issues. Apple came out with 14.4.1 ~ 10 days later to help with the USB hub issue. Many dev’s had to update their codebases. Regarding Sonoma 14.5: I’ve read yes, no, yes then no in regards to this OS update solving app code issues for the dev’s. I’m not running the dev or public beta 2 build, and don’t plan to. So I can’t personally confirm how SU24 behaves on it.
I was thinking sketchup 2024 support macOS Sonoma. But didn’t know that is doesn’t support 14.4+ Sonoma versions.
You read me wrong. SU24 Mac out of the box was supposed to support Mac OS 14+ (Sonoma) 13+ (Ventura), 12+ (Monterey) and 11+ (Big Sur). The new build released (24.0.483) in effect is incompatible due to being outdated for the security updates made by Apple. For new M3 owners downgrading isn’t an option.
I still didn’t receive my 14 day trial download link from Enscape. Is there a downloads page I can get the Mac installer from?
Hi, you can try this link : Trial Confirmed - Enscape™ | Enscape
But I don’t know if it linked to my account 
A colleague got me going. Not sure what to do now though, I have “EnscapeApplication” in Applications, that doesn’t do anything (in Terminal is says it must be run as a plugin), and no sign of Enscape inside of SketchUp. There are no new files in my plugins folder.
Could you give me the simplest steps to make the crash occur? For example, start SketchUp, new document, Start Enscape, close Enscape window.
Trying to follow your longer message doesn’t lead to a crash for me.
There are the steps to reproduce:
1 - Open Sketchup
2 - Create new document (can be empty)
3 - Launch Enscape, then enscape renderer window should open up
4 - Close or minimize the enscape window
5 - Activate (click in) sketchup app. Just trying opening a menu should lead to the kernel panic
Closing the Enscape window brings SketchUp forward, no need to click to activate it. Whterh I click or don’t click, I can use menus without a problem.
I can make a screen recording so you can see whether I’m skipping a step.
yep send me a screen recording. If it works on your Mac, so it seems mine have a problem 
Can you give me your Mac spec too please (macOS version, processor …) ?
M3 Max MacBook Pro. Sonoma 14.5.
See if I skipped a step:
Your steps seems to be correct. You have Sketchup graphics setting on “New GPU Engine” ?
Hummm my bad : Start to draw something, like a simple rectangle (after or before starting enscape)
Because I tried the same steps as you’ve done, without drawing anything and Sketchup doesn’t crash
Thanks, that helped. When clicking back in the model with the rectangle tool, the cursor froze, then a little while later my Mac restarted.
It’s going to be tricky to screen record that happening!
Strangely, the how to get started window is blank after the restart.
I will check in with the developer who is working on the other M3 related issues. Hopefully he will have made progress, and I can test whether the fix for those issues helps this one.
Of course I understand you can’t screen record because of the forced reboot.
The “good” news (if I can tell this…) is that you’re able to repdroduce the crash. Hope your developper have made progress on this 
He doesn’t yet have something for me to test. Hopefully soon.
I did do a screen recording, stopping at the point where I was about to close the Enscape window. It then didn’t crash! I don’t think that having a screen recording going all the time is a practical work around to the crash.
I let Support know that switching to the classic graphics engine is a work around for now.
Switching to the classic graphic engine is indeed a work around. But it is a waaayyyyy far slower than new GPU engine.
I’m working on a model of house with roof tiles (500 items), and with classic GPU engine this is laggy and very slow. With new GPU engine, it is really fast.
So… Waiting for the fix, I’ll modeling with “new GPU engine” and render with “classic GPU engine”. Not very convenient