Great Fairy grotto before the Forest Temple: cave walls and floor are not drawn #692
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#692
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Builder version
Source build of
mainas of today (with the merges up to #598, #566, #638, #645)How you built
From source, Windows 11, RTX 3060 Ti, Ryzen 5 3600
The error
In the Great Fairy's grotto on the way to the Forest Temple (Lost Woods / Sacred Forest Meadow side), the cave's walls and floor are not drawn: everything around is see-through, with only the fog, the light shaft and the fountain left, and Link standing in the dark.
In that room the counters show 0 texture handles without a registered texture, 0 storage buffers left unbound, 0 programs failed, ~514 draws a frame and 0 draws skipped, so it does not look like a missing texture.
HOOKSHOT_OCCLUSION_OFF=1changes nothing. It was the same before today's merges. I can attach a screenshot and the log.Sounds like you have the incomplete dump (23.3 Gb) instead of the complete 23.8Gb.
Can you confirm your dump is the full one ?
I have the same issue and it looks like i have the partial dump (23.3GB). I didn't know there was a partial version so this is good information. Now to find the complete dump.
Yep! the complete version fixed my issue and I can see walls in this area now.
Closing: another player with the same missing walls fixed it by using the complete 23.8 GB dump instead of the 23.3 GB one. Please reopen if it still happens with a complete dump.
Same symptom here (Great Fairy Fountain floor not drawn) with a 25,020,741,061-byte (23.30 GiB) .nup, i.e. the "23.3" one mentioned above.
python nx2/nup.py <file>.nup --verify(read-only, in the builder's tools folder) reports 3 members whose compressed data is all zeros (it starts with 00 00 00 00 instead of the Zstd header 28 b5 2f fd):/romfs/Tex/CmnTex_Map_Soil_FairyFountain_Floor_D_Nrm.bntx.zs/romfs/Tex/Rock_WaterTemple_Gate_M_01_Nrm.bntx.zs(matches #718)/romfs/Tex/RBake_Scene_GanonStage_G_2_1_d0_t0.bntx.zsThe other 186,589 records pass that check. Caveat: these 3 files add up to ~2.6 MB, far less than the ~0.5 GB difference to the full dump, and
--verifyonly checks the .zs headers, so the partial dump probably differs in more than these 3 members. Suggestion: run the same verification after unpacking and warn when a member is all zeros.