rec.autos.simulators

by **Greg Cis** » Mon, 26 Nov 2001 13:21:53

> Runs fine on my Athlon 750 with a $100 Geforce2 MX. Frame
> rates are often over 50 fps. FF doesn't cause too much of
> a frame rate hit.

I ran F1 2001 and then F1 2000 CS. The main difference seems
to be that F1 2001 looks to be in software mode. F1 2000 CS
is very clear and crisp at 800x600. F1 2001 is blocky and
does not appear to have the hardware acceleration working.

Do I need to try the V5 beta drivers?

Thanks,
Greg

by **Eldre** » Mon, 26 Nov 2001 15:37:42

>Guys...I still think this games sucks only because I still cannot calibrate
>my TSW in spilt axis mode (even with the patch). An $800.00 US controller
>and the game will not read it right. It is calibrated with windows properly.
>I want in on the fun!!!!

Which TSW do you have? My TSW2mod works fine... Hold down the pedals halfway
when you start the game until you go to the config screen. Also, everytime you
want to race, hold the brake pedal from the race day select screen until you
get on the track. Half-assed(maybe quarter-assed<g>), I know - but it works...

Eldred
--
Dale Earnhardt, Sr. R.I.P. 1951-2001
Homepage - http://www.umich.edu/~epickett
GPLRank - under construction...

Never argue with an idiot. He brings you down to his level, then beats you
with experience...
Remove SPAM-OFF to reply.

by **istof** » Mon, 26 Nov 2001 20:27:00

i suspect texture memory might be your problem.

see if this guy can help you.

http://www.drivingitalia.com/f12k1tutorial/englishindex3.htm

Regards all,
istoff

by **Vic Greenwoo** » Tue, 27 Nov 2001 03:32:08

How do I tell the framerate?
Thanks
Vic

> You're hurting for RAM - 128Mb isn't enough these days, plus it's dirt
> cheap. I have a PIII 850, 384Mb RAM, GeForce 2 Pro/64. The game kills in
> test mode (50-55), and gets pretty good framerates in races, too (~30-35)
> If you can spare $60 or so, get another stick of RAM in there - it'll really
> help out.

> > > Try the advanced options document for suggested FF settings for popular
> > > wheels, may get even better :)

> > The stock FF settings are pretty good on my Logitech Formula
> > FF wheel. However, the framerate totally sucks (it did before
> > the patch). I have a P3-750, 128MB ram, Voodoo5 5500. F1 2000 CS
> > was awesome at 800x600 with full detail. This game blows at
> > 800x600 and 640x480 at any detail setting. I even went into the
> > PLR file and edited the # of visable cars to 4. Why isn't this
> > and option in the game? Anyway it doesn't matter because the
> > performance afterwards is unchanged. The framerate just sucks...

> > Too bad because IMHO the FF in F1 2001 is better than GPL. But
> > I am *NOT* going to do strictly TEST sessions. In TEST sessions
> > the framerate is great until *ANY* other car is in the area. Then
> > it is crap.

> > --

by **briGu** » Tue, 27 Nov 2001 03:46:42

.

If you have the patched version (available at
http://common.ea-europe.com/f12k1/f12001update.zip) then all you have to do
is hit ctrl-F. If you have the original version, you'll need to get the
FRAPS program (www.fraps.com)...

by **Greg Cisk** » Tue, 27 Nov 2001 04:35:58

I have a Logitech Formula Force original and there is no drop
in framerate with FF enabled.

--

> Pat,

> What wheel do you use (assuming you use a wheel)? With my act labs FF my
> frame rate drops 20-30 fps when enabling force feedback.

> Todd

> > > The stock FF settings are pretty good on my Logitech Formula
> > > FF wheel. However, the framerate totally sucks (it did before
> > > the patch). I have a P3-750, 128MB ram, Voodoo5 5500. F1 2000 CS

> > Runs fine on my Athlon 750 with a $100 Geforce2 MX. Frame
> > rates are often over 50 fps. FF doesn't cause too much of
> > a frame rate hit.

> > --
> > Pat Dotson

by **Greg Cis** » Tue, 27 Nov 2001 04:34:45

> i suspect texture memory might be your problem.

The problem was RAM. I went from 128MB to 384MB and
from 4 visable cars to 15, and it is silky smooth on
my P3-750.

Thanks!

by **Greg Cis** » Tue, 27 Nov 2001 04:36:03

I have it at 15 :-)

