Hello Vred Forum
I encounter a very strange bug for few days now:
If I have a variant set, set to not "Synchronize during collaboration" and I activate it during an active collaboration session, Vred will freeze and definitively stop responding.
This was not the case about 2 weeks ago (around 15th June 2026).
Affected version: VRED PRO 2026.2 (18.2.0.13133 - reproduced on 3 separate PCs)
Unaffected version: VRED PRO 2024.2.1 (16.2.1.12330 -works as intended)
Simple example to reproduce the bug:
- Open VRED 2026.2 with a new empty file
- Start a Collaboration session (being the only participant is enough to trigger the crash)
- Create a Variant Set and assign it any role you want (material switch, geometry switch, Py script etc...)
- In the Variant Set properties, disable synchronization ("Synchronize during Collaboration" = unchecked)
- Activate the variant set (via touch sensor or manual activation - does not matter here)
→ VRED crashes
Additional notes:
- The crash affects all non-synchronized variant sets, not just this specific case
- Without an active collaboration session, the variant set works normally
- Reproduced on 3 separate Windows 11 machines, with 2 different configs as follow
- AMD Ryzen Threadripper 3970X + Nvidia RTX A4000 + 128Gb Ram
- Intel(R) Xeon(R) W-2245 + Nvidia RTX A4000 + 64Gb Ram
Does anyone encountered this bug too?
Since it is a new bug (worked 2 weeks ago, crashes today) without any Vred update in this time frame, I suspect the issue might come from outside of Vred ? Driver update ? Visual c++ Update ?
