Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1142)
Joined: 5/1/2010
Posts: 1217
sack_bot wrote:
Ilari wrote:
Basically, if game runs at 60fps, youtube drops every second frame, causing some blinking objects to become solid and some to disappear (according to sampling theorem, 30Hz (60Hz/2) aliases to 0Hz (i.e. static) when sampled at 30Hz).
The FPS is 50, so it must be sampled to 25 right?
If you downsample 50fps to 25fps, the same problem happens. But if 50fps is downsampled to 30fps, the blinking will occur at 5Hz...
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1142)
Joined: 5/1/2010
Posts: 1217
sack_bot wrote:
Ilari wrote:
Do those lasers blink? Blinking objects disappearing in Youtube encodes is well-known problem (caused by youtube dropping frames).
Yep.
On the frames where the horizontal lasers are not there.
Basically, if game runs at 60fps, youtube drops every second frame, causing some blinking objects to become solid and some to disappear (according to sampling theorem, 30Hz (60Hz/2) aliases to 0Hz (i.e. static) when sampled at 30Hz).
The speed run disconnected the grabbing hook there. Your run fully climbs to the next platform.
As aglar said, the screen needs to be scrolled enough (in the speedrun, the screen scrolls back a bit after this frame).
Also, this should be very minor change to the run. If you change this, please upload the changed movie to userfiles and request replacement. This avoids having to wait the 72 hours.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1142)
Joined: 5/1/2010
Posts: 1217
FractalFusion wrote:
By the way, the memory addresses given in the submission text are based on offset from C000 (main RAM/whatever it is called); e.g. 1A3F is treated in GB as well as VBA as DA3F.
AFAIK, bus-DA3F corresponds to wram-1A3F only if WRAM window 1 is set WRAM page 1 (Gameboy Color).
Otherwise, bus-DA3F corresponds to some WRAM address of form wram-xA3F (where the x is the page number set to WRAM window 1).
IIRC, WRAM window 0 is fixed to page 0, which means bus-C000-CFFF does correspond to wram-0000-0FFF.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1142)
Joined: 5/1/2010
Posts: 1217
jlun2 wrote:
Or is the hitbox for the gate completely different in Dolphin?
In some linked bugreports, someone speculated that the cause is that Dolphin lags less than a real system, and thus the motion quantums are smaller and not enough to pass through.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1142)
Joined: 5/1/2010
Posts: 1217
Krumstone wrote:
I'm not sure if I'm asking this in the correct place, but I got here from the fceux.com site.
I've been searching everywhere looking for a way to get an AVI video with FCEUX. It seems pretty simple, but I don't have the necessary menu items for this task. I only have File, Options, Emulation and Movie. I'm missing NES, Config, Tools and Debug. I tried to build it from source with no success.
I'd appreciate any pointers. Thanks a lot.
Is this on Linux or some other unix-like?
Here's the contents of template command I use for video dumping from from FCEUX:
Foo, bar and qux are metasyntatic, NESVSETTINGS is literial (the emulator itself replaces it with some settings).
And apparently video dumping disables speed throttle, so it is only useful for capturing movies into AVI.
The speed run disconnected the grabbing hook there. Your run fully climbs to the next platform.
As aglar said, the screen needs to be scrolled enough (in the speedrun, the screen scrolls back a bit after this frame).
Also, this should be very minor change to the run. If you change this, please upload the changed movie to userfiles and request replacement. This avoids having to wait the 72 hours.