Version 3.1p 3DSimED and later can import models from F1 2018. The plugin for F1-2018 can be found at  3DSimED3 download page.

To import F1 2018 models F1-2018 (*.erp) must be selected as the import file type.

Importing Cars. To import a car you must browse to your F1 2018 game and look for the f1_2018_vehicle_package folder within the asset_groups folder. Inside the f1_2018_vehicle_package folder there is the teams folder with all the cars, select the car, and then the wep folder. The wep folder should have the car’s erp file to select and import.
Note: to import a classic car browse the f1_classic_02_vehicle_package folder.

At present the format for some of the higher resolution bitmaps (mipmap files)  is not understood so the quality will not be the same as in the game.

Importing Tracks. Within the game’s asset_groups folder find the environment_package folder and then the tracks folder. Select the track and find the wep folder. For each track there are two erp to select from, one named <track_name>_2018.erp and the other named <track_name>_classic.erp, select one of those and the track should be imported.

As for the cars, the mipmaps files are not completely understood so textures will not be the same quality as in the game.

• Forza 7 and Forza Apex tracks can only be imported with version 3.1n or later.

• The .zip archives for the tracks need to be unzipped. Note that for the Forza 7 .zip files, the run-time encryption needs removing.

• The  .zips can be decompressed with quickbms_4gb_files.exe (some files > 2GB) , but to avoid file collision each track needs to be in a separate folder.

• The -D argument should be used with quickbms_4gb_files.exe to ensure each track has its own folder or use a powershell script as explained in Working with Forza Apex car models.

• Only the archives in the sub-folders of the tracks folder need to processed.

• To import a track you need to browse and find the track .pvs files. There seems to be little difference between the low, med,  high, wet, & night versions.

• When a pvs has been selected the Track Import Options dialog will be presented.

• The Quick Convert Swatch to DDS will convert .Swatchbin files to .dds on the fly and place them in a temporary folder. This should not slow the import as the Swatchbin format is very similar to DDS.

• Most of the DDS will be Directx10 format and because they are not native Directx9 format cannot be stored in ram as compressed data, so they are very memory hungry.

• Most of the swatchbin have associated higher resolution versions which can be converted to DDS but these can require so much memory that the track will not be imported correctly so care should be taken with both the higher and all level options.

• For some reason every track seems to have a few missing texture maps. A solid color texture map replacement will be created with the Replace missing texture map with color map option ticked.

• The Import Sky Objects option will ensure sky objects are imported but these seem to have little use and merely make editing more difficult.

Studio 397 have made some great improvements to rF2 particularly by adding DX11 rendering. A number of new  & updated shaders to take advantage of DX11 features have been included, and as a result 3DSimED has been extended to support these enhancements.

3DSimED 3.1m includes the new shaders from rF2 v1109 in the Select DirectX Shader window. This allows materials to be assigned these shaders and saved when exported to one of the .GMT format 3DSimED supports. If the game does not include the material shader then it will just use a default shader (which appears to be the simple diffuse texture map).

One of the filters for the shaders in the Select window is ‘rF2 DX11’ which are for shaders included in rF2 DX11 but not in the DX9 version. 3DSimED can include these shaders in the models, and can export them in the .GMT materials, but cannot render them correctly because of the DX11 features used, so it just renders them with a simple diffuse texture.

3DSiimED now includes 3 ‘Decal’ shaders included to make it easier to work with some models from other games. The Download Page includes a .zip of files required to ensure rF2 can understand and render these shaders, just ensure these are placed in the same folder as the CoreShaders.mas.