Can you describe what "this one insane glitch" is in more detail?
Dolphin is emulating the VC version, so, if it doesn't react like an N64 console version, that makes sense.
If you want more accurate crash handling, turn on MMU emulation in the game properties.
(06-22-2015, 02:47 AM)JMC47 Wrote: [ -> ]Dolphin is emulating the VC version, so, if it doesn't react like an N64 console version, that makes sense.
If you want more accurate crash handling, turn on MMU emulation in the game properties.
I'm not exactly sure if we are on the same page. Doing this glitch on an original or emulated n64 always crashes, while doing this on a Wii or emulated Wii (Dolphin) causes some weird results, which we are trying to figure out how to control with Dolphin. I turned on the MMU emulation under game properties, and I still get the same crash messages. Someone wrong warped with this, which is unheard of in this game, so we are trying to replicate it.
It's unlikely that Dolphin is accurate enough for that outside of the interpreter if the JIT is crashing.
If the interpreter crashes as well, maybe it's something else?
(06-22-2015, 12:41 PM)JMC47 Wrote: [ -> ]It's unlikely that Dolphin is accurate enough for that outside of the interpreter if the JIT is crashing.
If the interpreter crashes as well, maybe it's something else?
I have no clue. I was told I should contact a Dolphin developer to ask why this is happening, and if it's fixable. This glitch is so bizarre and unexplainable and to make sense of it, we need a reliable emulator to test things.
(06-22-2015, 12:41 PM)JMC47 Wrote: [ -> ]It's unlikely that Dolphin is accurate enough for that outside of the interpreter if the JIT is crashing.
If the interpreter crashes as well, maybe it's something else?
I didn't realize you said I should use interpreter. 4 fps kind of sucks, but upon using it I get a different crash message so I'm not sure if that makes a difference.
(06-23-2015, 05:50 AM)Rainmaker Wrote: [ -> ]I didn't realize you said I should use interpreter. 4 fps kind of sucks, but upon using it I get a different crash message so I'm not sure if that makes a difference.
It's probably not significant. Error messages are usually written for specific pieces of code, and the code for interpreter and JIT is completely different from each other, so this is a natural consequence.
(06-23-2015, 06:03 AM)JosJuice Wrote: [ -> ] (06-23-2015, 05:50 AM)Rainmaker Wrote: [ -> ]I didn't realize you said I should use interpreter. 4 fps kind of sucks, but upon using it I get a different crash message so I'm not sure if that makes a difference.
It's probably not significant. Error messages are usually written for specific pieces of code, and the code for interpreter and JIT is completely different from each other, so this is a natural consequence.
Do you happen to know if these error messages are pointing directly to addresses found in the game? I got this error:
https://gyazo.com/fff0ae5dd1802f8fc9274b7c959d3f02 which was then followed by hundreds more where PC = 801AE830 +4 occurred. Every single time a new message came up, it added four to the original all the way up to 801AEE00 or so. If I just understood what this crash was telling me, I think it would help a ton. (Sorry for reviving this really old thread, I just really want to figure this out.)