Emulator Issues #13805
open
Rogue Squadron Hoth terrain texture issue
0%
Description
Game Name?
Star Wars: Rogue Squadron II
Game ID? (right click the game in the game list, Properties, Info tab)
GSWE64
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
[Put MD5 Hash here]
What's the problem? Describe what went wrong.
Terrain texture issues on Battle of Hoth level
What steps will reproduce the problem?
Play Battle of Hoth level on SD Gen 3 (A750) based mobile devices using the device's default GPU drivers or any other official Qualcomm driver.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
[Yes 2503a-508 is the last one I tested]
Is the issue present in the latest release? For future reference, please also write down the version number of the latest release.
[Yes 2503a]
If the issue isn't present in the latest release, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
[First broken version number here (if applicable)]
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]
What are your PC specifications? (CPU, GPU, Operating System, more)
Rog Phone 8, Android 15, Qualcomm Snapdragon 8 gen 3, Adreno 750 GPU, 16GB ram, 256GB storage
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
This is the same issue that affects the Holoska level in Sonic Unleashed for the Wii, and the only current workaround/fix for Adreno 750 users is the Turnip v25.2.0 forced gmem drivers (release 2 and up).
There is also a minor issue in Rogue Squadron III involving the clouds on various levels not being rendered correctly that is fixed using the same turnip drivers. Oddly though, that version of the Battle of Hoth is not affected like RS 2 and Sonic Unleashed are.
Files
Updated by StLouisCPhT 8 months ago
I forgot to mention that is texture issue occurs on both OpenGL and Vulkan renderers, and the turnip driver only works for Vulkan, not OpenGL.
Updated by StLouisCPhT 8 months ago
Turning on manual texture sampling fixes this issue when using either OpenGL or Vulkan renderers, without the need for alternate GPU drivers.
(Also fixes the clouds not being rendered on Rogue Squadron III)
Updated by StLouisCPhT 6 months ago
After lots of random experimentation, the following workaround seems to be best for RS2 on Snapdragon 8 Gen 3 devices.
Turnip drivers v25.2.0 R10 GMEM
[Video_Hacks]
DeferEFBCopies = False
EFBToTextureEnable = True
EFBEmulateFormatChanges = True
ImmediateXFBEnable = False
SkipDuplicateXFBs = True
[Video_Settings]
SaveTextureCacheToState = True
Updated by StLouisCPhT 3 months ago
- File Screenshot_20251005-173915_Dolphin_Emulator.jpg Screenshot_20251005-173915_Dolphin_Emulator.jpg added
Oh yay. Selecting Vulkan and Hybrid Ubershaders without any other changes to settings is starting to properly display RS2 snow textures on the default Adreno 750 system drivers.
It only lasts a second, then the messed up textures take over and all subsequent loads only provide the messed up textures - unless you completely delete all the saved textures and start over.
I still need to test the other games that have reported the snow texture issue.
I guess it's time for me to start tracing back to when this started happening (or if I just somehow either 1) never thought to test this combination before or 2) I did, but it was a blink and miss it moment).
I'm attaching a screenshot I took that managed to also contain a thumbnail of the screenshot I took just prior with the working textures.
Updated by JosJuice 3 months ago
That's because hybrid ubershaders uses ubershaders while waiting for specialized shaders to compile, and then switches to specialized shaders. The bug is only in the specialized shaders. If you want to use the ubershaders all the time, you can do that by choosing exclusive ubershaders, but that's even slower than manual texture sampling.