Cooking a Home

Cooking a Home

1. Drag the old home (env.apk / .gltf.ovrscene / .opa) onto hsr_renderer.exe (or pass it on the command line). It loads and renders.
2. (Optional) Edit it: move/scale/hide objects, set the spawn point, add colliders. You can skip this entirely and port the home as-is.
3. Open the Cook tab and press COOK + SIGN + INSTALL.

Every control has a hover tooltip. The defaults are what most people want:

Option	Default	Meaning
Package	env's id	Android package id for the own-package (rooted) APK only. The spoof always uses Meta's haven2025 id and ignores this.
Auto-sign	✅ on	Sign the APKs so the Quest accepts them. Keep on.
Emit haven2025 spoof	✅ on	Also build the no-root APK. Keep on — it's the one most people install.
Animate skinned meshes (HZANIM)	☐ off	Experimental; can crash the env on device. Leave off unless testing.
Install to headset (auto)	✅ on	Cook → sign → install automatically (root-aware).
Wi-Fi IP / Device	blank	Wireless adb IP / a specific device serial. Blank = USB / default device.

What "COOK + SIGN + INSTALL" does

1. Cooks the (edited) scene into APK(s) in the cooked/ folder (editor sessions save to saved/).
2. Signs them.
3. Detects root on the connected headset and installs the right one automatically — see The Two APKs.

The status line at the bottom of the panel reports exactly what happened (which APK, signed or not, installed or not). Outputs are named:

• <env>_NoRoot-Spoof.apk — install on any (non-rooted) Quest.
• <env>_Rooted-System.apk — for rooted / dev headsets.

Manual cook (command line / headless)

Loading an env headless and cooking is supported; set HSR_NOINSTALL to skip the auto-install step in batch/CI runs. To sign an already-built APK someone sent you:

hsr_renderer.exe --sign <file>.apk      # -> <file>_signed.apk