I do 4:57 attempts on FCEUX emulator. Sometimes during runs, my fps drops to around 50 fps randomly for a split second. This sometimes can be very annoying sometimes, as it screws up the run. Two questions: Does anyone have any solutions to this? Switching to Nestopia is not an option, as it runs at 60 flat FPS on my computer. If this causes time to be lost, so that a run that is 4:57 on the spreadsheet is 4:58 long from the start to the end, will it get verified as a 4:57 or a 4:58?
If an emulator lagged and actually delayed the game play then yes it would be included in the time as a delay - same with 6-4 bowser lag or bbg lag frame - and same general principle as 60fps (as is the case on switch) vs console fps
You'd use hammer patterns and then add in any relevant lag.
That being said I'm not aware of emulators regularly causing lag in that way. My impression is that when they stutter that's rendering delays but doesn't actually affect the speed of the game, just how it's shown on your screen. But if it did actually delay the game then yes, the final time would also be delayed.
You should be able to tell if it's causing real delays or not based on livesplit. If you're splitting slightly late after seeing lag then I suppose it's possible your computer emulator combination is slowing game play somehow. But if livesplit is splitting in framerule units as it should then you shouldn't have anything to worry about.
Thanks Darpey - In the levels when the fps drops, it'll usually add +0.1 to the splits, even though the previous levels were 0.0. I'm decently sure it is slowing the game down - does anyone have any fixes for FCEUX random fps drops? I'm guessing it's because I have OBS + Nohboard + FCEUX + Livesplit open at the same time, but I don't know what to do about that.
Apparently NEStopia lags less (that's just what I heard so idk if its true). Also in nestopia you can set the fr to what you want (60.9..... for example)
idk maybe try bizhawk
"Switching to Nestopia is not an option, as it runs at 60 flat FPS on my computer."
Thanks everyone, issue has been resolved with help from some friends
Any% (NTSC) runs below 4:57.000 must now fulfill additional requirements in order to be verified.
- The run's full session must be included in the submission description.
- For emulator runs below 4:57.000, some form of input display must be visible for the duration of the run. A hand-cam or input