VHToolkit

Home

Page tree

Versions Compared

Old Version 9

changes.mady.by.user Unknown User (jmoore)

Saved on

compared with

New Version Current

changes.mady.by.user Edward Fast

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Ogre is provided as a renderer with the toolkit Toolkit as an open source alternative to Unity, and as an example of SmartBody integration.  Ogre communicates with SmartBody using the Bonebus library for sending and receiving messages. uses SmartBody as a dll.  For more information on the Ogre3D engine, please see OgreSDK.

Users

Launching Ogre

In order to To launch Ogre,  you can select the 'Ogre' profile from the 'Profiles' menu option in the Launcher, or select Ogre as the renderer 'Visualization' section and hit 'Launch'.

Connecting with SmartBody

After selecting the Ogre profile and launching Ogre as a renderer, you can launch SmartBody by pressing 'Launch' in the SmartBody section. SmartBody will connect with Ogre on launching and you should see the virtual human animateBy default Ogre loads SmartBody as a dll and connects to it once it initializes.  It can also communicate with SmartBody when it's running as a separate process using the Bonebus protocol if this is specified in the config file for Ogre.

Developers

Ogre has been integrated as a rendering engine with the toolkit Toolkit as an example to show showing that alternative renderers can be used with the Toolkit.  It demonstrates how an open source engine can be integrated with the Toolkit.

Message API

List here all the (ActiveMQ) messages this module receives and sends. You can use this section to explain how this module fits within the overall architecture. 

Known Issues

Provide a list of known issues and peculiarities. Allow the reader to give feedback, probably by giving a link to the Support page.

FAQ

 

FAQ

 Probably just link to the appropriate section in the Main FAQ.