Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

By default, only the Gavam and CLM facetrackers are turned on (for the Toolkit; otherwise only the Gavam is turned on).

Notes:

...

.  If you wish to change the configuration for running other modules

...

:

  • Edit \bin\multisense\ssi_vhmsger\bin\config.ini and change the "useXXXX" parameter to "true" to make a module work.
  • If the dependencies for the module are not setup correctly, the ssi_vhmsger will crash.
  • If running FAAST, make sure the "useKinect" as well as "useFAAST" parameters are both "true" in the config.ini.
  • A webcam must be connected to the computer.
  • If the application fails to start, one of the dependencies might be missing.
  • ssi_vhmsger will not exist exit when the "Kill" button from the launcher is clicked. Also, if it's killed from the launcher, the ssi tool will turn yellow.

...

  • Run it from the Launcher (go to the 'Perception Components' tab)
  • Navigate to \bin\multisense\PerceptionTest\ and run "PerceptionTest.exe".

Please contact either Unlicensed user or Unlicensed user if you have any issues in running the application.

Message API

Sends:

  • vrComponent

...

Receives:

  • vrPerception
  • vrPerceptionProtocol
  • vrAllCall
  • vrKillComponent (does not react to it yet)

Known Issues

  • The MultiSense Application currently does not listen to the vrKillComponent message. The application must be manually closed; attempts to kill it from the Launcher will cause it to highlight yellow and not close.
  • If the application does not appear to start up, make sure your camera is working properly. Also, if there is camera.option file present at the location "\bin\multisense\ssi_vhmsger\bin", delete it and try to run the application again. If there is a problem with running MultiSense, please contact us at vh-support@ict.usc.edu.
  • If a big red X appears on the screen after Gavam GAVAM is enable, it means that Gavam GAVAM is not able to detect the face properly. The application needs to be restarted; currently, there is no other way to reset. The CLM tracker can be restarted, though, by right clicking the output window.

...