Quest Home Editor v0.10.4
⚠️ Critical: cooking was broken since v0.10.1 — this fixes it
If you're on v0.10.1–v0.10.3, every cook produced a ~3.5 KB APK that wouldn't install. The built-in APK signer (added in v0.10.1) was gutting every cooked APK — it read each zip entry's size from the wrong place (miniz writes those sizes to the central directory, not the local header), so it copied zero file data into the signed APK. Update to v0.10.4 and re-cook — output APKs are full-size again (verified: a dome cook is now 21 MB, not 3.5 KB).
🫥 Invisible vistas — home loads with no vista scenery
Ported homes spoof as a footprint, so the shell always force-pairs a companion vista behind your home. New this release: neutralize every installed vista by replacing its scene with an empty one.
- Pulls the real vista off your headset, keeps its exact manifest/package/resources, and swaps only its scene for a 0-mesh empty one — then re-signs and reinstalls. So the paired vista loads fine (no crash, no fallback) but renders nothing.
- Verified against libshell in IDA: the shell accepts a vista as long as its package is installed and
assets/scene.zipexists — it never checks the scene has content. An empty scene is accepted, not rejected. - On by default in the Cook tab ("Neutralize vistas"), plus a standalone "Neutralize vistas now" button (no re-cook) with a per-vista progress bar. Works without root (vistas are store apps). Restore a vista anytime by reinstalling it from the store.
Fixes
- Tooltip text no longer overflows its box (every line was drawn one text-height too low).
Linux/macOS: build from source (bash QuestHomeEditor/build_linux.sh) — the cook fix is in shared C++ and applies to every OS.