[Wii] Super Mario Galaxy

[delroth]

Wiki Page - Super Mario Galaxy - [edit]

Previous discussion thread

[Duke Nukem]

OK something serious is going on here. In the clean master build 3.0-830 x64 downloaded from the official source (here at Dolphin) I get numerous GFX FIFO errors all the time at the Beach Bowl galaxy, Sunken Treasure star.
Haven't tried any other level yet, but I guess it's the same.

In the stable 3.0 release I have never experienced these kind of GFX FIFO errors on any galaxy or level in Super Mario Galaxy.

Is there something I have missed here lately? Is this a known problem?

I'm using DSP LLE, EFB Copy to RAM, Direct3D9 as usual and all the same settings since 3.0 that have always worked.

I guess I'll just have to revert back to 3.0 when playing this because I love this game.

[neobrain]

Not known as far as I can tell, feel free to investigate :>

[Duke Nukem]

OK it happens all the time when Mario/Luigi swims now.

GFX FIFO:Unknown Opcode (*insert random number here*)
This means one of the following:
*The emulated GPU got desynced,disabling dual core can help
*Command stream corrupted by some spurious memory bug
*This really is an unkown opcode (unlikely)
*Some other sort of bug
Dolphin will now likely crash or hang.Enjoy.

I tried:
- Direct3D11
- Disable Dual Core
- Disable Idle Skipping
- Enable Real XFB

Still the same GFX FIFO errors/warnings

I'm gonna try out the clean master builds 3.0-815 x64, 3.0-840 x64 and build 3.0-823 from the AX HLE branch to see if it's the same there. This is really really weird and I really really do not want to get back to 3.0

[Duke Nukem]

Bad news regarding 3.0-840 x64, this is what I got this time when swimming in Beack Bowl Galaxy - Sunken Treasure:

Backpatch - no support for operand size 1
Error encountered accessing emulated address c2429038 culprit instruction
movzx eax, byte ptr ds:
[rbx + rcx] at 0x1500cd6c
_______________________________________________________________
Unhandled disasm
Case in write handler
Please implement or avoid


Guess I just have to try 3.0-815 and the 3.0-823 AX HLE build before I call it a quits for tonight.

[neobrain]

Testing new AX HLE is pretty much useless, because that's not something that gets caused from DSP HLE, usually, unless it's some weird mem corruption in that regard. Anything before http://code.google.com/p/dolphin-emu/source/detail?r=8eb6f9002e2663eababd0ade685e9f8107531cd2 should have the same stability as new AX HLE.

[Duke Nukem]

Well it doesn't matter anyway, 815 and 823 both gave me:

GFX FIFO:Unknown Opcode (*insert random number here*)
This means one of the following:
*The emulated GPU got desynced,disabling dual core can help
*Command stream corrupted by some spurious memory bug
*This really is an unkown opcode (unlikely)
*Some other sort of bug
Dolphin will now likely crash or hang.Enjoy.


Dolphin haven't liked me at all today and this game especially have hated me.
I guess that I have no other choice then going back to stable 3.0 with this game for now.

[neobrain]

Well, it would be cool if you identified which revision caused that... :O

[Duke Nukem]

I have been playing, testing and fooling around for hours now. 3.0-784 is the last version I tried a while ago and 3.0-840 being the highest I have tried and no matter what I do under water on the Beach Bowl Galaxy - Sunken Treasure level this always happen:

GFX FIFO:Unknown Opcode (*insert random number here*)
This means one of the following:
*The emulated GPU got desynced,disabling dual core can help
*Command stream corrupted by some spurious memory bug
*This really is an unkown opcode (unlikely)
*Some other sort of bug
Dolphin will now likely crash or hang.Enjoy.


I have tried other Galaxies and they seem to work OK. Drip Drop Galaxy next to the Kitchen were completable for example.

I don't have a clue of what's going on here. This is a serious issue that makes the Beach Bowl Galaxy practically unbeatable (at least for me) and it's one of my absolute favorite galaxies in Super Mario Galaxy.

Please if you have the game try some of the latest versions and see if you have more luck then I had.

I give up for tonight and probably the rest of the week as I have other things to attend to.

I'll probably try out a new version next week or something.

[Duke Nukem]

To whom it may concern:

My testing and findings indicates that this error only occurs on the Beach Bowl Galaxy with any of the levels there that requires swimming and being under water.
Because the moment you dive in and start to swim and spin etc. things are going really slow and then BAM BAM BAM!

Many other galaxies have water levels where you can swim and stuff and they work just fine, like Drip Drop Galaxy I mentioned yesterday, Bigmouth Galaxy, Sea Slide Galaxy to mention a few.
The land/ground based galaxies works fine too since I played around for over an hour going from different galaxies until I decided to go to Beach Bowl to have some "fun" and indeed "fun" it was.

Well that's all I can come up with at the moment and I don't have more time to test other versions this week. So yeah....