Emulator Issues #7427
closed
Super Mario Galaxy random blue walls
0%
Description
Game Name?
Super Mario Galaxy
Game ID?
RMGP01
What's the problem? Describe what went wrong in few words.
So in Super Mario Galaxy there's one level called "Ghostly Galaxy", right? It's in the Kitchen dome, somewhat into the game. In one of the secret stars called "Matter Splatter Mansion" (also available when doing "A Very Spooky Sprint"), the walls that are supposed to be invisible appear visible. Another galaxy that has the exact same problem is "Matter Splatter Galaxy". I've made two screenshots, first is how it used to look like (I downloaded some random old version, 3.5-1124) and how it looks on the latest.
http://imgur.com/t1ozlz8
http://imgur.com/EFaB4yX
I've also tried making a Fifo log of Matter Splatter Galaxy, but it kept crashing when I tried to play back it, sorry for I'm either new to this or Fifo is buggy
What did you expect to happen instead?
For one, the blue walls are not supposed to be here. They are not on the Wii, they weren't on old versions, and it's not tied to a video backend.
What steps will reproduce the problem?
- Get a 100% save file for convenience
- Go to Ghostly Galaxy and select A Very Spooky Sprint star
- Take that launch star inside a glowing boulder to get to the correct area
- Just look at the blue walls, you don't need to dance to make them appear
Or attempt to open the Fifo log and hope it doesn't crash like mine does
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-1977
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
I will test that later, look in the comments maybe I already did
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
OS: Windows 7 64 bit
CPU: AMD Athlon II 2 X2 240 (2.81 GHz)
RAM: 2GB
GPU: GeForce GT 240
Are you using the 32 or the 64 bit version of Dolphin?
64 bit
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
http://imgur.com/t1ozlz8
http://imgur.com/EFaB4yX
http://a.pomf.se/gsntlx.dff
Tried OpenGL and DirectX backends, setting EFB copies, texture cache, XFB, other stuff in the settings
Updated by kostamarino over 10 years ago
I can't replicate this one, do you have the latest nvidia drivers installed?
Updated by JMC4789 over 10 years ago
- Status changed from New to Questionable
yeah, I just played through this very recently with no issues. It looks like some kind of culling issue with how the level is supposed to be. Do you have fast-depth or something on?
Updated by fr0ge over 10 years ago
I tried reproducing it again with DirectX, but there were indeed no problems here. The problem appears to be only in OpenGL. This will teach me to not do savestates
My drivers are v340.43 beta, still seems to be the latest.
Updated by JMC4789 over 10 years ago
If it happens in OpenGL, it's still an issue. I'll check it out on latest, it could be a new bug from NVIDIA even.
Updated by kostamarino over 10 years ago
I still can't replicate it using opengl...
Updated by fr0ge over 10 years ago
Are you trying this on the European version? If you do maybe I have some weird setting that does this
Updated by JMC4789 over 10 years ago
I'm on the U.S. version of the game. Let me actually load your fifolog. You need to playback fifologs in single core mode, just to let you know.
Updated by JMC4789 over 10 years ago
Your fifolog doesn't match the area of the screenshots. Can you please give me a screenshot showing your fifolog?
I don't see anything wrong with the screenshot, though, at least at a glance.
Updated by fr0ge over 10 years ago
Alright thanks for telling me
This is Matter Splatter Galaxy, the very beginning of it.
This is how it looks like on OpenGL (at least for me): http://i.imgur.com/9nwgRbm.png
And this is how it looks like on Direct3D: http://i.imgur.com/Ov3HIH5.png
Updated by fr0ge over 10 years ago
I found the exact revision when it started happening, it was 4.0-1192, here's its description:
Merge pull request #68 from neobrain/tev_fixes_new
Change pixel processing to use integer arithmetic.
Updated by JMC4789 over 10 years ago
Looks like it's an issue on your computer. I have NVIDIA as well, so I'm not exactly sure why you're getting different results.
Updated by JMC4789 over 10 years ago
Do you by chance have disable destination alpha on?
Updated by fr0ge over 10 years ago
Here's how the same place looks like with different settings (tested on Dolphin 4.0-2109):
http://imgur.com/a/kshQ1
And the Fifo log: http://kek.2fh.co/test/smg.zip
Updated by JMC4789 over 10 years ago
What version of the NVIDIA drivers do you have?
Updated by fr0ge over 10 years ago
This is the driver I have
http://www.nvidia.com/download/driverResults.aspx/76513/en-us
Updated by JMC4789 over 10 years ago
This really makes no sense at all. We're using the same drivers, we're using similar graphics cards, and we're getting different results. Can you screenshot all of your dolphin settings in the graphics sections of both D3D and OpenGL?
Updated by fr0ge over 10 years ago
You can have my user/config folder
http://kek.2fh.co/test/config.zip
Updated by JMC4789 over 10 years ago
It says you have per pixel lighting enabled in OGL, but not in D3D. Is that perhaps the problem here?
Updated by fr0ge over 10 years ago
Doesn't really make any difference when I enable or disable this opition though
Updated by JMC4789 over 10 years ago
Ok. There's one real thing that could be causing problems. And that, is that your NVIDIA driver is overriding some settings in Dolphin. If you have AA, MSAA, or any of that kind of thing enabled in the driver, maybe it's affecting OGL?
Updated by fr0ge over 10 years ago
I didn't touch the default options and the program specific settings don't even list Dolphin
http://i.imgur.com/vTfuwf9.png
Updated by JMC4789 over 10 years ago
You have 8x Anisotropic Filtering forced on in your driver. Don't know if that's the problem.
Updated by fr0ge over 10 years ago
Okay, changed that to "Application-controlled", but the problem is still here
Updated by JMC4789 about 10 years ago
There have been several NVIDIA updates since this issue, and I still can't reproduce. Can you test it again?
Updated by fr0ge about 10 years ago
I couldn't get the fifo logs, but I just went to the Matter Splatter Galaxy with OpenGL backend and I can confirm it still happens. I have a Nvidia driver 340.52 and Dolphin 4.0-3334
Updated by JMC4789 about 10 years ago
Thank you for the quick reply. I have no idea what's going on, though!
Updated by JMC4789 about 10 years ago
I think I figured it out. Your processor is older than mine... could you try saving a state in the area, then loading the state in interpreter?
Updated by fr0ge about 10 years ago
I did that, but it didn't make any difference
http://i.imgur.com/blZNpMM.png
Updated by JMC4789 about 10 years ago
Can you try it on some other computers? I'm just curious.
Updated by fr0ge about 10 years ago
I'll try that tomorrow, can't hold my word that the laptop I have can actually run Dolphin though
Updated by fr0ge about 10 years ago
I could not test it. Although the laptop had the latest drivers, Dolphin gave errors that the GPU wasn't compatible with both OpenGL 2.0 and DirectX 10
Updated by JMC4789 about 10 years ago
Okay, so here's my idea. If you're somehow hitting a driver bug that NVIDIA introduced to the GTX 2xx cards and older. I need to find someone with an old graphics card to verify, though. My GTX 280 is no longer with me.
Updated by JMC4789 about 10 years ago
Can you find the exact build that broke it? That's all I can ask for now.
Updated by JMC4789 about 10 years ago
Sorry about that, I wasn't paying attention well enough, apparently. The odds of this being a driver bug just went way up...
Updated by JMC4789 about 10 years ago
- Status changed from Questionable to Invalid
Okay, I had a bunch of people on older computers and NVIDIAs try it; it's not a driver bug. I had an 8200m, GTX 560m, a GTX 470, a GTX 285 among others test out this issue. Also tried out AMD video cards and even my integrated cards.
My thoughts that something you have installed/running when you play Dolphin causes EFB Access to CPU to fail. At this point, Because I've tested this on so many computers in so many different situations, I'm going to have to mark it as invalid. No one else can reproduce it, and my only guess is user error.
If someone else can confirm this issue, I'll gladly reopen the issue report.
I really hope this is something stupid like fraps hooking in, I don't like leaving the issue like this, but I'm out of options.
Updated by MayImilae about 10 years ago
The ultimate crapbook to the rescue once again. That 8200m is powerful indeed! ...in it's own way.
Updated by MayImilae about 10 years ago
The ultimate crapbook to the rescue once again. That 8200m is powerful indeed! ...in it's own way.