En Français (Merci a @boingtheboeing pour la traduction)

A plugin supporting blender 2.79-3.x for importing and exporting OMSI .sco, .cfg, and .o3d files.

Blender-O3D-IO includes a fast o3d file importer and exporter with full support for the format. For complex models, .cfg and .sco files can also be imported and exported. OMSI map tiles (.map files) can also be imported.

• Fully supports O3D file format:
  • Explicit vertex normals
  • Long headers (version >= 3)
  • Encryption (requires private o3d_crypto.py module)
  • Long triangle indices
  • Alternative encryption seed
  • Embedded materials
  • Bones
  • UV coordinates
• Supports many features in CFG/SCO files:
  • LODs
  • Imports and exports advanced material features including:
    • [matl]
    • [matl_alpha]
    • [matl_transmap]
    • [matl_envmap] & [matl_envmap_mask]
    • [matl_bumpmap] (Blender >= 2.80 only!)
    • [matl_nightmap] & [matl_lightmap]
    • ...
  • Interior lights and spotlights
  • Lens flares ([light_enh] and [light_enh_2])
  • Imports all referenced models (o3d files only) and textures in the CFG/SCO as separate objects
  • Imports .x if a compatible importer is installed (https://github.com/Poikilos/io_import_x)
• Imports OMSI map tiles (.map files): [WIP]
  • Imports referenced scenery objects
  • Imports terrain tiles and materials
  • Imports splines and converts them to meshes

1. Go to the releases page and download the latest release (available here), it should look like Blender-O3D-IO-Public-0.2.3.zip
2. Open Blender go to Edit->Preferences...
3. Go to the Add-ons tab and then press Install...
4. Select the zip file (do NOT unzip it) and press Install Add-on
5. You should now be able to import o3d/cfg/sco files from File->Import->OMSI Model Config (*.cfg, *.sco, *.o3d)
6. Map tiles can be imported from File->Import->OMSI Map Tile (*.map)
7. You can export o3d/cfg/sco files from File->Export->OMSI Model Config (*.cfg, *.sco, *.o3d)

OMSI and Blender handle 3D models and materials fairly differently so there are a few areas where the conversion between Blender and OMSI is a bit imprecise, this is most notable when exporting as there are a few assumptions the exporter needs to make to export files correctly. The exporter is designed to try as closely as possible to export an imported cfg file identically to the original. As such, the best way to learn the specifics of the exporter is to try importing some files, and examine how the importer sets them up in Blender.

The exporter decides what to export based on the file extension of the exported file. To export a cfg along with all its required o3d files, specify the .cfg file extension when exporting. When exporting a single mesh as an o3d, a single o3d file is produced; if on the other hand you're exporting multiple Blender objects as an o3d then the exporter automatically creates separate o3d files for each Blender object, this behaviour can't be changed.

For instance if the scene contains the following objects:

Scene Collection
| > Body
| > Wheel_H
| > Wheel_VL
| > Wheel_VR

If we enable the "Export selection" option in the export dialog, then we can control which objects are exported. With only the Body selected, if we export as Body.o3d we indeed end up with a single o3d file Body.o3d. If on the other hand we select all the objects and export as Car.o3d the exporter will automatically export separate files for each object:

Car-Body.o3d
Car-Wheel_H.o3d
Car-Wheel_VL.o3d
Car-Wheel_VR.o3d

If we export as Car.cfg then the behaviour is the same, except the o3d files are not prefixed with the file name and a cfg file is also generated:

Car.cfg
Body.o3d
Wheel_H.o3d
Wheel_VL.o3d
Wheel_VR.o3d

Blender uses a completely different shading system to OMSI so there are some limitations to consider when exporting materials:

• Some material features require a cfg file to exported to work correctly (transparency, envmaps, lightmaps, etc...)
• If textures aren't displaying in OMSI check the following:
  • Blender supports image formats that OMSI doesn't, if possible use dds files for textures, these are best optimised for OMSI and will generally load faster. (OMSI only supports DXT compression in DDS files)
  • Make sure the texture file exists in the correct textures directory in OMSI, the exporter converts all texture filepaths to relative paths, so the texture must be in the correct place relative to the o3d/cfg file for omsi to find it.
• Only the following material fields are exported:
  • Base Color/Diffuse Color
  • Alpha
  • Specular Color/Specular Intensity
  • Roughness/Specular Hardness (when the roughness is set below 0.1, the envmap is automatically enabled)
  • Emission Color
  • Base Color Texture
  • Alpha Texture
  • Specu