Editrpy Won't see Driver Names

Using Editrypy 3.0 with Indycar II, I only get car numbers in the fields when trying to assign driver names in the "edit car ID" menu item. The problem relates to the difference between the Driver.txt and Driver2.txt files. When I use the driver2 file instead of the driver file, the names seem to come up o.k. Anyone know the purpose of the 2 files, and a fix for the editrpy problem?

Quoted text (7 lines)

>Using Editrypy 3.0 with Indycar II, I only get car numbers in the >fields when trying to assign driver names in the "edit car ID" menu >item. The problem relates to the difference between the Driver.txt and >Driver2.txt files. When I use the driver2 file instead of the driver >file, the names seem to come up o.k. >Anyone know the purpose of the 2 files, and a fix for the editrpy >problem?

(This was my original post) I found the problem in editrpy was the "NUMDR" field in the drivers.txt file. Anything over 32 causes the names not to be read when editing the car id of the lap! I'm still wondering why each car set has a drivers.txt and drivers2.txt file?

: I'm still wondering why each car set has a drivers.txt and : drivers2.txt file? If I remember correctly, the drivers.txt file is there in case something happens to the drivers2.txt file. The program will default to the drivers.txt file if it has trouble with the other one. -- **************************** Michael E. Carver ************************* Upside out, or inside down...False alarm the only game in town. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

>I'm still wondering why each car set has a drivers.txt and >drivers2.txt file? The DRIVERS.TXT file is really around just in case you should accidently muck up your DRIVERS2.TXT file. Since you you only ever edit the drivers2 file the drivers file is there just in case. It also contains comments so that you can figure out what the different values correspond to. --- Frank ---

Quoted text (12 lines)

>>Using Editrypy 3.0 with Indycar II, I only get car numbers in the >>fields when trying to assign driver names in the "edit car ID" menu >>item. The problem relates to the difference between the Driver.txt and >>Driver2.txt files. When I use the driver2 file instead of the driver >>file, the names seem to come up o.k. >>Anyone know the purpose of the 2 files, and a fix for the editrpy >>problem? >(This was my original post) I found the problem in editrpy was the >"NUMDR" field in the drivers.txt file. Anything over 32 causes the >names not to be read when editing the car id of the lap!

In Editrpy, I used the NUMDR field as an indicator to tell me how many fields to skip over to get to the driver's name. I had the assumption that Indycar 2 drivers[2].txt files would always have NUMDR set to 32. There is a new version of Editrpy (version 3.1) which fixes this problem and a number of others (in particular the inoperative scroll bar). You can get the new version at: http://www.millcomm.com/~corrigan/editrpy.html I think the purpose was so that you could modify your drivers2.txt file, but leave the drivers.txt alone. Then if anything went wrong you just delete drivers2.txt and the game keeps working. -- Mike Corrigan

<Snipped> Hey Mike: I've just started to really get into using Editrpy 3.0, and I just wanted to say a big THANK YOU for creating the program. I've been using the utility that allows you to superimpose two replays on top of each other, and by using one of my laps combined with one of the really hot laps from Surfer's Paradise, I have managed to lower my lap times dramatically just by analyzing where I was losing so much time. I'm sure that as I play with the program a bit more I'll find some other really helpful goodies, but for now I'm very impressed with how much it has helped to improve my driving. Just wanted to let you know your work is appreciated! Ian McIlroy Ottawa, Ontario, Canada

says... Thanks for the kind words. You really should upgrade to v3.3 (available by anon ftp at didnt.doit.wisc.edu or at http://www.millcomm.com/~corrigan/editrpy.html v3.0 had a number of embarassing bugs. -- Mike Corrigan

says... Another bug! I just had another bug pointed out to me tonight that I have now fixed. This bug only occurred if you got the message "position > track len". After that message showed up, unpredictable crashes could occur. This is now fixed in v3.4. As a bonus, I've added a feature to the Race Report which will show time behind the leader as each car finishes a lap. As before, you can get v3.4 at http://www.millcomm.com/~corrigan/editrpy.html -- Mike Corrigan

Quoted text (14 lines)

>says... >>Thanks for the kind words. >>You really should upgrade to v3.3 .... >>v3.0 had a number of embarassing bugs. >Another bug! I just had another bug pointed out to me tonight >that I have now fixed. This bug only occurred if you got the >message "position > track len". After that message showed up, >unpredictable crashes could occur. This is now fixed in v3.4. >As a bonus, I've added a feature to the Race Report which will >show time behind the leader as each car finishes a lap. >As before, you can get v3.4 at >http://www.millcomm.com/~corrigan/editrpy.html

Mike, we all owe you many, many thank-yous. Your support for your program and speed to repair bugs is admirable... Papyrus could learn a thing or two from your example. Keep up the good work.