Race Sim Central
Rec.Autos.Simulators Archive

GPL: FD Instructions Please?

3 posts by 2 people · 15 Jun 2001 18:44 UTC - 15 Jun 2001 22:26 UTC

Ian 15 Jun 2001 18:44 UTC#178602
Hi: Could some kind soul please post the instructions to set up FD in GPL? I went to the VROC-F2 Yahoo Group and registered yesterday, but my membership is still pending so it won't let me download the file. I've got some free time this weekend and wanted to get into FD while watching Le Mans on Speedvision. Cheers, Ian
Ian wrote:
Quoted text (8 lines)> > Hi: > > Could some kind soul please post the instructions to set up FD in GPL? > I went to the VROC-F2 Yahoo Group and registered yesterday, but my > membership is still pending so it won't let me download the file. > I've got some free time this weekend and wanted to get into FD while > watching Le Mans on Speedvision.
Sure Ian, I just discovered the joys of FD this past week myself. Here we go, cut & paste job: DETAILED INSTRUCTIONS FOR CREATING GPL-FD CLASS =============================================== This is the process I've followed to create the FD (F1 chassis + F2 engine) car class in GPL with the GPL Engine Manager (GEM). This is almost certainly not the only way to do it, but this is what has worked for me, with virtually no problems at all. These instructions are specifically for creating the FD class, but the same basic approach could be used if you prefer the FG class. It looks pretty involved, but this process really isn't that hard at all. It really consists of: 1) Creating an FD player 2) Patching gpl.exe with GEM 3) Getting the engine sounds setup correctly =================== BEFORE YOU BEGIN... BACKUP YOUR EXISTING "gpl.exe" and "app.ini" files from your "\sierra\gpl" directory. Do it...do it now! =================== FILES REQUIRED ============== gpl.exe v1.0 (from your GPL CD) GPL v1.2 Patch: http://www.theuspits.com/owheel/gpl/patches.html GPL Engine Manger v1.19 (GEM): http://www.egroups.com/files/vroc-f2/Utilities/EngineChanger.exe Nigel Pattison's Carsound Patch: http://www.theuspits.com/owheel/gpl/files/carsound.zip (allows multiple engine sounds in FD events) 1) CREATE AN FD PLAYER ====================== * Load GPL and click on "Player Info"; * Create a New Player. This player will be a GP-class player, but it's recommended you add something like "FD" to the player's name to avoid confusion. When you've done this, exit GPL; * In Windows Explorer, go to your "\sierra\gpl\players\(your new FD player)" directory. Open the "player.ini" file there, and make sure you have the player designated as a GP driver, by looking for this line in the [Driver Rating] section: driverRating = 3 * Copy whatever car setup files you may want to use into the "\sierra\gpl\players\(your new FD player)\setups\(various tracks)" directories. The setup files must use the F1 setup extension, such as "monza.fe1" for an F1 Ferrari. 2) PATCH GPL.EXE WITH GEM ========================= * Backup your existing "gpl.exe" and "app.ini" files (if you haven't already), both found in your "\sierra\gpl" directory. You'll want to use these files for stock F1, F2 or F3 races; * Download the GEM v1.19 utility into a temp directory; * Create a temp directory that you can do some patching in, such "\sierra\gpl\temp"; * Copy "gpl.exe" from your GPL CD into the "\sierra\gpl\temp" directory. This will be the gpl.exe v1.0 file; * Patch this gpl.exe v1.0 with the Papyrus GPL 1.2 patch. Make sure you point the 1.2 patch utility to the "\sierra\gpl\temp" directory where the gpl.exe v1.0 file is. You'll now have a freshly patched gpl.exe v1.2 file; * Go to the directory where you placed GEM, and double-click on the "GEM119.exe" icon; * A GEM window should pop up, titled "Specify EXE to Patch" and will ask you "Please enter path to GPL.EXE". Type in the path to the freshly patched gpl.exe v1.2 file; * A GEM window will pop up with this message: "Exe has not been patched with 'Carsound' patch. Sounds will be left unchanged." This just means you haven't applied the Carsound patch yet to the gpl.exe file. Click "OK". * The "GPL Engine Manager 1.1.9" main window should now pop up. Here's where you actually apply different engines to different chassis. * To set up an FD package for each marque's chassis: Click on the drop down box next to each marque; Select the "2.5l Race" engine for each marque (Brabham through Lotus); Click the "Patch GPL" button. GEM will use the path to the gpl.exe file you specified above. Click "Yes" on the "Confirm Patching" window that pops up; After a moment, a "GPL Patched" window pops up. Click "OK", then "Exit" on the GEM main window. Your gpl.exe v1.2 file is now patched to an FD version. 3) SETUP THE ENGINE SOUNDS ========================== I'd highly recommended applying the Carsound patch now, so you can hear multiple engine sounds in an FD event: * Extract the "carsound.exe" file from the "carsound.zip" file into the "\sierra\gpl\temp" directory. Double-click the "carsound.exe" file and the FD version of your "gpl.exe" file will be patched to let you use multiple engine sounds. The Carsound patch also requires that you have the following .wav file for each marque in your "\sierra\gpl\sounds" directory. You can use any engine sound files you like, but they must be named: bra.wav brm.wav cov.wav eag.wav fer.wav lot.wav mur.wav The sound files I use are available on the "Files/Car Sounds" page at the VROC-F2 eGroups site, here: http://groups.yahoo.com/group/vroc-f2/files/Car%20sounds/engine_sounds.zip * To make the engine files sound correct, the last thing you must do is edit the "sampleRPM" value in the "\sierra\gpl\app.ini" file. Otherwise, the engine pitch will probably sound too high or too low. * Open the "app.ini" file with Notepad and change "sampleRPM" to this value, which I've found works well for the FD cars: [ Engine ] sampleRPM = 4500.000000 * Save the file, and you're done! OTHER PATCHES ============= If there are other patches you'd like to add (e.g., Papyrus' "disco fix" patch, etc.) you can add them now. It would be a good idea to backup the patched FD versions of gpl.exe and app.ini before doing so. MANAGING THESE FILES FOR YOUR F2 AND FD RACING ============================================== Because you now have different versions of "gpl.exe" and "app.ini" for F2 and for FD classes, you need to have a copy of both files for each class. All I've done to manage this is create two directories, one called "F2_files" and another called "FD_files", and placed the appropriate versions of gpl.exe and app.ini in each directory. When I want to switch between classes I just copy the appropriate files into "\sierra\gpl", then select the appropriate driver from GPL's "Player Info" screen. Hope this helps, and let me know if there are any inaccuracies with these instructions, etc. Cheers, Dave [email hidden] http://www.geocities.com/dmackf2 December 18, 2000 -- Fester
Thanks, Fester. Maybe I'll see you online when I get it working. Cheers, Ian Uncle Fester <[email hidden]> wrote:
Quoted text (230 lines)> >Ian wrote: >> >> Hi: >> >> Could some kind soul please post the instructions to set up FD in GPL? >> I went to the VROC-F2 Yahoo Group and registered yesterday, but my >> membership is still pending so it won't let me download the file. >> I've got some free time this weekend and wanted to get into FD while >> watching Le Mans on Speedvision. > > > >Sure Ian, I just discovered the joys of FD this past week myself. Here >we go, cut & paste job: > >DETAILED INSTRUCTIONS FOR CREATING GPL-FD CLASS >=============================================== >This is the process I've followed to create the FD (F1 chassis + F2 >engine) car class >in GPL with the GPL Engine Manager (GEM). This is almost certainly not >the only way >to do it, but this is what has worked for me, with virtually no problems >at all. > >These instructions are specifically for creating the FD class, but the >same basic >approach could be used if you prefer the FG class. > >It looks pretty involved, but this process really isn't that hard at >all. It really >consists of: >1) Creating an FD player >2) Patching gpl.exe with GEM >3) Getting the engine sounds setup correctly > >=================== >BEFORE YOU BEGIN... > >BACKUP YOUR EXISTING "gpl.exe" and "app.ini" files from your >"\sierra\gpl" directory. >Do it...do it now! >=================== > > >FILES REQUIRED >============== >gpl.exe v1.0 (from your GPL CD) > >GPL v1.2 Patch: >http://www.theuspits.com/owheel/gpl/patches.html > >GPL Engine Manger v1.19 (GEM): >http://www.egroups.com/files/vroc-f2/Utilities/EngineChanger.exe > >Nigel Pattison's Carsound Patch: >http://www.theuspits.com/owheel/gpl/files/carsound.zip >(allows multiple engine sounds in FD events) > > > >1) CREATE AN FD PLAYER >====================== >* Load GPL and click on "Player Info"; > >* Create a New Player. This player will be a GP-class player, but it's >recommended >you add something like "FD" to the player's name to avoid confusion. >When you've done >this, exit GPL; > >* In Windows Explorer, go to your "\sierra\gpl\players\(your new FD >player)" >directory. Open the "player.ini" file there, and make sure you have the >player >designated as a GP driver, by looking for this line in the [Driver >Rating] section: > >driverRating = 3 > >* Copy whatever car setup files you may want to use into the >"\sierra\gpl\players\(your new FD player)\setups\(various tracks)" >directories. The >setup files must use the F1 setup extension, such as "monza.fe1" for an >F1 Ferrari. > > >2) PATCH GPL.EXE WITH GEM >========================= >* Backup your existing "gpl.exe" and "app.ini" files (if you haven't >already), both >found in your "\sierra\gpl" directory. You'll want to use these files >for stock F1, >F2 or F3 races; > >* Download the GEM v1.19 utility into a temp directory; > >* Create a temp directory that you can do some patching in, such >"\sierra\gpl\temp"; > >* Copy "gpl.exe" from your GPL CD into the "\sierra\gpl\temp" >directory. This will be >the gpl.exe v1.0 file; > >* Patch this gpl.exe v1.0 with the Papyrus GPL 1.2 patch. Make sure you >point the 1.2 >patch utility to the "\sierra\gpl\temp" directory where the gpl.exe v1.0 >file is. >You'll now have a freshly patched gpl.exe v1.2 file; > >* Go to the directory where you placed GEM, and double-click on the >"GEM119.exe" >icon; > >* A GEM window should pop up, titled "Specify EXE to Patch" and will ask >you "Please >enter path to GPL.EXE". Type in the path to the freshly patched gpl.exe >v1.2 file; > >* A GEM window will pop up with this message: > >"Exe has not been patched with 'Carsound' patch. >Sounds will be left unchanged." > >This just means you haven't applied the Carsound patch yet to the >gpl.exe file. Click >"OK". > >* The "GPL Engine Manager 1.1.9" main window should now pop up. Here's >where you >actually apply different engines to different chassis. > >* To set up an FD package for each marque's chassis: >Click on the drop down box next to each marque; >Select the "2.5l Race" engine for each marque (Brabham through Lotus); >Click the "Patch GPL" button. GEM will use the path to the gpl.exe file >you specified >above. Click "Yes" on the "Confirm Patching" window that pops up; >After a moment, a "GPL Patched" window pops up. Click "OK", then "Exit" >on the GEM >main window. > >Your gpl.exe v1.2 file is now patched to an FD version. > > >3) SETUP THE ENGINE SOUNDS >========================== >I'd highly recommended applying the Carsound patch now, so you can hear >multiple >engine sounds in an FD event: > >* Extract the "carsound.exe" file from the "carsound.zip" file into the >"\sierra\gpl\temp" directory. Double-click the "carsound.exe" file and >the FD version >of your "gpl.exe" file will be patched to let you use multiple engine >sounds. > >The Carsound patch also requires that you have the following .wav file >for each marque >in your "\sierra\gpl\sounds" directory. You can use any engine sound >files you like, >but they must be named: > >bra.wav >brm.wav >cov.wav >eag.wav >fer.wav >lot.wav >mur.wav > >The sound files I use are available on the "Files/Car Sounds" page at >the VROC-F2 >eGroups site, here: >http://groups.yahoo.com/group/vroc-f2/files/Car%20sounds/engine_sounds.zip > > >* To make the engine files sound correct, the last thing you must do is >edit the >"sampleRPM" value in the "\sierra\gpl\app.ini" file. Otherwise, the >engine pitch will >probably sound too high or too low. > >* Open the "app.ini" file with Notepad and change "sampleRPM" to this >value, which >I've found works well for the FD cars: > >[ Engine ] >sampleRPM = 4500.000000 > >* Save the file, and you're done! > > >OTHER PATCHES >============= >If there are other patches you'd like to add (e.g., Papyrus' "disco fix" >patch, etc.) >you can add them now. It would be a good idea to backup the patched FD >versions of >gpl.exe and app.ini before doing so. > > >MANAGING THESE FILES FOR YOUR F2 AND FD RACING >============================================== >Because you now have different versions of "gpl.exe" and "app.ini" for >F2 and for FD >classes, you need to have a copy of both files for each class. All I've >done to >manage this is create two directories, one called "F2_files" and another >called >"FD_files", and placed the appropriate versions of gpl.exe and app.ini >in each >directory. When I want to switch between classes I just copy the >appropriate files >into "\sierra\gpl", then select the appropriate driver from GPL's >"Player Info" >screen. > > >Hope this helps, and let me know if there are any inaccuracies with >these >instructions, etc. > >Cheers, > >Dave >[email hidden] >http://www.geocities.com/dmackf2 > >December 18, 2000

Sponsors

Affiliate Links

Sim Gaming Expo MOZA Racing Sim-Lab Fanatec TrakRacer Asetek Internet Privacy From NordVPN Dreamhost Capital One Credit Card Application Fanatical CDKeys Amazon Amazon UK Project Motor Racing iRacing Get your racing gloves, boots and more from Demon Tweeks. Enlist at Roberts Space Industries, developers of Star Citizen and Squadron 42


Back from the ashes since July, 2019. First created in 2001 with the merger of Legends Central (founded 1999) and simracing.dk.

A site by a sort of sim racer, for sim racers, about racing sims. News and information on both modern and historic sim racing software titles.

All products and licenses property of their respective owners.


Facebook Threads Bluesky Twitter Mastodon Instagram YouTube Tiktok Twitch Reddit Google News Apple News Subscribe via WordPress Flipboard eBay

Race Sim Central © 1999-2026 | Some links pay RSC a commission. Advertising does not equal endorsement.Cookie Policy