Games locked at 30 FPS?

[och]

It seems that every game in 1964 0.99 runs at 30 FPS. I can disable speed limit, and then most games run at more than 100 FPS, but they also run 3x faster than they should be running, making them unplayable.

I remember in Project 64 games ran at 60 FPS and at normal speed. I there a way to do that in 1964?

 

[Allnatural]

Don't confuse VI/s with fps. The VI/s should be 60 (assuming NTSC and sufficient hardware). Fps is generally 30, less for some games (ie. Banjo-Kazooie runs around 20).

 

[och]

Don't confuse VI/s with fps. The VI/s should be 60 (assuming NTSC and sufficient hardware). Fps is generally 30, less for some games (ie. Banjo-Kazooie runs around 20).

What is VI?

 

[och]

PJ64 defenately running at 60 FPS, it says so on the PJ64 status bar, pretty much any game runs at 60 FPS.... With 1964 its 30 FPS...

 

[ScottJC]

Project 64's status bar lies (sad but true), when it says FPS it means VI's, i can assure you the fps is 30, equal to 1964.

NTSC Games run at 30 frames per second anyway, whats the problem? If they were going at 60 they'd be going too fast.
PAL Games run at 25 frames per second.

So PAL would display 50FPS in Project64 and 50VI's in 1964 but they mean the same thing.

VI/s = Vertical Interrupts per Second

Also, instead of double posting, use the EDIT button.

 

[schibo]

FPS can vary from game to game. Some will run at 30 FPS, some at nearly 60 FPS, some at 20 FPS. You cannot calculate the FPS by reading Vertical Interrupts per Second (VI/s). Since NTSC is close to 60 VI/s and PAL is 50 VI/s, VI/s is a reasonable gauge of speed to know if you are at full speed, above full speed, or below full speed.

If you want to know FPS in a game, such as in Rice's video plug-in, you can turn on the FPS overlay statistic in the plug-in's DirectX options.

For many games if you use a lower Counter Factor (CF) you will get more unique frames per second because more Display Lists per Second (DL/s) are processed. Use CF1 instead of CF3. A higher counter factor is for slower machines, and will produce less DL/s. Use an odd CF 99% of the time--at least in 1964.

 

[och]

FPS can vary from game to game. Some will run at 30 FPS, some at nearly 60 FPS, some at 20 FPS. You cannot calculate the FPS by reading Vertical Interrupts per Second (VI/s). Since NTSC is close to 60 VI/s and PAL is 50 VI/s, VI/s is a reasonable gauge of speed to know if you are at full speed, above full speed, or below full speed.

If you want to know FPS in a game, such as in Rice's video plug-in, you can turn on the FPS overlay statistic in the plug-in's DirectX options.

For many games if you use a lower Counter Factor (CF) you will get more unique frames per second because more Display Lists per Second (DL/s) are processed. Use CF1 instead of CF3. A higher counter factor is for slower machines, and will produce less DL/s. Use an odd CF 99% of the time--at least in 1964.

I dont quite understand how the CF factor works... I usually leave it at automatic. And I see now, the status bar of 1964 says 60 VI/s and on screen FPS says 30 FPS most of the time. However, I'm having a problem with Ready 2 Rumbe Round 2, it runs at ~15fps ~30 VI/s, however when I disable speed limit it runs at over 100.

 

[schibo]

I dont quite understand how the CF factor works... I usually leave it at automatic. And I see now, the status bar of 1964 says 60 VI/s and on screen FPS says 30 FPS most of the time. However, I'm having a problem with Ready 2 Rumbe Round 2, it runs at ~15fps ~30 VI/s, however when I disable speed limit it runs at over 100.

Disable autoCF and use CF1.

 

[och]

Disable autoCF and use CF1.

When you say use CF1, are you refering to the first listing in the CF menu? 1 x .5 half rate?

 

[-Shadow-]

When you say use CF1, are you refering to the first listing in the CF menu? 1 x .5 half rate?

Yes , he do .

 

[riles9262]

CF1 makes your games the smoothest they can run in my experience, provided that you have a powerful enuf computer.

And fps are different per game; for instance, fzero runs at about 60fps, zelda ocarina of time at around 25-30, and turok 2 fluctuating between 10 and 25 most of the time.

 

[knowitman]

Star Wars Episode One Racer runs at around 10-25. When you put the counter factor on 1 I think it forces the game to run at 60 fps usually w/o making the game run too fast. I noticed that Episode One Racer was running at aroudn 15. I turned the CF to 1 and it ran at 60. It didn't run too fast just smoother.