Missing Game Textures
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- computer-graphics
Research direction
Start by comparing this report with linked issue #414 and inspect the attached savagewind.log for the repeated texture format errors. Reproduce the missing distant buildings with default and Ultra shadow resolution, then trace the relevant graphics handling from the log; done means the buildings render at default settings and the log no longer reports the texture as undrawable.
Written by the indexing model from the issue text.
Description
Before you start
- I'm on the latest release, and the bug still happens there.
- I searched the existing issues and this one isn't reported yet.
Savage Wind version
0.4.1-alpha.4 (latest)
Game version
1.9.0
Your PC
WIN10 - 22H2 | 9070XT 26.10.2 | 13600K
Where in the game
As soon as I started the new game
What happened, and how to make it happen again
new game, noticed that some textures were missing; after leaving the cave, I found that the buildings in the distance had disappeared.
Only after setting the shadow resolution to “Ultra” (4096) do the crude models appear.
In the default settings, they disappear entirely.
This happens whether the draw distance is set to “High” or left at the default setting.
I asked the AI about the following issue:
The log contains a large number of duplicate error messages:
texture #3061 (nvn fmt 0x49, 32x32x32 target 2) can't be drawn into as format 95: left out of the pass
This indicates that the emulator encountered a texture format incompatibility issue while converting the Switch’s NVN graphics API to Vulkan.
deleted cache/vk_pipelines.bin and cache/vk_precompiled.bin and recompiled, but the problem persists.
I’m not sure if this is a driver issue or a problem elsewhere.
Settings
60 fps - 90 fps 2560X1440
savagewind.log
log file
It seems to be the same issue as the one described here, but I’m not certain.
https://github.com/Revivedx/SavageWindRecomp/issues/414
Before sending
- This report contains no game files, keys, firmware, generated game code, save files or links to copies of the game.
- Dominant language
- C
- Stars
- 811
- Forks
- 37
- Avg merge
- 17m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Revivedx/SavageWindRecomp
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
Revivedx/SavageWindRecomp#488 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Revivedx/SavageWindRecomp#490 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Revivedx/SavageWindRecomp#486 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Revivedx/SavageWindRecomp#485 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Revivedx/SavageWindRecomp#484 ·
Maintainers usually reply within 1 day
All issues in Revivedx/SavageWindRecomp
Similar issues
-
5700模组网络优先级问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
luainkernel/lunatik#2372 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
ly05010419/MacNativeGames#1796 ·
Maintainers usually reply within 1 day
-
ZSTD_decompressStream accepts a Compressed_Block with Block_Size 0 that ZSTD_decompress rejectsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jniebuhr/gaggimate#1009 · 1 comment ·
Maintainers usually reply within 1 day