Blender Import/Export Add-on

Note: This is a translation of the Blender Import/Export Addon manual created by Merk.

1 Introduction

2 Installation

3 Settings

3.1 General

Can be found in User Preferences (tab "Add-ons", category "Import-Export", detail view of "Train Fever (.mdl)").

Blender add-on settings

3.2 Import

3.3 Export

Additionally the input field for file names supports a couple of options:

• empty: the file name will be generated automatically (name of the object selected + appropriate file extension) and the directory currently selected will be used as "res" directory.
• name.extension: the file name matches "name", the exporter searches for a "res" directory in PATH; if the directory is not found the directory currently selected will be used again.
  
  
  • extension = .mdl, .grp or .msh: The file extension matches "extension"
  • other: the file extension is generated automatically

The default values for file names are determined based on the following logic:

• Model: object Name
• Group: the part of the object name before the first period (if the name doesn't contain any periods the full object name will be used)
• Mesh: Name of the mesh, not the name of the mesh object!
• Material: material Name
• Texture: Name of the graphics without file Extension

4 Object structures in Blender

5 Materials and textures

If the texture slot is named according to the previously required scheme the type of texture will be selected automatically.

6 Plugins

6.1 Animations and events

Enables export of animations and events.

Animations:
This field is only available for meshes, groups and lods and serves to assign more than one animation to an object:
https://www.transportfever.net…3-Blender-animations-png/

Events:
This field is only availabe for groups and lods.
https://www.transportfever.net…36024-Blender-events-png/
The individual events are listed in this field. They consist of a name (can be chosen freely with regards to groups, same goes for lods basically but Train Fever will recognize and use only certain names) and a list containing an arbitrary amount of records. Each record in this list contains a choice box for a child object and a choice box which is used to specify the event or animation that will be executed for this child object. In case forward is not ticked then the animation/event will be executed in reverse. In the choice box for the child object the current object can be selected which will cause its animation to be executed during the event.

Example:
A group is created for a folding door (*) which contains both door parts. An animation is added to this group used to rotate it around the z-axis. The second door wing gets an additional animation which rotates it in the opposite direction. Now create an event to open the door, choose a name, e.g. "open_doors" and add two records in the corresponding list:
[*]child: door group; name: name of the animation of the Group
[*]child: 2nd door wing; name of the door Animation
(*) Note: The exact German expression for this type of door is "Drehfalttür". I'm not sure how to translate this. My favorite translation sites came up blank for this; Google translate (which I avoid usually) suggested "folding door" so I'll go with that for now. Check out the pictures on this German Wiki page to get an idea what this is about.

6.2 Transport Network Provider (Paths)

To be honest I'm not an expert on this matter but I think eis_os designed it in a quite intuitive manner. First of all a "Transport Network Provider" object needs to be created (3D view: "Add" -> "Create TF Object") the parent of which needs to be set to model object (properties window: "Object" -> "Relations" -> "Parent"). After that "Transport Networks Groups" can be added at will the parent of which has to be the Transport Network Provider. Once a Transport Network Group is selected it's possible to specify the vehicle types (persons, trucks, trams, and so on) which are eligible to use the paths in the group. This is done in the object tab of the properties window in the panel "Train Fever TransportNetwork" (rightmost item). Paths are constructed from Bezier curves (standard Blender object: "Add" -> "Curve" -> "Bezier", Parent: Transport Network Group). An additional panel is available for this one too which allows for additional settings:

• Track width: Width of path, only relevant for paths which designate the waiting area for persons and cargo items as far as I know)
• vehicleNodeGroupA/B: specifies for which terminal the start (A) or end (B) point of the path serves as a vehicleNode (position at which the center point of a vehicle stops; -1 = no terminal)
• personNodeGroupA/B: specifies for which terminal the start (A) or end (B) point of the path serves as a personNode (not sure about this one myself; -1 = no terminal)
• personEdgeGroup: specicifies for which terminal this path serves as a personEdge (area in which persons or cargo items wait; -1 = no terminal)

6.3 Custom Metadata Provider (meta data for models)

This plug-in inherits almost all functions which are related to the metadata record in the .mdl. In case it's deactivated most of the information in it will neither be imported nor exported.Initially the following settings are available:https://www.transportfever.net…ender-model-metadata-png/In general the fields have the same (or at least similar) names as the corresponding fields in the .mdl. In the section "Description" the contents of the fields Name and Description will automatically be enclosed in _([tt] and [tt]) during export to ensure correct translation of the content with the help of strings.lua. In addition values for ParticleEmitter, Engines and Capacities can be adjusted directly in this panel rendering the additional objects obsolete starting with version 0.4.9. Existing data can be merged into the new system simply by creating corresponding number of records ("+" button) in the related lists => the add-on automatically populates them with the corresponding data. These objects can also be deleted. Unfortunately the Carrier record has to be set again explicitly for all records as I was unable to determine it from the existing data.In case these options do not suffice and even more records are required then unmarking the check box "Hide custom entries". This will provide (wherever possible) additional sub items which can be used to create records with an individual name and content:https://www.transportfever.net…odel-custom-metadata-png/This example would generate the following lua code:

example_str = "test",
example_int = 7,
example_table = {
    example_bool = false,
    example_float = 2.35,
    example_array = {1, 2, 3},
},

6.4 Materials and MatConfigs

Probably only interesting for people who want to attribute several materials to a mesh in order to use it multiple times (e.g. for varying coatings of a vehicle). If you don't need it, simply ignore the settings. https://www.transportfever.net…7-Blender-matConfigs-png/Additional materials can be used with meshes only, therefore they're listed in that area only. Records can be created and deleted using the "+" and "-" buttons respectively on the right border. Records don't need to be created in a particular order but shouldn't share the same Slot Index. This specifies which material slot/sub mesh the selected materials should be added to. A small hint displays the material currently active in this slot. In the rightmost field any number of records can be created which offer a choice box in which all materials available are listed. It is recommended to tick the option "save this datablock even if it has no users" for all materials which are not used by an object to prevent a scenario wherethey're not saved in the .blend file.MatConfigs can be set for meshes, groups and lods. Here too records are created/deleted using the buttons on the right, order doesn't matter either but is retained during Export. The field name is mostly optional as it's used only in the choice box of the parent object (in the screenshot above it is the position which says "ice1_mw") but with regards to the export it can exist only once within the object. In the field next to it a material/MatConfig can be selected for each submesh/child object; the number of list records is related to the number of submeshes/child objects and cannot be edited individually. In case the number of list records doesn't match the number of required records due to certain actions (e.g. deleting a child object) the add-on displays a hint and offers an option to add or delete records.