Posts by jpnmtrmn93

The forum is in reduced operation. The Addon and Support forums remain open.
Please note that OMSI is no longer under development. Some of the developers are now working on a new simulator. Further information concerning the LOTUS-Simulator can be found here.

    Thanks for your reply. I tried all of that and still could not get it. But, what I did notice is it doesn't work because the rotation of the spline was not 0, 90, 180, or 270. From what I can see, the spline has to be pointed exactly in one of the cardinal directions. So, I set the spline to point 180 degrees, direct south (the tunnel needed to be pointed at heading 150 degrees S/SE), and it worked perfectly.

    Thanks for the help. Really appreciate it.

    Thank you for your reply.

    Here is the video. Unfortunately, it is from 2014, so it may be outdated.

    Also, raising the height does not work for me. I set the height of the terrain to 100 meters, and the tunnel is still blocked by the terrain.

    I set the first spline outside the tunnel to "Yes, no THs" and set the first tunnel spline to "Yes, both THs". This is what I get.

    I found a video on YouTube explaining how to make a tunnel spline through the terrain, but the video is in German (I don't speak German), I can't see everything that the person does, and if I try listening to what he says, it just does not work for me. I get these weird terrain spikes still.

    Anyone know of a solution for this?

    Found what could be the problem. When naming the traffic light sets, it looks like there is a forced standard you must follow.

    Here's how I was naming the traffic light sets:







    Instead, I changed the names to:







    I ran this through the Crossing Editor, saved, and attempted to load the crossing in the map editor. It worked without freezing. Problem solved.

    After looking through the files, I realized what I wrote above was not the problem. This is what it is, more likely. If you have a crossing .sco file, open it in a text editor and remove al [use_traffic_light] lines and the numbers underneath. These set the traffic light index (starting from 0) for the path immediately above. If a traffic light pattern is not defined, these get ignored. But if there is a pattern defined it will look for the index. The error occurs when an index is referenced but not defined.


    1. Which version of OMSI 1 or OMSI 2 is being used?

    OMSI 2

    (I'll answer this one first) 3. Which action leads to the problem? (Place a new bus / Driving on schedule / ...)

    Placing a crossing .sco edited either with Crossing Editor or in Notepad++

    2. How often does the problem occur and how? (Error message, but playable / Crash / Freeze / ...)

    Every time; editor camera freezes. I can escape from placing the crossing, but cannot do anything else but exit from the editor without saving to reload the map.

    4. Which content was used? (Map, busses, ...)

    Map Editor

    5. Which mods or plugins were used? (SweetFX, ...)


    6. Logfile in spoiler or attached

    Error occurs at timestamp #191

    7. System information (OS, RAM, CPU, ...)

    Windows 8.1, 64-bit

    AMD A8-6600K APU Processor w/ Radeon HD Graphics, 3.90 GHz

    8GB RAM

    2GB NVIDIA GeForce GT 720 Graphics card

    460W Power Supply


    I am not sure if this is the correct place for this question. Hopefully someone can direct me to there, or can pass this message along to the developers.

    Driving the Solaris, there was originally no force feedback from going over bumps in the road. After copying over a forcefeedback.osc file and a forcefeedback_constfile.txt file, the steering wheel started shaking as soon as the bus loaded onto the map.

    Will this be addressed in a future update?

    Thank you.

    I have another issue to report. I do not know if it is just me, but the front door on the ticket purchasing side takes a while to open.

    EDIT: It could have been because of a low battery (who would have thought we'd be talking about a low battery on a bus in OMSI!). At the end of a run, I put the bus in neutral, and just kept the gas pedal down to charge the battery to full. I'll have to see if that solved it. But it is a temporary fix.


    So far I have only driven the rigid bus from the depot to Altona Station. I like how it runs. Now I want to actually go into service. However, I run into an issue. When I start I have an empty destination sign, which is good.

    I set the destination signs by using the timetable number (or Umlaufnummer) and then start the route. The destination sign displays the destination. We're still good, ready to go.

    Now, I need to go pick up the passengers at the first stop. I pull up and the passengers walk to the front door. But! When I open the doors to let them on...

    Uh oh! The game doesn't recognize that I have a destination set. And the passengers turn away and wait for the next bus. This happens right when I open the door.

    I finally got past the Zoologischer Garten train station on the X10 without jumping all over the place. I'm good for now.

    Apparently you have to use the electrics button again to turn on the bus. I was wondering if someone could fix that.
    Benutzen Sie die Taste für die Elektrik. (Is that how you say it? I'm still learning.)