Quote
Originally posted by: Jensen
Quote
Originally posted by: Professional 666
No, Mario 64 on N64 (NTSC) runs at 20fps... of the 30 "displayed frames in a second," only 20 of them mattered (same goes for the 3D Zeldas).
I used an emulator that displayed the actual game fps.
Zelda PAL: 16-17
Zelda NTSC: 20
Mario NTSC: 30
Anyways, I can tell just by playing Mario that it is quite a bit smoother than Zelda.
Do you have a source for your 20fps claim?
Here's a couple image sequences from 30.00fps, single-field only, captures from Mario64 off my N64 and Master Quest off my GC. Since every 3rd frame was a dup, for the longest time I believed Mario64 was 20fps.
But I've changed my mind. I swapped Mario64 and Ocarina of Time (and viewed them on a TV rather than vidcap software) and realized Mario was a bit smoother. I see with my eyes that Mario64 runs at 30fps. "yes." But why aren't my captures agreeing?
Something had me fooled, so I spent the day investigating why. My vidcap hardware drops every 3rd frame in most N64 captures . After examining odd & even fields in several captures, I concluded that the N64 is weird. My hardware will drop a frame whenever it receives a field anomaly (like the split-second screen mess you might see when you turn device/console on or off); it needs an odd and an even field to store a complete frame, if a field is strange or missing, the frame gets dropped and the last recorded frame gets duplicated to fill the gap. This doesn't happen when recording from DVD players, VCRs, GameCube, Dreamcast, Cable TV, etc. -- only N64.
Since the N64 isn't capable of p.scan, it sends fields, not frames, to a TV display. If 3 consecutive frames are composed of 6 consecutive fields, i'm guessing the 5th or 6th field is either strange or missing in the pipeline. Maybe the odd set of fields are complete, and every 3rd field in the even set is "weird." TVs don't seem to care, yet my vidcap hardware isn't satisfied. Blasted machines.