Cache generation

HeroBridge Standalone relies on pre-generated cache data to display available parts, presets, colors, body shapes, species, and expressions. If for some reason the cache generation has failed, or if no parts appear in the parts overview tool or Part Applier, this indicates the cache wasn’t created correctly.

Why we use cache

When HeroBridge Standalone is installed through the Package Manager, HeroBridge Standalone automatically attempts to export all cache data during setup. This process extracts data directly from the Sidekick database (including expressions from the demo animation controller) and stores it for runtime access.

This cache system is used for performance and compatibility reasons:

  • It prevents runtime lookups that could cause freezing or hitching when querying the Sidekick database.

  • It enables WebGL support, since the Sidekick database system isn’t supported on WebGL, but cached data is.

Troubleshooting steps

  1. Open the Sidekick Character Tool

    • If the tool opens and you don’t get errors about missing parts, the Sidekick installation is fine.

    • In this case, you can manually re-generate the HeroBridge Standalone cache.

  2. If the Sidekick Character Tool reports missing parts

    • This means your Sidekick installation is incomplete or corrupted.

    • You’ll need to completely reinstall Sidekick and HeroBridge.

Full reinstall steps

  1. Uninstall HeroBridge Standalone:

    • Go to Tools → HeroBridge Standalone → Uninstall HeroBridge Standalone

  2. Delete the Synty folder from your project.

  3. Follow the setup guide from the beginning, ensuring the Sidekick tool works before reinstalling HeroBridge Standalone.

Last updated