Emulator Issues #11309
closedHeatseeker Text HUD disappearing
0%
Description
Game Name?
Heatseeker
Game ID? (right click the game in the game list, properties, info tab)
RHSE36
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
e6facf00fda06b87af7e840230cb04da
What's the problem? Describe what went wrong.
Text on the HUD randomly disappears, like the name of the missiles, the labels for the health bar and speed, etc.
What steps will reproduce the problem?
Playing the game for a sufficient amount of time, though sometimes it'd occur immediately on a mission. The screenshots provided are of the third level. Mostly occurs randomly, however.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
5.0-8512
Is the issue present in the latest stable version?
No, Dolphin 5.0 itself seems to work fine, though I haven't extensively tested it.
If the issue isn't present in the latest stable version, 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.)
Don't know how to use this.
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
Two screen shots attached, first in-game, the second in pause menu. All text for the menus is gone. However, subtitles and mission objectives still appear.
What are your PC specifications? (CPU, GPU, Operating System, more)
CPU: Intel Core i7-4720HQ 2.6GHz
GPU: Nvidia 980M
OS: Windows 10
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Only the screenshots.
Files
Updated by Techjar over 6 years ago
Please bisect and provide a fifolog, without that we can't do much. Instructions for both of these can be found at the links in the template.
Updated by GhostAngel over 6 years ago
I did try both, but since the appearance of this bug seems completely random, I don't notice it through bisecting various builds as the test ends before I play long enough for it to appear, and I could only possibly record it via fifoplayer after it appears, again due to randomness, which I don't know if it'll help.
It just seems to come up if I play it enough, and randomly so, but often enough to be noticeable.
Updated by Techjar over 6 years ago
Based on the other issue you reported, it seems like you may have a graphics driver or hardware issue.
Updated by GhostAngel over 6 years ago
Entirely possible, though it's only these two games that have issues. And only on the most recent build as going back to the stable build of Dolphin 5.0 seemed fine. Every other game I used, like all the James Bond games (aside from the VP6 video lines issue), the Godzilla games, Star Wars games like Rogue Squadron 2 or Bounty Hunter etc. all worked fine. Just these two creates problems. Heatseeker's was random, though King Kong was replicatable to me.
I'm also noticing that Dolphin Bisect seems to crash when I switch builds, which probably was it stopping rather than it automatically changing. What would you recommend I do? I've been lurking and scouring different forums for these issues and when I couldn't find it, I reported them here.
Updated by Techjar over 6 years ago
Ah, okay, maybe not a driver/hardware issue then if it's only affecting these games. As for the bisect tool, you are using the latest version (1.2.1 at this time), correct? If so, I'm not sure. Will have to ask Helios about it.
Updated by GhostAngel over 6 years ago
Yeah, specifically off Github. I never used it or Fifoplayer before, so I had to learn how to use it a bit, but running into that issue. And with Heatseeker, again, it's entirely random. I could play one mission and have nothing go wrong, then replay the same mission and immediately have bugs, and then replay the same mission and have it start fine, but then bug out again. The last time I tested, I actually had an opposite situation happen where the text stayed, but all the visuals on the HUD bugged out. Not disappeared, but just bugged out and displaying improperly. But the mission ended soon after and I didn't get a screenshot.
So that's why it's just so odd to me. I don't even know if Dolphin 5.0 itself is entirely bug free and I just got lucky there.
So that's why my ability to provide much info beyond "this is broken, here's a screenshot for proof" is limited.
Updated by Techjar over 6 years ago
Hmm, well JonnyH has pointed out to me that games can utilize the GPU in different ways, resulting in hitting bugs that other games don't. That would also kind of explain why it only happens on newer builds, as Dolphin has changed a lot since the last release. I would make sure your graphics driver is up to date, and possibly try doing a clean install of it.
Updated by Techjar over 6 years ago
Oh and again, if you could provide a fifolog that would be immensely helpful. It would pretty much put the nail in the coffin as to whether this issue is Dolphin itself, or something outside it.
Updated by GhostAngel over 6 years ago
My graphics driver is always up to date, and I always do a clean install, so that's not entirely the issue. If I could get DolphinBisect to work properly, I could at least narrow down which build causes it, but the crashes makes it a slow process.
I could try providing a fifolog, but I still don't exactly know how to use it so it might be a while. Spent all day trying to get this figured out, and didn't have much success with my other issue with King Kong either.
One thing I will say is I'm using a laptop, with a laptop GPU. I wonder if that could be causing issues as I'm sure most people play games on desktops.
Updated by Techjar over 6 years ago
I'm more interested in the fifolog than the bisect. Also, have you made sure Dolphin is using your dedicated graphics and not integrated graphics? Our nvidia optimus hint doesn't seem to work, so you have to manually force it to use the correct GPU via a setting NVCP.
Updated by GhostAngel over 6 years ago
Okay, so I recorded a fifolog (I assume that's what the .dff file is), where the HUD's visual parts get screwed up rather than the text, but it exceeds the 5MB limit apparently. What did I do wrong there?
I also uploaded one for King Kong.
Updated by JosJuice over 6 years ago
It's normal for them to be big. Try putting it in an archive like a zip file and see if that gets you below the limit. If it doesn't, you'll have to use an external file hosting service.
Updated by GhostAngel over 6 years ago
- File Heatseeker.7z Heatseeker.7z added
Got it.
Hopefully someone figures out the issue. For now, I'll just play the 5.0 version of Dolphin.
Updated by Techjar over 6 years ago
Can you provide a screenshot of what that fifolog should look like?
Updated by JMC4789 over 6 years ago
The fifolog looks fine. Have you tried all graphics backends.
Updated by GhostAngel over 6 years ago
- File RHSE36-1.png RHSE36-1.png added
I can't ever quite seem to replicate it. It not only seems random, but now the issue also seems random. So the fifolog should have bugs where it's all different colored boxes on top of the numbers. The initial screenshots I made had the visuals be fine but the numbers and text disappear.
Now I have this where the visual aspects almost don't show up at all. But this is the closest I could get it to look like so far. If I get something more similar to the fifolog, I'll update it.
Updated by GhostAngel over 6 years ago
- File RHSE36-2.png RHSE36-2.png added
Huh, spoke too soon. As soon as I restarted the mission from this screenshot, this came up. Still not exactly alike, but it's basically the same where the boxes are all glitched up over the text.
So it's really weird, sometimes it's one thing, sometimes it's the other. The only thing I can say is it's entirely random, and it only seems to affect the HUD and menus, so objectives and subtitles work fine.
Updated by JMC4789 over 6 years ago
You said this doesn't happen in Dolphin 5.0? Please bisect the issue, that would help a ton.
Updated by GhostAngel over 6 years ago
Dolphin Bisect keeps crashing whenever I try a second Dolphin build after the initial test, and this is also completely random, making it even harder to get.
That's why I was unable to provide a bisect for either this or the King Kong game I was using.
Updated by GhostAngel over 6 years ago
Thanks for taking a look at it. It was one of the games I enjoyed playing at the time, given the lack of arcade flight games on the Wii (Ace Combat was always PS2 before going to 360 and PS3, and Tom Clancy's HAWX was PS3/Xbox 360/PC).
Updated by Techjar over 6 years ago
As mentioned earlier, have you tried all graphics backends? Something is getting mucked up after it's passed to your GPU, cause the fifolog looks fine here.
Updated by GhostAngel over 6 years ago
I did. Tried all the backends, though I usually prefer Vulkan. Was the first thing I fiddled around with.
Updated by GhostAngel over 6 years ago
Another update, well that's odd but it seems like changing the backend to either Direct3D 11 or OpenGL seems to have made it go away. At least I played a mission twice without the bug showing up.
Could be a Vulkan issue then? I swear I recall seeing it as well when I tried it last time on those other backends, but now it seems it only really shows up on Vulkan.
Updated by JMC4789 over 6 years ago
I've been playing the game now for... maybe 45 minutes, probably not long enough to reproduce the issue, but, enough to get a sense for the game.
I was past the two missions at the start. I have a suggestion - try setting the Texture Cache to Safe and try using single core. If the bug does occur, can you try toggling the texture cache to make it reload values?