rec.autos.simulators

How to make F12001 cars not disappear so soon?

Phillip Arche

How to make F12001 cars not disappear so soon?

by Phillip Arche » Wed, 05 Dec 2001 09:07:45

I realise this  has been asked and answered before, but I've formated my
H/Drive and didn't keep the relevent messages and our news server only keeps
messages a couple of days. So the question is: what do I need to change in
F1 2001 to have the AI cars not disappear so quickly.
At the moment they're gone when they get 50 metres up the track.
                            TIA...
                            Phillip...
STP

How to make F12001 cars not disappear so soon?

by STP » Wed, 05 Dec 2001 10:30:04


Open the "default.cfg" file in your F12001/Save/ folder. Scroll down to
LocalCam=COCKPIT and change LODMultiplier=(1.000000) to 2.000000 or
3.000000.

Phillip Arche

How to make F12001 cars not disappear so soon?

by Phillip Arche » Wed, 05 Dec 2001 11:00:58


STP,
       Thanks muchly for the info, I knew it was in a config or ini file
somewhere, but couldn't find it.
                                    Cheers...
                                    Phillip...

teehol

How to make F12001 cars not disappear so soon?

by teehol » Wed, 05 Dec 2001 12:54:50

On Tue, 4 Dec 2001 13:00:58 +1100, "Phillip Archer"




>> Open the "default.cfg" file in your F12001/Save/ folder. Scroll down to
>> LocalCam=COCKPIT and change LODMultiplier=(1.000000) to 2.000000 or
>> 3.000000.

>STP,
>       Thanks muchly for the info, I knew it was in a config or ini file
>somewhere, but couldn't find it.

 That does the trick, but there's another setting to change this also,
which was claimed to not use up so much CPU-video power.

 There was a post about how to do this, and with little/no frame-rate
hit. Unfortunately, I don't have the old post, and never did
understand (exactly) what to change. I do remember it had something to
do with pixel display (?).

 Matt

Don Burnett

How to make F12001 cars not disappear so soon?

by Don Burnett » Wed, 05 Dec 2001 13:05:41


> On Tue, 4 Dec 2001 13:00:58 +1100, "Phillip Archer"



> >> Open the "default.cfg" file in your F12001/Save/ folder. Scroll down to
> >> LocalCam=COCKPIT and change LODMultiplier=(1.000000) to 2.000000 or
> >> 3.000000.

> >STP,
> >       Thanks muchly for the info, I knew it was in a config or ini file
> >somewhere, but couldn't find it.

>  That does the trick, but there's another setting to change this also,
> which was claimed to not use up so much CPU-video power.

>  There was a post about how to do this, and with little/no frame-rate
> hit. Unfortunately, I don't have the old post, and never did
> understand (exactly) what to change. I do remember it had something to
> do with pixel display (?).

>  Matt

I changed the lod as above to 2, it made a big difference with no noticeable
framerate hit.

Don Burnette

David G Fishe

How to make F12001 cars not disappear so soon?

by David G Fishe » Wed, 05 Dec 2001 15:35:48

From another post:

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.

David G Fisher


Bria

How to make F12001 cars not disappear so soon?

by Bria » Wed, 05 Dec 2001 17:34:05

Is this the same with F1CS2000? I am talking about the GenVeh??.prt files
where I can see a line, in the very first session with:

  ObjFile=VIRVD LODIn=(5.0) LODMid=(100.0) LODOut=(140.0) SphereTarget=False
HatTarget=False CollTarget=TRUE OmniShade=True

Thanks,

Brian



> From another post:

> 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.

> David G Fisher



> > I realise this  has been asked and answered before, but I've formated my
> > H/Drive and didn't keep the relevent messages and our news server only
> keeps
> > messages a couple of days. So the question is: what do I need to change
in
> > F1 2001 to have the AI cars not disappear so quickly.
> > At the moment they're gone when they get 50 metres up the track.
> >                             TIA...
> >                             Phillip...

David G Fishe

How to make F12001 cars not disappear so soon?

by David G Fishe » Thu, 06 Dec 2001 04:36:29

I don't know about F1CS2000.

David G Fisher


> Is this the same with F1CS2000? I am talking about the GenVeh??.prt files
> where I can see a line, in the very first session with:

>   ObjFile=VIRVD LODIn=(5.0) LODMid=(100.0) LODOut=(140.0)
SphereTarget=False
> HatTarget=False CollTarget=TRUE OmniShade=True

> Thanks,

> Brian



> > From another post:

> > 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.

> > David G Fisher



> > > I realise this  has been asked and answered before, but I've formated
my
> > > H/Drive and didn't keep the relevent messages and our news server only
> > keeps
> > > messages a couple of days. So the question is: what do I need to
change
> in
> > > F1 2001 to have the AI cars not disappear so quickly.
> > > At the moment they're gone when they get 50 metres up the track.
> > >                             TIA...
> > >                             Phillip...


rec.autos.simulators is a usenet newsgroup formed in December, 1993. As this group was always unmoderated there may be some spam or off topic articles included. Some links do point back to racesimcentral.net as we could not validate the original address. Please report any pages that you believe warrant deletion from this archive (include the link in your email). RaceSimCentral.net is in no way responsible and does not endorse any of the content herein.