That information about the controller line is pretty interesting, as it means you could measure lag with a multimeter or modified controller (NESbot-style). Thus, you might not even have to get the emulator to calculate lag for you, if you can measure it from the console itself.
[/URL]
The FPS is 30.5 and the VI is 60.9 (about a 2:1 ratio, as expected). These numbers fluctuate by a few decimal places here and there but generally they are the 30/60. The VI will drastically change during load times; sometimes as much as 20-40 when the input counter only changes by 1. I suppose this is a GOOD thing because I noticed that the N64 console will actually stop polling when there are load screens. So what the emulator may be doing is skipping the time where the polled inputs are not even provided (it did this to me when TASing on Dolphin also). In fact, the controller line goes to zero volts when the load times occur, and picks back up when loading is done. Next thing to find out is if Mario64 or other games absolutely need to have inputs on both polls in order to function on console.
I think the simplest explanation is also the most likely here: SM64 not only displays at 30FPS; it also only receives input at 30FPS. The extra polling the console does is ignored. Of course this should be tested, but it just strikes me as extremely unlikely that this hasn't already been considered.
Wow, this could be huge - this means that there technically could be more frame savings locked in Mario 64, if you had true 60 Hz polling, as opposed to the 30Hz polling that Mupen does.
The problem with Mupen (and PCSX-rr, for that matter) is that they frame advance on the GPU update, as opposed to the V-sync. Now, for games like Grand Theft Auto 2, that is fine - it only polls once per 2 v-syncs. However, for games like Final Fantasy 8, and possibly Mario 64, this provides less possible input than the console is actually allowing for. I had fixed PCSX when we switched over to PSXjin, and now it accurately frame advances on the V-sync, even though the GPU only updates once per 2 frames. This, of course, is a pain in the ass to Motharayas, who is attempting to do GTA2, and has too many vsyncs.
Any news soulcal?
SM64 doesn't run at 60FPS (I think it's 30 or 20FPS instead), even if the console is polling for input that often. I'm not familiar with the systems involved, but it's not inconceivable that the movie format would include a specifier for target framerate, so that it wouldn't have to include input for frames the game doesn't care about. If so, you should be able to stretch the input file to cover more time.
And another thing to consider about the TASer of Dolphin, is that we don't have read-only mode. If we want to see if a part of a TAS synched, we need to start the TAS all over EVERYTIME.
This is improper emulation, nothing else, and all improvements achieved through it are thus irrelevant and in fact counterproductive. We don't, and we shouldn't use emulation inaccuracies to our advantage because that just defeats the purpose.
Why not just kill 2 enemies for 9900 drops each? You have the pistol equipped now, the time lost is a headshot + waiting for the pick-up.
Remember there's that forced cabin fight, which is a potential goldmine for money in manipulated drops.
EDIT: Why did you capture the TAS at like 20 fps? (desync?)
But I wonder, is it slower to go through the gap in the wall instead of the door after you exit the house?
Also is there nothing useful to be found in the two barrels right before the second emblem?
And over in 1-3 in the cave, you can shoot the lantern in order to shoot the treasures in the ceiling. Is it possible to use a grenade (which you probably can get from the dynamite enemies) to blow them down instead? You'll earn a nice 14000 ptas from the Headdress and two spinels in there alone, not counting the crate in the same area as well.
Like you already mentioned this game have lots of loading, so you are suggesting to make the movie even longer just to win seconds on the end screen?
Ultimatly this isnt SDA so dont take game time objectives arbitrarly especially since this is something the site usually against (our movies are measured real time), if the runs arent comparable then it doesnt matter your time is higher than another run, given its still superplay, if your run doesnt do anything spectacular and is basicly just the same thing than a human would do, maybe you have a problem with the game choice.
