rFactor 2 developer Image Space Incorporated have revealed the epic Brabham BT44B will be joining the simulation and have taken the bold move of launching a series behind the scenes development blogs featuring detailed information invaluable to modders of the sim. ISI have created the development blog with the intention of brining modders some golden information on how to create high quality modded vehicles to rFactor 2. Written by ISI's Michael Borda, the intention of the blog is to take modders through the process of optimizing vehicle physics in rFactor 2 and will eventually be accompanied with "spreadsheet releases and more in-depth explanations along the process". This is a strong move by ISI to add some value back to the community who have long thought that one of rF2's strongest points (its detailed physics) is also one of its biggest entry barriers to new and experienced modding teams alike. rFactor 1 was the original godfather of modding content with seemingly daily releases of various sizes and quality. However since the release of rFactor 2 modding teams have been slow to pick the baton back up and many have moved onto other titles to display their creative talents. With a detailed tyre and physics model alongside a continual update of the title's core baseline, rFactor 2 does seem to have lost its way in recent years with regards to engaging new modding talent. This move by ISI must surely be seen as a huge positive for fans of the game and the genre in general if it allows more individuals a greater understanding of the complexities involved in creating content for this sim. The full development blog can be read below. This first installment will delve into a question that many people have. And that is, so how do I get my rF1 physics into rF2? From a basic standpoint, you don't need to do much at all, but you DO need to have some form of placeholder .TGM files. To do so, you need to look through the vehicles we have at the moment, and decide which is the most similar to the vehicle you're working on. Pay a visit to the Dev Corner of the rFactor.net website, you'll see a TGM archive (v0.8) which contains a (mostly) complete archive of ISI & donated .TGM files, if you feel like contributing to the project please feel free to submit them. Filenames It may help to know the filename structure that we employ when naming tyres. Looking at the somewhat recently released 2012 FISI, by opening the FISIR_Car.mas file, we can see a bunch of TGM's which go by something like '245-660-13x12 Medium 2012.tgm'. Normally we put an abbreviation of the brand up front, in this case it could be preceded by a P_ but I elected not to do so, in this particular case. The next thing you'll see is 245-660, if you're American, you might well be thinking, the heck is that? Generally, the first numbers represent the size of the tyre, in this case, in metric and, more specifically, millimeters. In this instance, the tread width is 245mm, with an overall diameter of 660mm. The following numbers 13x12 should hopefully be more obvious, the represent the rim size in inches, diameter, width. Following on, "Medium" is the compound name, sometimes we'll write "Slick" (if there's only one dry compound) or "S8" or whatever, as the compound. Finally, we include the tyres intended production year "2012" which helps us keep track of the evolution of the tyre. Although, it can sometimes get confusing, we prefer to follow brand naming conventions for tyre sizes. Different brands may use imperial, or different ordering of sizes (diameter first as opposed to width first). Racing tyres usually list tread width and overall diameter but street tyres are usually defined by their section width and the ratio of the height of the sidewall to that section width. Older tyres often went just by their section width and rim diameter, and so naming used to be even more confusing. Let's look at another tyre. The rabbit out of my hat points to the Dissenter tyre, G_27.0x11.0-15x9.5_Slicks_1974.tgm. G is a random brand association (I'll let you guess the implication here). 27.0x11.0 is the size code, as used by that brand. 15x9.5 the rim size. "Slicks", the tread pattern or compound. "1974", the year of the tyre. If you happen to look up 27.0x11.0 on your favorite search engine, you might tend to find the correct tyre (of which this is a representation of). 27 is the diameter in inches, while 11 is the tread width, also in inches. This is the primary reason to stick with brand naming structure, even if it might be confusing to some, it tends to remove all doubt of which tyre it's actually supposed to be. If in doubt, typically the last 2 numbers before the compound/tread name will be the rim size in diameter and width. The prior numbers should hopefully be obvious enough, but you may have to apply some logic as some brands measure in millimeters, others in centimeters, and others yet, use inches. Back to it, tyre choices So which tyres did I choose for the Brabham BT44B? With it being a cross-ply / bias-ply tyre that I'm looking for (racing radials were first introduced by Michelin in 1977), I went to the cross-ply folder in our (recently updated) TGM examples archive. There I found something I know to be an approximate match (construction wise) to a 1975 Formula tyre. A 10-20-13.tgm and A 13.0-24.5-13.tgm, these are a representation of an early 70's Can-Am type tyre and will do the job. A quick search revealed that the relevant Goodyear tyres of the time were sized at 9.2-20.0-13" for the front and 16.2-26.0-13" for the rear. So at this point, I need to adapt these tyres into a suitable place-holder. To do so, as a minimum, we need to set the size multipliers and then we'll see if our car works in-game. The tyre sizes are 10.0/20.0 for the front which compares to 9.2/20.0, so the radius is already OK, but the front tyres are slightly too wide. 9.2/10.0 gives us 0.92. A search for "SizeMultiplier" in the TGM file (which I have renamed to G_9.2-20.0-13x10_Slick.TGM) I simply replace the existing value with: SizeMultiplier=(0.92,1) This entry will be under the [REALTIME] section, and will adjust the overall tyre dimensions. The rear tyre has a larger size discrepancy. Comparing them, 16.2/13.0 for the tread widths and 26.0/24.5 for the diameter results in a SizeMultiplier=(1.246,1.062), actually a better result is to use: SizeMultiplier=(1.246,1.07) The reason for this is because the 24.5 is actually a bit smaller in radius than indicated (24.3"). Avon's website has quite a catalog of historic racing tyres for reference. For this reason, it is wise to try and get measurements from the manufacturer directly, or at least from their website when all else fails. Tyre sidewall numbers are not always precise but may act as a last resort. Before we can try the car in-game, and see if it behaves acceptably, we have to point the TBC file to the direction of the TGM files, so that rF2 knows what to look for. Under Front, we need to add a TGM= entry, it should look like this: Front: TGM="G_9.2-20.0-13x10_Slick.tgm" While the rear should contain: Rear: TGM="G_16.2-26.0-13x17_Slick.tgm" And that's it, we have a crude physics set working in rF2. Because the original physics were quality, they will remain mostly intact, and additional rF2 physics improvements will be made over the course of a few weeks, with each update having a corresponding blog post to show what has changed. A short list of future changes will look something like: Updating, replacing and removing all old parameters. A proper new dedicated tyre that utilizes the contact patch model and all the latest tyre parameters. New internal combustion engine model. Ultra-chassis conversion (which allows chassis flex). But before I stop, let's do something to make sure the steering range is reasonable. Under the [CONTROLS] section of the HDV file was an entry: SteeringFFBMult=2 This line is obsolete and irrelevant in rFactor 2, so can be safely replaced. To determine a reasonable figure for this, while driving around in the developer SDK version of rFactor 2, press the key combination CTRL+V, which will show the Force Feedback outputs from the game. To keep FFB clipping to a minimum and FFB strength to a maximum, you can enable / disable this FFB output as needed. I came up with a torque of about 7.3Nm. Without any references, I used a conservative value for TurnsLocktoLock of 1.8 (likely too high). The top of the controls section now looks like: [CONTROLS] NominalMaxSteeringTorque=7.3 TurnsLocktoLock=1.8 There is one more thing left to do with a high importance. We need to add another line ModelWheelsIncludeAllTireMass=1 in the [SUSPENSION] section of the .hdv. With this parameter active, rF2 considers the tyre mass as already contributed the .pm or .ini file, as was the case with rF1. The preferred location for this line is just under "PhysicalModelFile=". The top of this section now looks like: [SUSPENSION] PhysicalModelFile=BT44.pm ModelWheelsIncludeAllTireMass=1 A quick test at this point has shown the car handles reasonably well in-game, so this will wrap things up for now. If you are trying a similar project and have strange grip issues, or whatnot, the likely cause is that your tyre radii between TGM and TBC don't match. We will coincide future updates to the Brabham BT44B with new blog posts outlining the processes and changes, along with some of the tools that enable creation and analysis of certain things (like tyres). This will be done roughly in weekly installments and is likely to get more technical as we proceed. Check out our awesome rFactor 2 Racing Club right here on RaceDepartment and have a look at the wide selection of excellent cars, tracks, skins and apps developed by the community and available to download now! Do you think the new ISI development blog could encourage you to enter the world of modding? Already a modder? Do you think this could help? Could this be the start of a revival in the rFactor 2 modding scene? Lets discuss!