>A lot of people have talked about the missing two frames..
>Use the estimated framerate-2. Of cause I tried it, and it works :-)
>But in my opinion, you don't get more frames. Instead you get less
>difference between the fastest and the slowest framerate. That way the
>games seems smoother, you don't get a drop when you pass the grand
>stands, or when closing up to others cars.
>As I see it, you don't get more than the frame rate you request, even if
>the occupancy drops to under 50%. Therefore I think that the -2 frames,
>is simply a matter of the calculated framerate being a little
>optimistic.
>I don't think the games uses that much time on calculating anything from
>the frame-rate settings, other than it seems like real-time is slowed
>down when occupancy rises abowe 100%.
>If the frame-rate was increased simply by changing the settings, there
>would have to be a MAJOR BUG in the program, and from what I have seen,
>there is not.... (Best that way)
ok...if U set the frame rate -2 it just lowers your processor
occupancy and the game runs faster only because it shows less frames
per second WITHOUT lowering graphic details and thats why it seems to
run faster becasue there is no slowdowns or jerkiness. But the average
fps rate is lowered by that 2 fps.
This -2 fps was set to avoid sudden slowdowns...and give U a little
room for processor...its a good idea to setup the details so that the
occupancy isnt over 80% when driving alone...so that there is room
for "hotter action" and thus higher occupancy.
Generally its a a good idea to lower fps if U have it already over
20....and the game looks much smoother because the occupancy wont go
over 100%. But its not very wise to do it if U already have it around
15 fps...the game wont look very smooth with 13 fps.
Personally I always go for higher frame rate so I rather lower the
details than fps...
~~~~~~~~~~~~~~~~~~~~~~<Ville Kopu>~~~~~~~~~~~~~~~~~~~~~~~~~~
ViK at IRC, #f1 & #gp2 http://koti.kolumbus.fi/~vkopu
~~~~~~~~~~~~~~~~~<Second is first of loserS>~~~~~~~~~~~~~~~~