Before I hear the words "foul", here are the results for ICR2:
Well I thought I would do a controlled experiment to see how much ICR2
plays with time. There's GOOD news & BAD news.
: The BAD news is that GP2 wrecks havoc with the 4th dimension.
The GOOD news is that ICR2 plays consistant with the 4th dimension.
For the ICR2 test I took a replay of a lap and replayed it with maximum
graphics details in SVGA and again with minumum graphics in VGA. This
was the same setup I used for GP2.
Results:
: Internal GP2 Time 1:24.623
Internal ICR2 Time 1:30.94
: Real Time (SVGA ~300% occupancy) 3:43.86 (+164.5%)
ICR2 Real Time (SVGA max detail) 1:32.84 (+2.20%)
: Real Time (VGA ~31.5% occupancy) 1:20.07 (-5.4%)
ICR2 Real Time (VGA min detail) 1:32.84 (+2.20%)
The BAD news is that ICR2 does not accurately reflect real time. Also
there is the related bad news that when ICR2 drops frames to keep time
consistant, this can wreck havoc with feedback and over-compensating
with the wheel/gas/brakes. However, by playing with the min/max display
and tweaking the graphics to AUTO/OFF/ON one can come close to getting a
fairly balanced frame rate. Except for occasions when the traffic is
really bunched up.
For the record these tests were run on the same machine under the same
conditions.
Gateway2000 P5-90
16 meg of memory
ATI Mach64 video card w/2meg memory
m64vbe installed with vesa extensions 2.0
--
**************************** Michael E. Carver *************************
Upside out, or inside down...False alarm the only game in town.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=
Well I thought I would do a controlled experiment to see how much GP2
plays with time. There's BAD news & GOOD news.
The BAD news is that GP2 wrecks havoc with the 4th dimension.
For the test I took a saved Hot Lap and replayed in with maximum
graphics detail in SVGA and again with minimum graphics in VGA. The
results:
Internal GP2 Time 1:24.623
Real Time (SVGA ~300% occupancy) 3:43.86 (+164.5%)
Real Time (VGA ~31.5% occupancy) 1:20.07 (-5.4%)
The GOOD news is that the lower the CPU occupancy, the less GP2 plays
with reality. Thus finding a balanced fps can limit the effects of
telescoping time. Of course this is also bad news at tracks where the
occupancy rate fluctuates widely.
I still don't like the idea of having real time accordion while I'm
trying to do battle or hot-lapping. Since we are talking about
split-second reactions and rhythm. The way GP2 works there is no way to
keep time from yo-yo'ing about, thus making consistant laps extremely
difficult. This is especially true during races or qualifying due to
occupancy fluctuations with traffic.
"When you are courting a nice girl an hour seems like a second. When you
sit on a red-hot cinder a second seems like an hour. That's relativity."
Albert Einstein (1879-1955), German-American theoretical physicist.
Quoted in: News Chronicle (14 March 1949).
--
**************************** Michael E. Carver *************************
Upside out, or inside down...False alarm the only game in town.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Before I hear the words "foul", here are the results for ICR2:
[time comparisons snipped]
You're right Michael, but I prefer Papyrys' approach to handle processor
suffocation (sp?). In GP2, it comes REALLY hard to get your braking
points
and turn-in points correct if your car takes 10 real-time seconds to
travel
50 meters. Granted, if you get 3 fps in ICR2, controlling the car is
difficult but at least you know where you are on the track after one
second (if you count seconds to determine your turn-in points, like I
sometimes do) to get the turning point right. Also, as you said, ICR2
and NASCAR can drop graphics details when needed to maintain frame rate.
Of course, some of the graphics, like trackside objects are better be
turned
on to keep your braking marks :-)
--
Henrikki (Hena) Hakkanen Tel. +358-(9)0-345 5538
------- The best way to accelerate a Mac is 9.81 m/s2 --------
--------------------------------------------------------------
Disclaimer: Opinions expressed here are mine and does not
necessarily reflect those of my employer!
