Has the software developer SketchUp fixed them yet? Currently, this situation persists and has a significant impact on work.
during the weekend ?
no.
I have the EXAKT same problem
The tip from @colin did help. No problem with my M3 Max after setting Antialaising to 0x. Thank You! 
1 Like
Agreed, this tip (antialiasing to 0x) seemed to solve my crash problems.
Thanks
Russ
3 Likes
Everyone - I got a tip from SU support to do the following on SU 2024 because there must be some issue with the new graphics engine and the M3 series. So far so good and no crashes.
yes. since the problem is with the new engine, returning to the old engine fixes it.
itâs not really a fix. itâs pretty much returning to sketchup 2023.
Colin also gave a better solution a bit before, using the new engine with 0x AA allows you to use ambiant occlusion and a faster modelling without crashes.
Good I found this topic. Recently got my new MacBook Pro with M3 Pro chip and when I updated my SketchUp, it crashed almost immediately.
Following this topic for sure and trying the settings @mwenvironments got suggested.
If it fixes it, great. If it doesnât, if you can share a file to repro the issue, please do.
Barry
1 Like
Do you mean sending the bug splat report when it crashes?
Yes, Bugsplats on crashes (and PM me to look at them) or if you get a kernel panic, paste that in here. Thanks so much for your help.
b
Continuing the discussion from Panic and crash in SketchUp 2024 for M3 16" MacBook Pro:
Hi, same here with sketchup 2024 and ânew GPU engineâ selected.
Crash that ends up to a forced reboot occurs at any time (with or w/o Enscape, but I feel that using Enscape âaccelerateâ the crash/reboot).
Tried setting âFSAAâ to â0xâ but no luck, crashes always occurs.
Tried setting âlegacy GPU engineâ : Seems to work because not encountered any crashes since this morning.
Iâm waiting for a bug fix
Thereâs a real problem with the new graphics engine: pipeline structure, command buffers. It appears some calls from the graphics engine to the Metal API are pipelining/transforming correctly â shader/shader bindings, some textures, some buffers look functional. The problems start after entry point with commands, queues, instruction sets, barriers etc., â pipeline structure to GPU or swapchain between macOS WindowServer process and the call instance(s) to the Metal API.
I donât see any kernel extensions (kexts) or #includes to a kexts collection (AuxKC) from the SU24 install. Plus, the SU24 install didnât require a reboot and user permissions. I canât think of a reason SU would need to bypass the OS layers, API/Framework calls and communicate on a low-level directly with the kernel anyway.
From my current understanding Trimble has brought in their graphics engine developer and (s)he are working to debug/port correctly/update the code. I donât know if this is a native or third-party to their agile sdlc. Hopefully after cleaning up and running test builds â weâll have a deployable stable build shortly.
How can I send the macOS crash log ? I canât find a way to send it.
Thanks
Does anyone encountering the âkernel panic / Forced rebootâ use Enscape plugin with sketchup 2024 ?
After a whole day using Sketchup 2024 ânew GPU Engineâ without Enscape plugin (activated, but Enscape not running), I have no crash / kernel panic / Forced reboot.
So I also put these setting in sketchup pro 2024 in âgraphicsâ section (sorry in French)
For this time, it seems to work great. And I can say that the new GPU Engine improve significantly performances, specifically in case of +200 object (roof tiles)
Last results of my tests during the week end â It seems that as soon as something is âconnectedâ to sketchup (twin motion or Enscape for exemple) make Sketchup freeze, then force a reboot of the Mac.
It seems to come from iomfb_driver, below an extract of the kernel panic report from macOS
panic(cpu 0 caller 0xfffffe001983bddc): DCPEXT1 PANIC - program_swap: Async Swap request landing on unsupported platform. Force panic
- iomfb_driver(10)
program_swap: Async Swap request landing on unsupported platform. Force panic
RTKit: RTKit-2419.101.1.release - Client: local-t602xdcp.RELEASE
!UUID: 10178379-fe92-3317-9095-ad703b8bb255
Time: 0x0000017951774df2
DCP = Display CoProcessor
IOMFB = I/O (Input/Output) Mobile Frame Buffer (manages screen framebuffer (i.e., screen (re)draw memory)
RTKit = Appleâs RealTime Embedded OS
Itâs things like what weâre experiencing that bring one up to speed on whatâs happening in a broader sense. It seems there are many new reports of a kernel panic involving these systems â see Google or MacbookPro 16 M3 Pro DCP PANIC - Apple Community.
Apple is serious about privacy and security. Starting with Sonoma 14.4 onwards Apple has patched a security exploit in the RTKit which would allow an attacker to bypass kernel memory protections. See: About the security content of macOS Sonoma 14.4 - Apple Support
Even previous to this Apple had âwalled offâ the kernel from potential exploits/attackers. No more frivolous kernel extensions communicating directly with the kernel or querying its sensitive data. Now, a user must implicitly approve a kernel extension in recovery mode. Just an example for music production: https://www.sweetwater.com/sweetcare/articles/kernel-extensions-on-mac-with-apple-silicon/
So, what us SU24 Mac users are waiting on is for Trimble to update the code in regards to Apple shutting the door on various parts of it in Sonoma 14.4+. I concur that when these reports were first starting to be shared after running the new SU24 there was unusual pushback, but the good news is: Theyâre now aware and working on it. It shouldnât be long.
1 Like
Checking if I understand this right - are you saying that something in the new graphics engine in SketchUp is triggering an issue in Sonoma, that Apple have a fix for in 14.4? Or, is it that the thing SketchUp is doing wrong already will start to cause kernel panics in 14.4 and later, until the technique is changed in SketchUp?
BTW, Iâm partly testing in Sonoma 14.5, and havenât had kernel panics.
Hi, I donât know what @swhite would exactly says, but as far as I know by doing several different tests this week end, I can for now says that Sketchup is triggering kernel panic with a hard forced reboot with new gpu engine AND with a render plugin (can do it every time with Enscape, sometimes with twin motion. But twin motion is not sketchup 2024 compatible)
I also start a support ticket with chaos Enscape, but really donât know if the bug is related to Sketchup, Enscape or macOS.
How could I help you to investigate this bug ?
You already started! I can try installing the Enscape extension and see if I then get crashing and rebooting.
Which Sonoma are you using?