Doom 3 capped at 60 fps.
- Thread starter Ferocious
- Start date
They didn't have to lock the framerate to do that, but there is no benefit to not locking it since you can't see >60fps anyway.... so who cares?
Strafe jumping isn't directly tied to the framerate so I don't think that will matter much but...
1. an fps cap is speculation at this point
2. It's likely that movement speed in D3 will be slowed considerably to match the pace of the game so strafe jumping might not really be available or even useful.
3. any talk about q4 is major speculation since it's only known to use the d3 engine at this point, no word on the pace of the game (will be single player focused though)
4. If they want strafe jumping available the physics engine will allow it regardless of the rendering engine. Strafe jumping started as a bug but that bug was fixed long ago and the code modified to continue to allow it.
I can easily see past 60 fps. I fade somewhere between 80 to 110.
1. an fps cap is speculation at this point
2. It's likely that movement speed in D3 will be slowed considerably to match the pace of the game so strafe jumping might not really be available or even useful.
3. any talk about q4 is major speculation since it's only known to use the d3 engine at this point, no word on the pace of the game (will be single player focused though)
4. If they want strafe jumping available the physics engine will allow it regardless of the rendering engine. Strafe jumping started as a bug but that bug was fixed long ago and the code modified to continue to allow it.
I can easily see past 60 fps. I fade somewhere between 80 to 110.
There are demos you can use, which are usually used by me to show that 30fps isn't enough
. I guess if you spin really fast, a bit over 60 helps, and doom3 is the kind of game where you'd do that.
One thing I know for certain is....
There were several key jumps that I simply could NOT do in Quake 2 with my Voodoo 2 card.....that I could end up doing when I got my Voodoo 3 card.
There were several key jumps that I simply could NOT do in Quake 2 with my Voodoo 2 card.....that I could end up doing when I got my Voodoo 3 card.
Voodoo cards
"Mem'ries,
Like the corners of my mind
Misty water-colored memories
Of the way we were"
Yeah...that's true methinks. I usually use /com_maxfps 125 and it pretty much stays pegged there without changing.
but there is no benefit to not locking it since you can't see >60fps anyway.... so who cares
When are people going to learn that maybe you cant see 60fps but you can sure as hell feel it.
Play Quake 3 at 60 fps then crank it up to 160 and tell me you dont feel a big change!
When are people going to learn that maybe you cant see 60fps but you can sure as hell feel it.
Play Quake 3 at 60 fps then crank it up to 160 and tell me you dont feel a big change!
BFG10K
Lifer
- Aug 14, 2000
- 22,709
- 3,000
- 126
If he's simply capping the engine then it's nothing new as the game's internal calculations should alwasys run at a fixed and constant speed and they shouldn't be tied to the framerate at all.
If he's also capping the renderer then that could cause problems, especially if the cap is detrimental to the minimum framerate like vsync is.
If he's also capping the renderer then that could cause problems, especially if the cap is detrimental to the minimum framerate like vsync is.
ViRGE
Elite Member, Moderator Emeritus
- Oct 9, 1999
- 31,516
- 167
- 106
While there isn't enough information to make a definite conclusion, here's the best guess of what's going on:
* The game engine's "tic" rate(that is, the world update rate) is being locked at 60hz, or 60 updates a second
* Quake 3 and before this had a lower rate(closer to 20hz)
* A video card can only render a different frame when it has different information to work with
* Quake 3 allowed for additional frames by using interpolation to guess what's happening between tics, and render based off of that
* Doom 3 will not use interpolation; this is because interpolation causes <100% accuracy in movement, resulting in things like "better" jumps in Q3 when you were doing more than 90FPS, where this errors added up
* Because Doom 3 will not use interpolation, there is an absolute maximum of 60 different world states in a second, meaning that there are a maximum of 60 different frames in a second
* Because there can only be 60 frames, you lock the framerate at 60 seconds so that you don't get bursts of repeated frames, resulting in uneven flow(Q3 was always even because of interpolation)
D3 is not a "twitchy" shooter mind you, so even though some people may be able to feel a difference, it does not mean it will be as noticable in a slower-paced game. Oh, and as for benchmarks:
* The typically benchmark method is to either playback a scene, rendering as many frames per second as possible; this relies on interpolation also(since a playback also has tics). The alternate way is to simply have a set number of frames(, and render those back as fast as possible(by having each tic progress after a frame is rendered, instead of basing it on a clock); this is what a D3 benchmark would do
* The game engine's "tic" rate(that is, the world update rate) is being locked at 60hz, or 60 updates a second
* Quake 3 and before this had a lower rate(closer to 20hz)
* A video card can only render a different frame when it has different information to work with
* Quake 3 allowed for additional frames by using interpolation to guess what's happening between tics, and render based off of that
* Doom 3 will not use interpolation; this is because interpolation causes <100% accuracy in movement, resulting in things like "better" jumps in Q3 when you were doing more than 90FPS, where this errors added up
* Because Doom 3 will not use interpolation, there is an absolute maximum of 60 different world states in a second, meaning that there are a maximum of 60 different frames in a second
* Because there can only be 60 frames, you lock the framerate at 60 seconds so that you don't get bursts of repeated frames, resulting in uneven flow(Q3 was always even because of interpolation)
D3 is not a "twitchy" shooter mind you, so even though some people may be able to feel a difference, it does not mean it will be as noticable in a slower-paced game. Oh, and as for benchmarks:
* The typically benchmark method is to either playback a scene, rendering as many frames per second as possible; this relies on interpolation also(since a playback also has tics). The alternate way is to simply have a set number of frames(, and render those back as fast as possible(by having each tic progress after a frame is rendered, instead of basing it on a clock); this is what a D3 benchmark would do
Doom 1-2 have a cap of 35 and they run at the required speed even now, not at 1000+FPS.
I find 35 FPS absolutely enough for DooM. DooM III will have a pretty high cap IMO, the gameplay will be most likely slower than in Q3.
I find 35 FPS absolutely enough for DooM. DooM III will have a pretty high cap IMO, the gameplay will be most likely slower than in Q3.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 24K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 20K
-
-
-
Facebook
Twitter