Hey you F1c mod users!

I almost missed this utility that Vince Klortho made. It's a brilliant piece of work. Basically he wrote a little gem that will edit all the various 3dconfig files. If/when you change video drivers, then you have to run the F1 3dconfig or the various 3dcondfig files that were built into some of the mods. The vidguide line especially had to match your F1 config file or the mod would incorrectly load up F1 cars. Vince's tool runs 3dconfig ONCE and then updates ALL the other config.ini files that the mods use. So now, instead of cutting and pasting all day after a driver upgrade or videocard change, you can easily get all your mods set to the same settings without opeing each file. THANKYOU VK! http://forum.racesimcentral.com/showthread.php?t=146573 dh

Great find Dave! I just updated the ATI drivers and had a hell of a time remembering how to make it work. I will get much use from this! "Dave Henrie" <[email hidden]> wrote in message news:[email hidden]... I almost missed this utility that Vince Klortho made. It's a brilliant piece of work. Basically he wrote a little gem that will edit all the various 3dconfig files. If/when you change video drivers, then you have to run the F1 3dconfig or the various 3dcondfig files that were built into some of the mods. The vidguide line especially had to match your F1 config file or the mod would incorrectly load up F1 cars. Vince's tool runs 3dconfig ONCE and then updates ALL the other config.ini files that the mods use. So now, instead of cutting and pasting all day after a driver upgrade or videocard change, you can easily get all your mods set to the same settings without opeing each file. THANKYOU VK! http://forum.racesimcentral.com/showthread.php?t=146573 dh

Ya great utility very much needed. That was always a PITA. I updated to 56.xx drivers a couple of weeks ago and got stuck in the loop of the mod always running 3dconfig then loading F1C. I ended up just cutting and pasting below the gridsize line from config.ini to the Mods' *.ini file which seems to work fine. I realize with this utility, or the cut and paste work around, this issue is solved but just for my own edification what was the proper procedure again? I thought you had to run one race in F1 and then restart the Mod but that didn't work. Rudeboy "Tiny Lund" <[email hidden]> wrote in message news:[email hidden]... > Great find Dave! I just updated the ATI drivers and had a hell of a time > remembering how to make it work. I will get much use from this! >

Quoted text (9 lines)

> I realize with this utility, or the cut and paste work around, this > issue is solved but just for my own edification what was the proper > procedure again? I thought you had to run one race in F1 and then > restart the Mod but that didn't work. > > > >

Every time you made a video change you would have to run the F1 3dconfig which would generate a new config.ini file. The 2nd half of any mod's .ini file would have to match the original. However, some of the newer mods have included thier own 3dconfig program which generates a new .ini file for the mod. Running this new util is just like running 3dconfig, only it then allows you to copy the results over to the rest of the mods, this avoids any cutting and pasting or having to run 3 or 4 other 3dconfig programs for the various mods. THE ONLY drawback to Vince's utility is that by using it you lock all the mods into the same video settings. Some mods, like PrototypeC might not run as well as the rest and may experience more video slowdown. This can be fixed of course just by editing the offending mods' .ini file, or running it's built in 3dconfig.(but remember only a few of the newer mods use their own 3dconfig.) dave henrie