Table of Contents |
---|
Ogre is provided as a renderer with the toolkit Toolkit as an opensource 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. Ogre uses SmartBody as a dll. For more information on the Ogre3D engine, please see OgreSDK.
In order to To launch Ogre, you can select the 'Ogre' profile from the 'Profiles' menu option and then launch the renderer OR you can in the Launcher, or select Ogre as a renderer in the launcher under the Visualization section and hit launch after providing the command line argument options you wantthe renderer 'Visualization' section and hit 'Launch'.
...
By 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.
Ogre has been integrated as a rendering engine with the Toolkit as an example showing that alternative renderers can be used with the Toolkit. It demonstrates how an open source engine can be integrated with the Toolkit.
After selecting the Ogre profile and launching Ogre as a renderer, you can launch smartbody by hitting launch in the smartbody section. Smartbody will connect with Ogre on launching and you should see the virtual human character animate.
Section aimed at developers. Use to explain the architecture of the component, how to make changes, where files are located, what caveats exists, etc. Should at least contain a section on the messages received and send.
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.
Provide a list of known issues and peculiarities. Allow the reader to give feedback, probably by giving a link to the Support page.
Probably just link to the appropriate section in the Main FAQ.