Quest Home Editor v0.10.10
Builds on v0.10.9's vista fix. If your ported home shows a black/empty environment or "the vista neutralized but my home didn't show" — this is for you.
Why the home showed black / didn't appear
A footprint home is loaded together with its paired vista. So if the vista's scene fails to load, the shell rejects the whole environment and falls back to nuxd — which renders as a dark/black void. That's what "neutralized the vista but my custom home didn't show" actually was: the older, broken empty vista was still rejecting and dragging your home down with it. v0.10.9 fixed the empty vista; this release makes sure a broken one gets repaired automatically.
Auto-fix a broken vista on connect
When you plug in your Quest, the editor now checks the recent logcat for a vista that rejected on load and, if it finds one, automatically re-installs the current (fixed) invisible vista and reloads your home — no button press. It runs once per device, and only reloads the headset if it has to. New toggle "Auto-fix a broken vista when the Quest connects" (on by default).
What to do
- Update to v0.10.10.
- Re-cook + install your home (COOK + SIGN + INSTALL), or just plug in the Quest and let the auto-fix run.
- Your footprint home loads with an empty (invisible) vista behind it — no scenery, no black void.
Linux/macOS: build from source (bash QuestHomeEditor/build_linux.sh).