Mismatch using Variant Sets in Collaboration Mode

[fbruchD4CS2]

I have created Variant Sets via the Simple UI Capture feature and would like to switch between these Variant Sets when in Collaboration Mode with another PC. However, for some of the VSets, certain nodes get hidden for the Slave PC when the Master activates the VSet. These nodes are neither in the Geometry, nor in the Script tab of the VSet. Therefore, I don't understand why they get disabled on the Slave PC, but enabled on the Master PC. 

EDIT: After some more testing, it seems to me as if the VSet gets handled differently for the Slave than for the Master PC: 

The Master PC enables ALL nodes and then disables the ones that are specified in the Geometry or Script Tab of the VSet. The Slave PC ONLY does whatever is specified in the VSet. Nodes that were inactive before remain inactive, whereas they get set to active on the Master PC if not specified otherwise. Can anyone confirm this and tell me what the best way is to fix this problem?

I am using VREDPro 2019.2 and the session loaded on either PC is exactly identical. 

Thank you in advance!

Kind Regards, 

Florian

[marcus_fritzen]

Hi Florian,

that's weird. You are using the identical scene (with the created vsets from the simple ui) on all machines? When the master executes a vset, the same vset is executed on the slave plus some additional state checking.

It would be very helpful if you could provide a simple demo scene with which the problem can be reproduced.

Thx,

Marcus

[fbruchD4CS2]

Hi Marcus, 

Thanks for your reply! I attached a simple session that is able to demonstrate the issue. 

I created the VariantSet "Disable Green Sphere" with the SimpleUI. When you activate it as the Master, every node except the green sphere will be enabled, while the green sphere will be disabled. On the Slave PC however (if Master activates the VSet), all that happens is that the green sphere will be disabled. Every other node remains in the state it was in before, disabled nodes will remain disabled. 

Let me know if you experience the same issue with this session (and any other session using Simple UI VSets and Collaboration really). 

EDIT: Every time I try to attach the vpb and Post it deletes the attachment before I can post it. Is there another way I can send it to you? It's only 2MB.

Kind regards, 

Florian

[marcus_fritzen]

Yeah, unfortunately VPB files get filtered. Try using zip. Thx

[fbruchD4CS2]

Got it, zip file should be attached now!

[marcus_fritzen]

I can reproduce the issue and added a bug-report for it. Unfortunately, I can't tell when it'll be fixed.

Cheers,
Marcus

[fbruchD4CS2]

Okay, thanks! It's a good start. Will I be informed if anything new comes up?

[marcus_fritzen]

I attached the link to this thread to the ticket with the note to update the thread once the issue is resolved.

Cheers,

Marcus

[fbruchD4CS2]

Perfect, thanks a lot, Marcus!

Cheers, 

Florian

[rothm · Accepted solution]

Hello,

the captured states are currently not correctly updated when the variant set is switched during a collaboration session. Until this is fixed, the variant set could be switched with a synchronized python command.

vrSessionService.sendPython("selectVariantSet('Disable Green Sphere')")

In this case the captured states are updated correctly.

Marcus

[fbruchD4CS2]

This works, thank you very much!

Kind regards,

Florian