I'd like to see things move away from the whole 'I changed the textures lets call this a new track' concept, because that leads to confusion. They could even throw in a new mas file if they wanted different textures or to add cones or barricades, and just order the scn file properly in order for them to override the default textures. Now, if someone wants to make a new event, they just add a new event folder to the Daytona Track folder. gdb file that would call the proper pieces and set up the proper format for the race listed. In each of those folders there would be a. These would corespond to different events held at the track. Now, in the Daytona folder, there would sub-folders. However, all the track pieces and textures should be contained in the DAYTONA.MAS and DAYTONAMAP.MAS files. As a subfolder we can then have different layouts and sponsored versions. When building a new track it is best to model the entire circuit, including all variants in the main folder. Regarding circuits, we would like new tracks to follow some conventions.Īs per ISI Mike D's recommendation the following format should be used. In turn we hope that this will translate to an increased number of mods which will now be executable from the main shortcut, thus increasing convenience for the player, and simultaneously reducing HDD consumption. To help reduce the need for this, new to rFactor are some extra features which enable more independence with current folder structures. If you do this, you are likely to consume significantly more HDD space. Note: Using a different circuits directory is not recommended in most circumstances. The config file allows the use of different directory structures. This file rarely needs to be changed when creating new mods, however it has been left possible for you to create own configuration files. The config.ini contains entries that define directories where particular files are stored for the executable file. Let's start with the configuration file (config.ini) located in your main rFactor directory. The above diagram shows rFactor from a text file dependancy point of view. To get started, we will take a look at rFactor from a hierarchical point of view. If you are new to modding, please take a few minutes to go through some general tips. At the same time we would like to provide experienced users with an understanding of additional features new to rFactor.

The main priority of this tutorial is to give those learning the modding scene the best possible start. This section illustrates the file structure and describes the uses of the differing file types used in rFactor.

This is an overview into how rFactor works.

How to create a mod for rfactor 2