finish it. If not, it will be over 1000 laps at Martinsville in 4 days
I did the exact same thing. I did notice there were one or more cars that
didn't exactly pit, but just hung in the pit lane, apparently out of their
assigned stall, and so never registered as pitting. I tried bumping them,
gently, nudging them out of the pit wall lane and then they would zoom around
and re-pit. That fixed it. Like you did, the best trick is to save often,
especially late in the race, so if you have to do the bump bit and it doesn't
work, you don't have to repeat a significant number of laps.
On my first try, I initially raced a Quick Race, to see how my setup would work
under race conditions. After I completed 100 or so laps, I decided to convert
that race into a Championship race, by entering the championship, then resume
game=yes, and off I went, until the race ended, and the "quit race weekend?"
prompt came up, and I stupidly realize that I just wasted running a complete
race, and not having it count for my points.
Going into the *.txt file and cutting the field of cars I didn't want to do, as
suggested by someone else. If your championship is with 39 cars, and you edit
the car lines from 40 to say, 37 (so that 36 would actually race), the bottom
four cars get dropped. I had my carset arranged by car number, so all of a
sudden the high number cars, like the 88, the 94, the 99, to name 3 big names,
weren't going to be in the race. Not liking that, I decided to simply move 4
other cars from the list, but this also created points problems, as the points
assume that the carset order doesn't change. So, for example, if the #1 car of
Steve Parks is first on your list, and he is 30th in points, and you now move
him out of the carset, and now the 2 car is now the first car down the list,
well, Rusty Wallace now is shown as 30th in points. In short, whatever order
your carset is arranged to start the championship year is the order you need to
keep things to not have wild points changes from previous races.
Martinsville is the only track that I have seen this problem occur at. Yet.