1. Location of the file
The log file is located in the main directory and has the file name logfile.txt.
2. Content of the file
The header of the file starts with a current timestamp followed by the version of OMSI:
The log entries follow the following pattern:
- Sequential number
- Timestamp
- Type
- Message
The following types are available:
- Information: message that something has been loaded or notice of what OMSI is doing. Essentially, these messages can be ignored because they usually have no practical relevance for debugging. Example: Starting and closing OMSI
- Warning: Errors that are not so serious that they disturb the game flow or crash the game, but are logged anyway. Example: Texture not found
- Error: Serious errors that disrupt the course of the game or cause the game to crash. Example: Faulty script
In the appendix you will find an example log file.
3. Embedding a log file in the forum
3.1. Directly in the post
After OMSI has been closed, open the log file and load it in your favourite text editor (we recommend Notepad++ ). Use CTRL+A to select the entire text and CTRL+C to copy it to the clipboard. This selects the complete log file. The copied text then finds its way into a new post via the </>code button:
After clicking on this button in the editor, the logfile is then copied into the source code section, the result now looks like this (the above text is to be understood as an example):
Further measures such as packing in a spoiler are not necessary! The code block automatically provides a reduced preview that can be expanded:
3.2. As file attachment
Alternatively, the log file can also be attached as an attachment if it is particularly long. This can be done under the post in the tab "File attachments & images". After uploading, the log file will be presented as an attachment as follows:
The result when sending the post will look like this:
4. Frequent warnings
4.1. Did not find texture file ...
A texture was not found. These messages can usually be ignored and follow from a faulty or missing texture in the mesh file (o3d etc.). Such warnings are also often found in the OMSI standard content (cf. Appendix, entry 40ff. and 67).
4.2. File ... texture filename ... not found in mesh file ...
A material with a given texture is defined, but it is missing in the mesh or the given index in the [matl] entry is wrong.
4.3. Problem while getting file http://... (information)
An internet texture was not found.
4.4. bus stop ... found no exiting path
4.5. Direct3D-Device lost / resetted
Until today, the origin of this message is unclear. It is assumed that this problem is caused by faulty textures or drivers [3].
5. Common errors
5.1. The file ... could not be loaded
A required file (e.g. declared script, font file etc.) could not be found.
5.2. In ... there was an error in line ...
This usually indicates a syntax error in the file. However, the error does not necessarily have to be found at the specified position.
5.3. Help for Scripts
- Count that for every {if} there is also an {endif}.
- Count that for each {frame}, {init}, {frame_ai}, {macro:...}, {trigger:...}, there is also an {end}.
- Each opening parenthesis should have a corresponding closing parenthesis.
6. Further
With the command -logall, further info messages and warnings are output. However, the log file can become very large. For more information, see Start Parameters.
