With millions of people World-wide upgrading to Windows '95, I think
that there really is a need for a good "control centre" for F1GP that
runs under Windows and prevents novice users from having to dip into
DOS to apply all the patches. I was in the process of writing a
something along these lines, but stopped because GP II was supposedly
coming out soon. However, I spoke with a friend in the trade, who
told me that a Microprose employee had told him that there wasn't a
hope in hell of Microprose shipping GP II before Christmas. So, I've
started working on it again. Although we have lots of amazing patches
for F1GP/WC, I don't believe anyone has actually written something for
Windows that lets you combine everything. If you want to see just
how brilliantly useful something like this can be, check out Oliver
Roberts' F1GP-Ed on the Amiga.
When it is finished, it will do everything that GPED can do, as well as
changing the external view camera setup (my own invention, ported from the
Amiga version of my editor), crash damage (ala GPDAMED) including the way
the marshals react to crashed cars (ala GPFLAG). Obviously, the user interface
for this will not be a case of entering numbers on the command line, but will
instead have stuff like scroll bars for setting time delays in seconds,
accident speeds in MPH etc. As well as this, the utility will allow GPLAPTIM,
GPPERF and GPGAP to be configured using the same method. It will build the
user a batch file in their F1GP directory, and on clicking on a button or
menu option will launch the batch file to run F1GP/WC with the patches
enabled/configured where needed.
Plus, I'm thinking of including a bridge between the performance of the real
cars and drivers and their computer representations in F1GP/WC. Anyone
who's seen my Amiga editor (F1Ed) will know that this means a kind of built
in "database" where you enter in real recorded lap times from qualifying
and races, you then give the editor a horsepower range to work with (eg.
the slowest team to have 700 BHP, the fastest 1000 BHP), and it will go away
and produce the appropriate BHP figures for the teams, and the qualifying
and racing figures for each driver. My tests with the Amiga version of F1GP
proved that although far from faultless, this method generally put the right
cars in the right place on the grid. For instance, last year Michael Schumacher
and Damon Hill often qualified in pole, whilst Jos Verstappen would be back
in about 10th, and the Pacific cars would be way down at the back of the grid.
O.K., you can do this by inventing the figures yourself, but by using this
system, you don't really have to think about it, just copy type a few lap
times :-)
For other editor writers, the offsets of the .exe file will all be in the
ini file (my idea to make it easy to add new versions of GP.EXE without
having to rebuild or redistribute the application). The .ini file will be
commented, so you'll be able to see what needs changing just by reading it.
Also, the data file that the application uses to save all of these settings
will be in Windows .ini file format, (a) because it's very easy to write the
code for Windows, and (b) it makes it very easy to distribute your own data
files by email or usenet (without even needing encoding). For instance,
part of the file may look like:
[Teams]
1=Benetton,Renault,775,1,2
2=Tyrrell,Yamaha,765,3,4
..
[CarColours]
1=33,135,255,135,8,255,141,5,135,56,36,5,5,5,5,5
2=33,160,160,8,0,160,160,160,160,84,36,160,135,135,160,160
..
With such a potentially short lifespan, the editor will of course be freeware,
and I expect to have something ready to distribute in a couple of weeks,
although this will not be a finished version. I've found some space on a WWW
site for it, and the URL will be posted here when it's ready.
Sure, I could have written all this to run under DOS, but when everyone will
soon be running Windows '95 or some other kind of GUI on their computer, what's
the point?
_________ ___________________________________________