series for trainer

buzard

I'm trying to make a series for the trainer using various skins and tracks. I'm having problems with one aspect. I want the cars to be the advanced trainers. I can't figure out where I would set this. I made several attempts with different lines in the .VEH file and a couple in the rfm. But I still seem to have to buy and manually update each car.
 
I'm not sure if it's that what you want, but simply try it out.
First make a Backup of the original file: ..\GameData\Vehicles\rTrainer\Trainer_Upgrades.ini.
Then extract the zipped file into the Folder ..\GameData\Vehicles\rTrainer.
 
Redapg has suggested one means of forcing the upgrades you want... In your case it is a quick means to the end.

ISI designed a system for this purpose that is a bit more elegant and can handle many more variable conditions such as per track upgrade changes... or perhaps you want a custom mix of upgrades.

Check out the notes from ISI in the following "TrackConfigsBase.ini" that you can find in the ISI "National Stock Car" vehicles folder.

Code:
// This file is used to specify that certain upgrade configurations must
// be used at certain tracks.  Any file named TrackConfig*.ini in the
// same directory as an upgrades.ini file will be concatenated to this
// list of configurations.  That may come in useful if a whole new set
// of tracks is introduced by somebody.
//
// Alternately, files dropped in specific track directories that are
// named VehicleConfig*.ini can be used and will override any entries
// in this file.  The format of the VehicleConfig*.ini file is slightly
// different, taking a <VehicleClassSetting> to match the vehicle, rather
// than a <TrackName> to match the track.  The VehicleClassSetting for
// a given vehicle can be found at the top of a relevant SVM file.
//
// Specifying a certain upgrade configuration in this file can be done
// one of two ways:
//
// "<TrackName>" = "<ClassPackage>"
//
// In this case, <TrackName> matches the TrackName given in any track GDB
// file, and <ClassPackage> matches one of the "UpgradeClass" entries in
// the upgrades.ini file.  In addition, <TrackName> may be the wildcard
// '*' which will be used as the default if no other matches are found.
//
// The second way is to specify specific upgrades in a list:
//
// "<TrackName>":
// Rear Spoiler=2
// Suspension=1
//  <etc.>
//
// <TrackName> is, again, either a TrackName from a track GDB file or the
// wildcard '*'.  This must be followed with a colon and then a list of
// newline-delimited upgrade type settings.  This list must end with one
// empty line before the next configuration is specified.
//
// As a final note, mismatches due to the client missing or altering one of
// these files should result in the explanation "X.HDV or Track Config" mismatch.

////////////////////// Oval Courses /////////////////////

"Alabama Superspeedway":
Track Configuration=1
Oval Direction=0

"Brianza Junior":
Track Configuration=2 // ??
Oval Direction=1

"Brianza Oval":
Track Configuration=1 // ??
Oval Direction=3

"Brianza Pirello":
Track Configuration=0 // ??
Oval Direction=2

"Concord International Speedway":
Track Configuration=0
Oval Direction=0

"Fort Worth Speedway":
Track Configuration=0
Oval Direction=0

"Jacksonville Superspeedway":
Track Configuration=1
Oval Direction=0

"Joesville Speedway":
Track Configuration=2
Oval Direction=0

"Orchard Lake Speedway":
Track Configuration=0
Oval Direction=0



////////////////////// Road Courses /////////////////////

"Barcelona GP":
Track Configuration=3
Oval Direction=0

"Brianza Florio":
Track Configuration=3 // ??
Oval Direction=0

"Brianza Full":
Track Configuration=3 // ??
Oval Direction=0

"Brianza Grand Prix":
Track Configuration=3
Oval Direction=0

"Concord Infield":
Track Configuration=3
Oval Direction=0

"Essington GP Circuit":
Track Configuration=3
Oval Direction=0

"EuroRing_GP":
Track Configuration=3
Oval Direction=0

"Fort Worth Road Course":
Track Configuration=3
Oval Direction=0

"Jiading Circuit":
Track Configuration=3
Oval Direction=0

"Lienz Altstadt":
Track Configuration=3
Oval Direction=0

"Lienz GP Short":
Track Configuration=3
Oval Direction=0

"Lienz GP":
Track Configuration=3
Oval Direction=0

"Lienz GP Long":
Track Configuration=3
Oval Direction=0

"Lienz 24 Hour GP":
Track Configuration=3
Oval Direction=0

"Lienz Rally Hillclimb":
Track Configuration=3
Oval Direction=0

"Mills Metropark Long":
Track Configuration=3
Oval Direction=0

"Mills Metropark Long Reverse":
Track Configuration=3
Oval Direction=0

"Mills Metropark Short":
Track Configuration=3
Oval Direction=0

"Montreal GP":
Track Configuration=3
Oval Direction=0

"Northamptonshire GP":
Track Configuration=3
Oval Direction=0

"Northamptonshire International":
Track Configuration=3
Oval Direction=0

"Northamptonshire National":
Track Configuration=3
Oval Direction=0

"Nuerburg GP":
Track Configuration=3
Oval Direction=0

"Nuerburg Sprint":
Track Configuration=3
Oval Direction=0

"Orchard Lake Road Course":
Track Configuration=3
Oval Direction=0

"Sardian Heights Long":
Track Configuration=3
Oval Direction=0

"Sardian Heights Short":
Track Configuration=3
Oval Direction=0

"Shuber Park":
Track Configuration=3
Oval Direction=0

"Toban Raceway Park Long":
Track Configuration=3
Oval Direction=0

"Toban Raceway Park Long Rev":
Track Configuration=3
Oval Direction=0

"Toban Raceway Park Short":
Track Configuration=3
Oval Direction=0

"Toban Raceway Park Short Rev":
Track Configuration=3
Oval Direction=0


// You can force track configuration for all other tracks by using wildcard '*'. For example;
//"*":
//Track Configuration=3
// Would force road course config at all other tracks that have not been specified above.
// Though it could still be overriden by using VehicleConfig*.ini in the track folder.
 
Thanks. I'm on the right track for several things now. After looking at you posts it made want to review a couple of things in the .VEH file. Bingo, the "AIUpgradeClass=" is the toggle.

All of the files I was using were identical, so I could not see what to change. I thought that line was telling the program where to look for upgrade info.

After a closer look, I finally located an advanced trainer, it seems only the first car of all the trainers that come with rfactor is an advanced class. Once I opened up the .veh for that car I could see what I was looking for. DOH!

Also since almost all of the add on single seat mods are one make one configuration, all the .veh files from other mods are identical for car configuration as well. I looked at several but obviously it did not help.

Of course the AIClassUpgrade will apply only to AI cars. I'll use the upgrade file redagp posted for testing out the cars and tracks the switch to the trackbase.ini file info from gringosan when things get finalized. I'll have to hack the trainer.rfm file for this so adding the trackconfigsbase.ini to the vehicles filder to handle the class toggles should be the best way to go.

Perfect info for what I wanted to do. Thanks again.
 

Back
Top