Communications inside blenderVR are organized through a master/slaves structure.
Although inside “virtual environment”, all nodes are equivalent, one node is the master.
The master node is the one that computes all scene interactions, updates the animations and dispatches them to the slaves.
This node have extra possibilities regarding slaves:
Playing blender animations on slaves has been reported to conflict with the update coming from the master and may produces flicking.
To avoid that (and restrict calculation of scene updates), slave nodes are suspended (
bge.logic.getCurrentScene().suspend()) during blenderVR runs. Even if you
resume() the scene, next execution of blenderVR will
suspend() it on the slaves.