--

by **Greg Cis** » Tue, 27 Nov 2001 04:39:41

> Make sure you set other cars to LOW detail, otherwise you're *** the V5.

I have them at full detail :-)

Actually it is still kicking. As you may have seen, my problem was
RAM. Thanks anyway though.

It was the number of visible cars... What is LOD?

--

by **David G Fishe** » Tue, 27 Nov 2001 05:29:33

I thought you were talking about the LOD too.

The setting ranges form 1 to 4. It adjusts how soon the cars disappear from
your view in the distance. 1 is the default setting. If you set it to 4, the
cars will stay viewable at a greater distance, but it kills your frame rate.

You can chnage it by editing the LODMultiplier line in the "default" file in
C:\Program Files\EA SPORTS\F1 2001\Save

David G Fisher

> > Make sure you set other cars to LOW detail, otherwise you're *** the
V5.

> I have them at full detail :-)

> > It should get better with this setting. Also no AA and 16-bit graphics.
A
> > little more ram should help a bit since my old system was close yet I
had
> > better performance.

> > Unfortunately, the V5 now basically sucks (ouch, it hurts saying that!).
I

> Actually it is still kicking. As you may have seen, my problem was
> RAM. Thanks anyway though.

> > was running a PIII 672 (o/c) w/256 mb ram and a V5 and got 10 fps in
race
> > with mid detail (running everything low got me over 20 when the cars
spread
> > out). Upgraded to an AMD 1600+ w/512 MB ram and jumped to 20+ fps with
high
> > detail graphics. Upgraded to a GF3 Ti 500 and get 50 fps in race with
all
> > graphics FULL over 80 fps testing. V5 is sadly over the hill.

> > PS-Setting other cars LOD to 4 isn't the number of cars it's a distance
with
> > 4 being quite high so fps should suck.

> It was the number of visible cars... What is LOD?

> --

by **briGu** » Tue, 27 Nov 2001 06:03:48

This is the wrong way to do it - we've talked about this before on the High
Gear forums. I quote from Simon Philips:

If you want to see cars more than 100m down the road, then the key is in the
f1car.gen file....

modify the lines that contain the "VD" references from something like...

<MAX> MeshFile=<1234>vd.MTS CollTarget=False HATTarget=False LODIn=(18.0)
LODOut=(140.0)

to something like

<MAX> MeshFile=<1234>vd.MTS CollTarget=False HATTarget=False LODIn=(18.0)
LODOut=(500.0)

just for info, the "VD" lines are used to determine at which distance the
low detail models (referenced by the D suffix) are used... in the above
example, between 18 and 140 meters.

There were a couple of threads on this during the first burst of posts on
this forum after the release of the game, and I think this is also on
Jenson's F1 FAQ page.

Changing the global LOD-multiplier setting (in the default.cfg) will only
put more strain on your system, as MANY more polygons are being pushed. The
method above (f1car.gen) will only increase the number of polys by a tiny
amount.

by **David G Fishe** » Tue, 27 Nov 2001 07:14:48

Great. Thanks for the info.

David G Fisher

> > I thought you were talking about the LOD too.

> > The setting ranges form 1 to 4. It adjusts how soon the cars disappear
> from
> > your view in the distance. 1 is the default setting. If you set it to 4,
> the
> > cars will stay viewable at a greater distance, but it kills your frame
> rate.

