Quest Home Editor v0.10.17

Quest Home Editor v0.10.17

Fix: cook REJECTED (falls back to nuxd) on older Quest OS

Follow-up to v0.10.16. Cooks were still rejected on the Oct-2023 Quest OS (Quest 3 UP1A.231005) — the env fell back to nuxd instead of loading.

Root cause (libshell, IDA-confirmed): the cook emitted boundsCenter/boundsHalfSize of MeshPartBoundsOverride as a 3-field {x,y,z}, but the field is a Vec4. Newer OS parsers leniently accepted the short form (defaulting w=0); the older OS parser is strict and emits Core: Expected:'Vec4', Found:'{x,y,z}', which aborts the content.hstf template JSON load (ErrorMissingData) and rejects the whole env.

Fix: emit both as full Vec4 ("w":0) — passes the strict parser on old and new OS (kept version:0 from v0.10.16). Verified on-device: re-cooked steam_void now installs, selects, and loads on the Oct-2023 Quest 3 (previously rejected → nuxd).

New: "Anti-cull bounds" cook toggle

Cook panel → "Anti-cull bounds (animated meshes stay visible)" (persisted). Leave ON normally; turn it OFF to drop MeshPartBoundsOverride entirely if any headset still chokes on it, so the env always loads.

If a past cook was rejected or black on an older headset, re-cook it with this build.