Versions Compared

Key

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

Table of Contents
maxLevel4

...

vhAssets is a collection of 3 redistributable Unity3D Engine package files named vhAssetsPackage, vhAssetsPackageOSX, and vhAssetsTestScenePackage.unityPackage.

The vhAssetsPackage and vhAssetsPackageOSX are redistributable Unity3D Engine package files that contain functionality for allowing SmartBody and VHMsg to work from within the Unity3D engine on windows and mac platforms, respectively. The vhAssetsTestScenePackage provides a sample scene that shows how to setup a SmartBody driven character in Unity using the vhAssetsPackage/vhAssetsPackageOSX packages.

The Toolkit uses Unity as it's primary rendering engine.  It can run in Unity Free or Unity Pro.  For Unity Free, we interface with SmartBody using 'bonebus mode'.  For Unity Pro, we access SmartBody directly using a .dll.

Some additional functionality that the vhAssetsPackage/vhAssetsPackageOSX contains is:

  • An extension of MonoBehaviour that allows order-dependent initialization and updates
  • SmartBody interface
  • VHMsg interface
  • VHCL Audio interface
  • Asset Post-processors that ease pipeline integration
  • Resolution independent UI classes
  • Interactive Debug Panel
  • Customizable Free Mouse Look
  • Ini file configuration
  • Loading Screen
  • Performance time demo tests
  • File Parsing
  • Application setup point
  • Customizable build process
  • Fps and Memory Debug Info

Any of these optional components are available when installing vhAssetsPackage or vhAssetsPackageOSX

Quick facts:

...

Unity

Unity is available within ICT.  The latest version is available through SVN here:

...

Upgrading .unitypackage files is a little more difficult.  This quote from the Unity docs explains it:

"For the cleanest possible upgrade, it should be considered to remove the old package contents first, as some scripts, effects or prefabs might have become deprecated or unneeded and Unity packages don't have a way of deleting (unneeded) files (but make sure to have a security copy of the old version available)."

The easiest way I've found is to use the approach the SVN docs recommend for vendor branch upgrades.

...