- iRacing.com Announces iRacing 2.013,048
- iRacing.com to create virtual McLaren MP4-12C GT39,282
- Scanning What’s in Store for iRacing with Tony Gardner7,399
- Dave Kaemmer Comes Clean on Dirt7,398
- The iRacing.com Protest System – May, 20126,710
- Improving the Sound of iRacing5,633
- iRacing 2.0 Debuts in 2011 Season 34,933
- Preview Shots of HPD ARX-01C, Ford GT & Suzuka4,891
- Two New Cars and Two New Tracks Coming to iRacing Soon4,799
- iRacing.com to Build Digital Honda for New Super GT Series4,521
- Towler, Wood Suspended from Upcoming iWCRR Events 66
- Coming Soon, the iRacing Driving School 41
- iRacing.com Announces iRacing 2.0 41
- iRacing.com Announces 2010 World Tour 40
- Q&A with NiCWS Winner and Pro Road Racing Champion Richard Towler 36
- Dave Kaemmer Comes Clean on Dirt 32
- The iRacing.com Protest System - May, 2012 30
- iRacer Profile: Sandeep Banerjee 27
- FW31 Envy 27
- iRacing Announces Added Features, Lower Prices 24
- iRacing.com2340
- NASCAR 1893
- Motorcycles 1844
- Formula Cars 1707
- WRC 1428
- IndyCar 1299
- Touring Cars 873
- Sports Cars 307
- Other Racing 356
ROWA: Goddess of Filenames
by Ray Bryden on December 21st, 2010
The world will not end on December 21, 2012. That momentous occasion will occur sometime the day before, on December 20, 2012. The story of this revelation begins with my breakfast, for when I was about to ingest my toasted English muffin, I noticed the image of a god-like figure in the toasted pattern of butter-infused crispy porosity. Though I marvelled at its comforting portrait, my stomach was even more curious about it, so I sent it down directly for its opinion. Immediately I was struck by its loud verbal proclamation: “ROOOOOWWWAAaaaa!” Thus, I concluded, I was possessed by the great goddess “ROWA.” I was taught to always trust my gut.
First among the things taught to me by ROWA – long may she be jam smeared – was proper order. ROWA hates entropy. As a result, I have taken to setting up a pattern for keeping my setups in order by using a naming convention which helps organize them very effectively. To accomplish this I have assigned each track a three-letter code (two for the track and one more for the layout). Adding the car to the name is optional, but is helpful if you are sharing setups and posting them online, as is the code which identifies the originator of the setup. There is also a one letter code which identifies the type of setup. Lastly there is a code which shows which version of the setup it is, as tweaking of the setups are common, and it is good to know which version is the newest.
So the ROWA filename format is defined thusly:
tt#_cc_f_iii_vXX.sto
Underscores are optional, but I’m old school and filenames with spaces still seem wrong to me. In any event, the “tt” is the track code, with the “#” depicting the specific layout, the “cc” is the car code, “f” represents the type of setup, and “vXX” depicts the version number. As an example, a new Silverstone (GP layout) qualifying setup for the Williams F1 created by me would be:
SSG_F1_Q_RHB_v01.sto
“SSG” = Silverstone / grand prix layout
“F1″ = Williams-Toyota FW 31 F1 car
“Q” = qualifying setup
“RHB” = my initials
“v01″ = my version of the setup. Tweaking the setup should be recorded somewhere, and the version code increased incrementally with each file save.
Using this format, it is easy to know exactly what each setup is for. You can try to resist the format, but considering the 10,000+ combinations of tracks, layouts, cars and setup types, you can either struggle with crazy long filenames or try to decipher some other dogma for keeping track of them. If you are vigilant, and ROWA looks kindly upon the vigilant, you can archive older versions of setups to another directory, to avoid unnecessary clutter in the setup folders. The bonus is you can and will use the same format for replays and even screenshots.
ROOOOWWWAAaaaa!
Now keep in mind that all setup files are only useful until December 20, 2012. According to ROWA, the world will end that day, and you should therefore relieve yourself of all worldly possessions beforehand. You can ship them directly to me and they will be offered as a sacrifice when the time is right.
ROOOOWWWWAAaaaaa! Excuse me – I must be hungry.




David Phillips
Chris Hall
Jameson Spies
Jason Lofing
Tim Terry
David Allen
Allen Krier
Chris Cunningham
Tim Doyle
David Roberts
Ben Rothberg
Dylan Sharman


Reed
December 22nd, 2010 at 1:45 pmPerfect Ray………nice way to do it and as recently discussed, personally I think having the track or track code first makes the most sense as this way all setups from all sources are in a common area and not scattered throughout the folder. I believe your track code sheet is worthy of printing!!
Reed
December 22nd, 2010 at 1:46 pmClicking on the pics results in a “Redirect Loop”, any chance we can get a link to those?
Ray Bryden
December 22nd, 2010 at 3:56 pmHi Reed – I posted the codes on the iRacing forum. I’ll see if there is a way to post the file here as well.
Merry Christmas!
Joe
December 22nd, 2010 at 6:40 pmNice post! I’m sure most people have their own way of naming setups, and mine are below…
@ [- ][ = ]
For example, say I use Rusty Greer’s setup for stafford from 2010-4 he posted in the forums. I name it as:
stafford @ 10.4 – race = Rusty Greer
If I come up with my own setup during 2010-4, I name as follows:
stafford @ 10.4 – race
Now my setups are organized by track, then build, then type, then source. I think that organizes it in the right order!
Joe
December 22nd, 2010 at 6:41 pmIm so glad my ‘brackets’ were stipped from my post (wonderful URL encoding)….
Reed
December 24th, 2010 at 1:25 pmThanks Ray, I’ll check the forums.