Hello, VAQ experts
How can this frustrating issue be resolved?
This directly makes it difficult to manage and render projects under review in the current version.
The project needs to be finalized to avoid chaos in overall scene management.
In a previous discussion (Issue of Visualarq object connect to twinmotion) regarding the data linkage between Twinmotion and VAQ, there has been a new and clearer discovery.
In the GUID aspect, it appears that VAQ objects differ from native Rhino objects in their record-keeping behavior. This results in TM, during real-time connections, capturing GUIDs that generate nonexistent instances and positions.
Recorded examples demonstrate inconsistent object behaviors.