Running on an Apple M4 laptop, Ive had success running a number of windows games via Fusion, however I run into this crash when trying to run 'Satisfactory':
2025-08-08T12:11:26.843Z In(05) vcpu-3 Guest: vm3d: VM3DDevAdapterGrowOTableItem: Grow OTable 0 from 16384 entries to 32768 entries, use 128 pages
2025-08-08T12:11:27.166Z In(05) vcpu-3 Guest: vm3d: VM3DDevAdapterGrowOTableItem: Grow OTable 1 from 32768 entries to 65536 entries, use 1024 pages
2025-08-08T12:11:30.970Z In(05) vcpu-1 Guest: vm3d: VM3DDevAdapterGrowOTableItem: Grow OTable 0 from 32768 entries to 65536 entries, use 256 pages
2025-08-08T12:11:31.632Z In(05) vcpu-3 Guest: vm3d: VM3DDevAdapterGrowOTableItem: Grow OTable 1 from 65536 entries to 131072 entries, use 2048 pages
2025-08-08T12:11:40.161Z Wa(03) svga mksSandboxLog: MTLRenderer: shader resource declared as 'uint' but bound as 'float'
2025-08-08T12:11:42.446Z In(05) vcpu-3 Guest: vm3d: VM3DDevAdapterGrowOTableItem: Grow OTable 1 from 131072 entries to 262144 entries, use 4096 pages
2025-08-08T12:12:32.378Z In(05) vmx GuestRpcSendTimedOut: message to toolbox timed out.
2025-08-08T12:12:32.378Z In(05) vmx Tools: [AppStatus] Last heartbeat value 169 (last received 6s ago)
2025-08-08T12:12:32.378Z In(05) vmx TOOLS: appName=toolbox, oldStatus=1, status=2, guestInitiated=0.
2025-08-08T12:12:35.778Z In(05) vmx GuestRpcSendTimedOut: message to toolbox-dnd timed out.
2025-08-08T12:12:35.778Z In(05) vmx TOOLS: appName=toolbox-dnd, oldStatus=1, status=2, guestInitiated=0.
2025-08-08T12:12:39.800Z In(05) vmx GuestRpcSendTimedOut: message to toolbox-dnd timed out.
2025-08-08T12:12:43.901Z In(05) vcpu-0 Tools: [AppStatus] Last heartbeat value 170 (last received 0s ago)
2025-08-08T12:12:43.901Z In(05) vcpu-0 TOOLS: appName=toolbox, oldStatus=2, status=1, guestInitiated=0.
2025-08-08T12:12:50.794Z In(05) vcpu-1 TOOLS: appName=toolbox-dnd, oldStatus=2, status=1, guestInitiated=0.
2025-08-08T12:12:53.219Z In(05) mks SOCKET 1 (69) recv detected remote shutdown
2025-08-08T12:12:53.219Z In(05) mks ISBRendererComm: Remote Disconnect: socket closed.
2025-08-08T12:12:53.219Z Wa(03) mks mksSandboxLog: MTLRenderer: Error during command buffer execution: Caused GPU Address Fault Error (0000000b:kIOGPUCommandBufferCallbackErrorPageFault)
2025-08-08T12:12:53.219Z Wa(03) mks mksSandboxLog: PANIC: Error during command buffer execution: Caused GPU Address Fault Error (0000000b:kIOGPUCommandBufferCallbackErrorPageFault)
The `Wa(03) svga mksSandboxLog: MTLRenderer: shader resource declared as 'uint' but bound as 'float'` / `Wa(03) mks mksSandboxLog: MTLRenderer: Error during command buffer execution: Caused GPU Address Fault Error (0000000b:kIOGPUCommandBufferCallbackErrorPageFault)` combo seems suspicious, and makes me think there may be a bug in how the Metal API is being called (ie, if that 'uint' that is declared is used to point at an index, but the value passed to it is actually represented as a 'float' in memory -- in other words, uint(15) == 0x0F, but 15.0f might look more like 0x41 70 00 00 in memory, and if passed directly ends up with 15.0f being converted to uint(1097859072) !! )