rec.autos.simulators

I have these mod's for F12002: GTR2002/AR147/M3C

When I run a championship now and then the program Crash To Desktop...:(
I can't see anything wrong anywhere....
I can run 2-3-4 or 5 tracks of the Chpship, and then suddenly, when the
next track is loaded, it CTD...:( What the f*** is wrong? :(

System:
Athlon 1000 MHz
512MB ram
Ti4200/128MB

AND...I have the standard font for the desktop, my res. is 1024/768,
I have copied the last half of the *.cfg-file to the GTR2002/AR147/M3C -
*.cfg's...

...BTW: everything else runs fine , and have for years...
(RM/STCC2/F12001/F1RC/LFS/...)

Annoying....:(

Best regards
Thore_DK

    I haven't done much with the championships, but on the surface this
sounds like an incorrect entry in your championship game.gdb   Perhaps it's
looking for a track you don't have.   Hopefully somebody here will chip in
with more advice.  Is it the same track each time?
dave henrie

Hi Dave and thx for the reply...

No, it's not the same track each time....
For example: I can start a new championship with 16 tracks, drive track
1-2, then it's CTD...The championship is saved automatically, and I can
restart the game and go on with tracks 3 and 4, then its CTD on the 5.
track. Restart the game again, then maybe I can run the championship on
track 6, then CTD...then restart and run track 7-8-9 and so on...

Right now 1 hour ago I ran the 10. and 11. track without problems, and
then on the 12. (Silverstone) it CTD's...restart of game, and
Silverstone was done..:) Next track (13) was Hungary, and the track
loads, I click the right arrow (next session) 4 times to get to RACE,
and ...CTD when the the race is about to begin...:(

All thsi is in the M3- mod...but every time i run the AR147 mod I have
the same problem.
I also experienced same problems in the GTR2002.

A very funny problem in the GTR2002:

On France (Magny C) I had the CTD in the last corner before the
start/finish line almost every time I tried...also in Single Race
mode...:)

As I see it, I think it's a graphic problem, and the reason on Magny C.
could be the heavy graphics on the start/finish line (spectator stands
and so...)(?)

I have been fiddling with the graphic details, but nothing helps-..:(

Best regards
Thore_DK

Maybe this is the same problem I'm having with GTR 2K2...  Occasionally GTR
and M3C will CTD during the loading-track screen.  The track loading seems
to take a good 30 seconds or so, and seems more likely to CTD if I make any
controller inputs...i.e. impatiently tapping a pedal while waiting for the
track to load... :)  Seems to happen with any of the tracks.  Haven't
noticed it happening with the new BPR mod or the ARC147 mod, although I'm
trying not to tap pedals anymore...;)   GTR is patched to the 1.2 version w/
all of the car and track updates, running at 1600x1200x32 resolution...   My
system: WinXP w/ Serv. Pack 1, DX 8.1, Audio Audigy soundcard, Radeon
9700AGP, TSW2 Modified wheel (4 axes, 4 buttons).   Not sure what to suggest
to you, except to avoid making controller inputs during loading screens.

Sean

   I wonder if it is not a soundcard problem.  Your reply cleared up a few
issues.  It sounds like F1 2k2 doesn't release all of the available
resources when it has finished a race.  One or two races later...boom you
run out of usuable memory.  The Simple solution...tho not a very convienant
one....is to reboot between each round.  
  I would double check your IRQ settings and make sure the Video and sound
cards are not sharing an IRQ number with other devices.  After
that...Perhaps updating the soundcard drivers...even reducing things in the
bios like the AGP setting or the PCI latency timer.  But that is kinda just
taking blind stabs at what 'could' be a solution.  
keep us posted.
dave henrie

Dont know that this helps at all, but I just bought a new computer and for the
first time, loaded f1 and gtr2002.  Everytime I loaded GTR it would CTD at the
race menu.  Since I bought this computer just for my racing sims, I brought it
back.  It turned out to be nothing more than getting the new drivers for my
Nvidia card.  The ones with the card were several months old.  Although this
isn't exactly the same problem, I thought I would pass it along.

Mike