> > You can chnage it by editing the LODMultiplier line in the "default"
file
> in
> > C:\Program Files\EA SPORTS\F1 2001\Save

> This is the wrong way to do it - we've talked about this before on the
High
> Gear forums. I quote from Simon Philips:

> If you want to see cars more than 100m down the road, then the key is in
the
> f1car.gen file....

> modify the lines that contain the "VD" references from something like...

> <MAX> MeshFile=<1234>vd.MTS CollTarget=False HATTarget=False LODIn=(18.0)
> LODOut=(140.0)

> to something like

> <MAX> MeshFile=<1234>vd.MTS CollTarget=False HATTarget=False LODIn=(18.0)
> LODOut=(500.0)

> just for info, the "VD" lines are used to determine at which distance the
> low detail models (referenced by the D suffix) are used... in the above
> example, between 18 and 140 meters.

> There were a couple of threads on this during the first burst of posts on
> this forum after the release of the game, and I think this is also on
> Jenson's F1 FAQ page.

> Changing the global LOD-multiplier setting (in the default.cfg) will only
> put more strain on your system, as MANY more polygons are being pushed.
The
> method above (f1car.gen) will only increase the number of polys by a tiny
> amount.

by **Don Burnett** » Tue, 27 Nov 2001 08:40:57

I played around with the LOD multiplier line in the default file.
I changed it from 1 to 2, and it made a big difference on when the cars in
front dissapear, at almost no frame rate hit for me.
Starting at the back of a full field of cars in Germany, I get 23-25 fps and
after the first turn it gets into the low 30's. I saw almost no difference
in my framerate between 1 and 2 LOD.

Don Burnette

> Great. Thanks for the info.

> David G Fisher

> > > I thought you were talking about the LOD too.

> > > The setting ranges form 1 to 4. It adjusts how soon the cars disappear
> > from
> > > your view in the distance. 1 is the default setting. If you set it to
4,
> > the
> > > cars will stay viewable at a greater distance, but it kills your frame
> > rate.

> > > You can chnage it by editing the LODMultiplier line in the "default"
> file
> > in
> > > C:\Program Files\EA SPORTS\F1 2001\Save

> > This is the wrong way to do it - we've talked about this before on the
> High
> > Gear forums. I quote from Simon Philips:

> > If you want to see cars more than 100m down the road, then the key is in
> the
> > f1car.gen file....

> > modify the lines that contain the "VD" references from something like...

> > <MAX> MeshFile=<1234>vd.MTS CollTarget=False HATTarget=False
LODIn=(18.0)
> > LODOut=(140.0)

> > to something like

> > <MAX> MeshFile=<1234>vd.MTS CollTarget=False HATTarget=False
LODIn=(18.0)
> > LODOut=(500.0)

> > just for info, the "VD" lines are used to determine at which distance
the
> > low detail models (referenced by the D suffix) are used... in the above
> > example, between 18 and 140 meters.

> > There were a couple of threads on this during the first burst of posts
on
> > this forum after the release of the game, and I think this is also on
> > Jenson's F1 FAQ page.

> > Changing the global LOD-multiplier setting (in the default.cfg) will
only
> > put more strain on your system, as MANY more polygons are being pushed.
> The
> > method above (f1car.gen) will only increase the number of polys by a
tiny
> > amount.

by **STP** » Wed, 28 Nov 2001 01:30:21

Stop being a cheap bastard and buy a GF3 or Radeon 8500.

by **Greg Cis** » Thu, 29 Nov 2001 05:09:20

> > Namely: I have a V5 5500. After I got the game running with
> > DX 8.1, the framerate was about 2 seconds per frame or
> > worse. I read that you had to do the windowed mode thing
> > for Nvidia cards but I presumed the Voodoo5 would be OK.
> > Any suggestions?

> Stop being a cheap bastard and buy a GF3 or Radeon 8500.

Yeah? Who the hell are you anyway?

--

rec.autos.simulators

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)

F1 2001 PATCH (beta)