D5 3.1.0
Rhino LiveSync 1.1.3
Rhino 8
group geometry will crash rhino
when modelling, the moemnet i group anything my rhino crashed, un-useable. otherwise amazing stuff. please adjust or advice.
Hi @ivan1
Please send us your Rhino file so we can test it on our end. You may generate a link containing the Rhino file, then send it to me privately.
I can confirm this, and I have logs.
Same combination: Rhino 8.34.26223.11001 + D5 Render 3.1.1.0755 + D5 LiveSync for Rhino 1.1.3.0016 (the latest build). Windows 10 Pro 19045, i9-9900, 96 GB RAM, RTX 5070 Ti 16 GB.
Rhino does not show a crash dialog and does not ask to recover the file: the process simply disappears while LiveSync is connected. Six times in two days:
2026-10-19 01:03:24 - last command: Drag
2026-10-19 23:05:48 - last command: Copy
2026-10-20 00:15:17 - last command: ExtrudeCrv
2026-10-20 03:25:56 - last command: Drag
2026-10-20 04:07:09 - last command: Group <-- the case reported in this thread
2026-10-20 05:00:58 - last command: Drag
(times are local, UTC+2)
What the logs show:
1) In the plugin log (%LOCALAPPDATA%\d5_immerse\Saved\Logs\rhino.log) the last line written by each of those Rhino processes is <command> success from D5RhEventWatcher::OnEndCommand. CD5LiveSyncPlugIn::OnUnloadPlugIn (the SHUTDOWN line) is NEVER written. When I close Rhino normally, that line is always there. So the process is being terminated abruptly, it is not Rhino shutting down.
2) Windows sees nothing at all. No Application Error (1000), no Application Hang (1002), no Windows Error Reporting record, no crash dump - zero events for Rhino 8 in the last 15 days. That is why there is no warning and no dialog.
3) It is not memory or VRAM: 73 GB of 96 GB RAM free, no Resource-Exhaustion events, VRAM at 9.3 GB of 16.3 GB.
4) In the engine log (d5_immerse.log, times in UTC) D5 was busy and discarding the plugin’s messages at each of the three crashes I could cross-check:
03:25:56 - MeshSync in "syncMode = WholeImport, status = update" (re-importing the whole model)
04:07:09 - five straight seconds of
Warning: [MeshSync] FD5MeshSyncManager::IsReceiveMsg: msg ignored as status is <session>
with FD5MeshSyncManager::GetStatus returning status-2
05:00:58 - D5 was rendering a photo: AFusionSceneCaptureActor::Tick [FusionPhoto Done], and
FurnitureSyncAgent::ProcessCameraPosV3Command answering "RenderBusy" to Rhino
5) The only warning in the whole plugin log is this one, 50 minutes before one of the crashes:
d5Client.cpp:124#D5Client::getD5ProjectMetaData
[json.exception.parse_error.101] parse error at line 1, column 1: syntax error while parsing value
The plugin received an empty reply from D5 and tried to parse it as JSON. It looks like the plugin does not handle an empty/late answer from a busy D5.
So from here it does not look like the command itself (Group, Drag, Copy, ExtrudeCrv all did finish successfully - the log says “success”); it looks like Rhino dies right after the command, while the plugin is pushing the change to a D5 that is busy and refusing the message.
Two more details that may help you reproduce it:
- The scene is heavy: 14,530,856 triangles (from
MetaDataJsonSaved), Rhino autosave file 165 MB. - In two of the three cases I had two Rhino instances open at the same time, each one with its own MeshSync session against the same D5 (session ids 725570427, 732287498, 1578438135). The crash always hit the instance that was being edited.
I can send the full rhino.log and d5_immerse.log, and the Rhino file, by private message - just tell me where to upload them. Is there any way to disable the automatic push and keep only manual “Sync once”, as a workaround? Right now the only safe way to work is with LiveSync off.