Dolphin, the GameCube and Wii emulator - Forums

For all who read this thread.

Some people from the Mario Kart Wii forum told me how to get rid of 41 times Mario Circuit in Wiimm's distributions.

This was said there:
You need to go into Config and change the CPU Emulator Engine from JIT recompiler to JITIL experimental recompiler for this to work. I don't know why, that's just the way it is. Remember to change it back later when you're playing other games.

This should work. Have fun with Mario Kart Fun!

410172

p.s.: no bumping old threads cause this one is not even two weeks old :o lol

That's not a solution, that's a work around. If there is a bug with the JIT, it should be reported. It's not just the way it is; it needs to be fixed.

Yes I'd like to confirm the bug.
Maybe the code itself is buggy, but it works on Wii, JITIL, but not JIT. It's a valid bug unless the code itself has undefined behavior.

Also I'm planning to design a cheat disk for CTGPR. Same reason, all tracks replaced with trollfaces, use whatever cheat codes. Sadly, it will only work on Dolphin because CTGP 1.02 patch blocks the cheat-handler memory patch (while Dolphin Gecko does not inject it), and it's too much trouble to recompile the CTGP patch without the anticheat.

(05-16-2014, 12:55 AM)410172 Wrote: [ -> ]For all who read this thread.

Some people from the Mario Kart Wii forum told me how to get rid of 41 times Mario Circuit in Wiimm's distributions.

This was said there:
You need to go into Config and change the CPU Emulator Engine from JIT recompiler to JITIL experimental recompiler for this to work. I don't know why, that's just the way it is. Remember to change it back later when you're playing other games.

This should work. Have fun with Mario Kart Fun!

Eyh, I'm actually the one who wrote that to you over there! Glad it worked out.

(05-16-2014, 02:43 AM)JMC47 Wrote: [ -> ]That's not a solution, that's a work around. If there is a bug with the JIT, it should be reported. It's not just the way it is; it needs to be fixed.

I've been thinking about reporting this for a while. What would be the proper place though? I don't know if reporting a problem that only exists with certain fan patches for a specific game to the tracker would be the proper way of doing it. Maybe make a thread here in the support sub-forum?

Here's where you report issues: http://code.google.com/p/dolphin-emu/issues/list

(05-16-2014, 08:33 AM)JMC47 Wrote: [ -> ]Here's where you report issues: http://code.google.com/p/dolphin-emu/issues/list

I just submitted a report, I hope I didn't screw up too badly. :<

http://code.google.com/p/dolphin-emu/issues/detail?id=7288

I'd imagine it's a low priority issue though, with it only affecting a few custom patches for a particular game on a particular CPU emulator engine. Still would be nice to see it fixed someday.

Issue report looks solid at a glance. The fact it works on JITIL makes it a lot easier to narrowdown and fix

I'll be doing more tests tomorrow to find the exact build where the bug starts to take on a different form. I highly suspect it's related to this: https://forums.dolphin-emu.org/Thread-green-notice-development-thread-testing-wanted-newer-ppcanalyst-cpu-core-improvements

I think it's related to PPC_FP; as that shouldn't affect non-MMU games in any adverse ways.

I have no idea what you just said (I'm not familiar with the terminologies), so I'll just be doing a lot of manual testing tomorrow.