Cache and Character Packs
Automatic Cache Export
When HeroBridge is installed through the Package Manager, it tries to generate the required cache during initial setup. It exports this data from the Sidekick database. Expressions come from the runtime facial demo animation controller.
- Parts
- Presets
- Colors
- Body shapes
- Species
- Expressions
Why HeroBridge Uses a Cache
The cache avoids runtime database access. It prevents freezes caused by live database queries and supports WebGL, where SQLite databases are not compatible.
Generate the Cache Manually
Generate or regenerate cache data at any time from:
Tools > HeroBridge Standalone > Generate CacheSidekick Icon Cache
During cache generation, HeroBridge asks whether to generate the Sidekick Icon Cache. This cache is required by the Parts Overview Tool and the Sidekick Part Applier.
When you generate it, HeroBridge asks you to save unsaved scene changes, opens a temporary scene, briefly enters Play Mode to create preview icons, then restores your previous scene.
You can skip this step and generate it later with Tools > HeroBridge Standalone > Generate Cache.
Check Sidekick Meshes
HeroBridge checks Sidekick meshes to make sure Read/Write is enabled. All Sidekick meshes need Read/Write access. Some meshes have this disabled by default, which can make HeroBridge features fail or behave incorrectly.
When HeroBridge finds a problem, it can fix the mesh settings for you. Run the check manually from:
Tools > HeroBridge Standalone > Check MeshesAdd a New Sidekick Character Pack
After importing a new Sidekick Modular Character Pack, regenerate the HeroBridge cache:
Tools > HeroBridge Standalone > Generate CacheThis lets HeroBridge find parts, presets, colors, body shapes, species, and expressions from the new pack.