Emulator Issues #12333
open
Crazy Taxi Arrow appearing incorrectly
0%
Description
Game Name?
Crazy Taxi (GCN)
Game ID? (right click the game in the game list, Properties, Info tab)
GCTE51
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
5cfbfbba443bce3923f033b812a8376b
What's the problem? Describe what went wrong.
In the latest version of Dolphin the green arrow at the top center of the screen appears incorrectly at the top right, behind the farebox.
What steps will reproduce the problem?
Play Crazy Taxi in any mode. Problem occurs with or without widescreen hack, with both an NKit dump and regular dump.
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
5.0-13178
Is the issue present in the latest stable version?
Yes
5.0-12716
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.)
[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)
Intel i5
Nvidia GeForce MX250
Windows 10
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Works perfectly in Dolphin 4.0.2.
Files
Updated by JMC4789 over 3 years ago
- File CrazyTaxi.png CrazyTaxi.png added
- Status changed from New to Questionable
Cannot reproduce. Default settings on the latest development version.
More information required. What backend were you using? Was there any other settings you used that would be considered non-standard or potentially able to cause graphical issues?
Updated by rodomallard over 3 years ago
Using Direct3D 12. No non-default graphics settings, only a widescreen cheat but the issue occurs with cheats turned off as well. Used same NKit image with older version of Dolphin (4.0.2) that worked with also default settings.
Updated by ZephyrSurfer almost 3 years ago
Is the problem happening when you run the fifolog you provided. Can you screenshot the image of the issue while running your fifolog.
Does the issue happen on OpenGL or Direct3D 11/ Direct3D 11 for you as well.
Can you test if it works for you in the last Stable version of Dolphin 5.0? If it works in 5.0 please bisect when it started happening.
Updated by ZephyrSurfer over 2 years ago
I realised what this issue is.
I seen another user with a similar issue and found these are the same issue at hand.
This is an issue caused by StereoMode = -1
This is the only way I can reproduce the issue the user reported on the build they had used -> 5.0-13178
Why would StereoMode get set to a value of -1? That's not mapped on the GUI
Updated by ZephyrSurfer over 1 year ago
Can this be reopened?
The issue is when user's config has StereoMode set to -1.
Reproduction is achievable with the fifolog attached on this ticket when config set to this value.
Updated by pokechu22 over 1 year ago
- Status changed from Invalid to Questionable
Can reproduce with StereoMode set to -1. It also affects other stereo modes (presumably anything other than Off) but those actually are valid modes. I'm not sure if there's any way to make it work correctly, though, or why the stereo mode would become -1.
Updated by ZephyrSurfer over 1 year ago
The user provided image also looks the same as StereoMode = 4 now that I've looked through the values. But indeed it affects the other modes.
(Some other user that reported an issue before had a very similar issue and it turned out the StereoMode was blank on the GUI and had -1 set on the GFX.ini so I had just checked this one and it produced the issue the user described.)