vizconnect vs(?) vizcave

[istarion]

hey all

I have access to a 3-wall cave system and am now trying to figure out how to efficiently program for that thing.

What are the jobs of the vizconnect and vizcave modules in this setup? Do I need only one or both?

The one thing I could discern is that vizconenct sets up / connects the head and wand trackers, but not what it does with them and how to access them. for example to disable wand inputs during certain times in a vr run.

thanks and cheers

[Jeff]

The vizconnect cave and powerwall options generate the vizcave code for you. What are the three walls and is a separate machine used to render each wall?

[istarion]

The walls are left, center, and right, all driven by a single machine.

[Jeff]

Then you can use the corner cave manual configuration option and turn both right and left walls to on.

[istarion]

Yes, I have a working config that I can load with vizconnect.go(config).
My question is more how to find out what handles the vizconnect offers and how to use them. For example running the basicLinking script from vizard -> getting started -> Linking with a vizconnect.go(config) does not work as there is no longer a viz.MainView that is usable/accessible (in bind view to avatar, avatar to pointer is still ok). What takes its place?

[Jeff]

In a vizconnect application, view updates are based on the transforms of parent nodes (e.g. trackers, transports) in the scenegraph. Commands that set the view or link the view to another object get overwritten. You can use a vizconnect viewpoint (http://forum.worldviz.com/showthread.php?t=5331) object to help set the view. This forces the view to a location while taking into account the parent hierarchy. Moving the user to a general location within the environment can be accomplished by setting the position of a parent transport’s node3D object. In this case, the view position is equal to the transport position plus offsets from other parent nodes:

transportNode = vizconnect.getTransport('main_transport').getNode3 d()
transportNode.setPosition([0,0,20])

[istarion]

That's what I was looking for, thanks.