1. ensure that your motion capture system is streaming identified markers before starting visual3d.
2. start visual3d and switch to the real-time tab.

rt_v3d_1.png

3. if you don't see any plugins listed make sure you 1) selected “built-in rt” 2) have installed the plugins.
(note: the sdk's for mac and optitrack/motive do not support win7-64.)
4. click on the plugin for your system.

rt_v3d_2.png

5. fill out the dialog with the information visual3d needs for your specific system (see next section) and click “done”.
6. visual3d will connect to the real-time stream originating from that system. some systems take a few seconds to begin streaming.

the fewer processes you have running the faster your computer will run. close all applications and processing that are unnecessary to biofeedback (only your motion capture software and visual3d should be running).

if you're having trouble with lag - try streaming less data. if you have targets on the full body - but are only interested in the ankle angle, try collecting only the necessary data. the more work your computer has to do - the slower it will run.

a file dialog will allow you to select the c3d file.

rt_dialog_c3d.png

the server and client addresses should be the same unless you are streaming from a different machine.

ensure that your settings in cortex are correct for streaming:

rt_dialog_cortex_settings.png

ensure that the selected cal file is correct. picking the wrong file will cause incorrect force plate data and bad forces.

rt_dialog_mac.png

the interface address is the ip address of the pc running motive. the local and multicast addresses should be the same (localhost, 127.0.0.1, or the motive system ip).

rt_dialog_motive.png

ensure that the selected command and data ports match the ones from motive. pay particular attention to the circled settings.

rt_motive_datapane.png rt_motive_showadvanced.png rt_motive_advanced.png

make sure to select “play with real-time output” when streaming from qtm.

rt_qualisys_play.png

the qtm server address should be ip address of the machine running qtm. this may be localhost or 127.0.0.1.

rt_dialog_qtm.png

we recommend using the default port (22222). if for some reason you need to change it, ensure that the port matches your settings.

rt_qualisys_options.png

the nexus server address should be localhost, 127.0.0.1 or the ip address of the machine running nexus.

ensure that the selected system file is correct. picking the wrong file will cause incorrect force plate data and bad forces.

vicon_connect_to_server.png

markers not showing up?
- make sure that the markers in your motion capture system have labels.
- ensure that you're getting data by going to view > view real time data.
rt_plugins_view_rt_data.png
- open edit > preferences in visual3d and ensure that “targets” is checked in the 3d view options tab.
- there are icons in visual3d's toolbar that toggle the display of labels, bones, and segments.

missing / incorrect forces?

- for qtm, make sure that you are streaming from a .qtm file, not .c3d.
- verify your system is actually streaming the force data.
- ensure that the correct system or calibration file was selected if using nexus or cortex.

missing plug-ins?

if you don't see your plugins listed in visual3d, make sure:
- you selected “built-in rt” on the real-time tab
- you have downloaded and installed the plugins
- you are not running win 7 64-bit with mac and optitrack/motive since they do not support win7-64.)
- plug-in's directory has not been changed (edit→preferences; default folders)

}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}