Emulator

Have you tested this in the latest development version of Dolphin? You didn't list a version in the issue report, and the linked video is of 5.0.

JosJuice wrote:

Have you tested this in the latest development version of Dolphin? You didn't list a version in the issue report, and the linked video is of 5.0.

I just did a test with 5.0-8533 and same issue, it skips past the screen almost instantly.

It skips over it depending on what controllers are plugged in for me. If I'm using a Wii Remote + Classic Controller, it lasts longer than if I have a GameCube Controller plugged in. I compared it to Mario Party 2 on console and it seemed pretty much perfect.

Edit: Just read your issue that it's for Ocarina of Time VC - please follow the issue report template next time. Also, would you try the different controller configurations out of curiosity? I wonder if we're doing something wrong. Also, there are plenty of other minor timing issues with Dolphin and OoT VC that I'd recommend it not be used for speedrunning. Our cycle accuracy just isn't good enough.

Sorry, I assumed this was a general VC issue and not just OoT VC, so I left that info out, I also assumed (correctly) that it was occurring up to current versions, so I left that out, but I can see how it can cause problems with organization if everyone starts making these kinds of assumptions.

Most of the players are trying to play with a Gamecube controller, as that's the norm for speedrunning OoT at the moment. To my knowledge there's no way to make that screen go faster in OoT, because if there were speedrunners would be using it.

Sorry, I assumed this was a general VC issue and not just OoT VC, so I left that info out, I also assumed (correctly) that it was occurring up to current versions, so I left that out, but I can see how it can cause problems with organization if everyone starts making these kinds of assumptions.

Most of the players are trying to play with a Gamecube controller, as that's the norm for speedrunning OoT at the moment. To my knowledge there's no way to make that screen go faster in OoT, because if there were speedrunners would be using it.

As far as the timing issues, considering the current "allowed" emulators are Project64 1.6 and 1.7, I doubt it could be much worse.

I don't know if I should open a new issue about this but the last change messed up MM's reset times. They were faster than console before but now they are a lot slower. Here is a console reset:https://youtu.be/s3ohLCQnjjo?t=28 and here's Dolphin's resets on 5.0-13688(I include both JP and US because they use different IOS versions)https://youtu.be/-fGxHR0OrU8 https://youtu.be/Q9r0_E0c9ss

On Majora's Mask (J) I can confirm that my Wii is ~6 seconds faster for some reason. I have limited space on my Wii, will test NTSC soon. I'm not sure which IOS I'm using, as I have to boot it from GeckoOS

Dolphin is 6 seconds slower on NTSC-J, 8 seconds slower on NTSC for me. I'll provide logs in IRC as not completely blow up the issue report with a huge wall of text.

https://www.irccloud.com/pastebin/1o8YCYsN/

Partial log showing what I think is the second half of the reads. The rest fell off of the history, so I'd have to put in a modicum of extra effort to get them. If these aren't sufficient in showing what's going on, I'll do so.

The regression should be fixed in 5.0-13690.

Yes, it looks like it's fine now. Thank you for fixing it so fast.