OMSI 2 and TDR problem

Willkommen in der OMSI-WebDisk!
Als Gast kannst du nur Inhalte in deiner ausgewählten Sprache sehen. Registrierte Nutzer können die Sichtbarkeit anderer Sprachen in ihrem Kontrollzentrum aktivieren, weitere Infos hier.
Alle Themen sind in den Foren mit einer Sprachflagge gekennzeichnet: = Englisch [EN], = Deutsch [DE], = Französisch [FR]. Wenn du die angegebene Sprache nicht beherrschst, schreibe auf Englisch!
  • Hi,

    I played OMSI for many years on my old laptop. This year I bought a new laptop Dell Vostro 15 (3500).

    It has an Intel Core i5-1135G7 with integrated Intel Iris Xe G7, 8GB RAM.


    OMSI on it has great FPS, but sometimes it loads GPU on 100% which is a problem. OMSI freezes, and after few seconds screen goes black, graphics driver resets and OMSI crashes.

    In the logfile, there is an only error:

    109 11:26:21 - - Error: Direct3D-Device lost!


    I tried it on Berlin, Lemmental V3 Updated, it happens everywhere.

    I have been searching where could be a problem, I found, that OMSI is beeing shut down by timeout detection and recovery. So I set delay in registry to 10 seconds, 20 seconds and it didn't help. I tried to turn off this function, but OMSI freezes and laptop freezes too, so I have to do hard reset.


    I tried OMSI 2.2.032 and 2.3.004, with and withou 4GB patch, but in both, there is a same problem.

    I tried other games, like ETS2, some benchmark tests which loaded GPU on 100% but nothing freezed, TDR don't kill them.

    Do you have any idea how can I fix it?

    I will be happy for any advice or tip.

    Thanks in advance.

  • Yes no problem,

    here it is:


    I tried also -logall argument on OMSI.

    logfile -logall.txt

  • Yes, I tried it with 4GB patch and without it. Perfomance is better with 4GB patch, but the problem is still there.


    Today, I've done some testing and I was surprised.

    When I was using Citaro E2/E3 from Morpheus, I have problem with overloading GPU, OMSI freezed and TDR killed it after 10 seconds.

    This most often happens when switching the view to the cab, or when engaging gear (or after departure).


    I realized that the Citaro is using a dashboard from Urbino II, so I tried the Urbino and it worked really great. High FPS, no FPS drops and I drove the whole line with it.


    So I thought that it is probably caused by some big textures, maybe memory overflow or something similar.


    But when I looked on it at task manager (sorry, I have Windows in czech language, so I can't switch it to english), red arrows are pointing to graphs, when OMSI crashed.


    I talked to friend, who have a powerful PC and he has a problem with all Moprheus packs of Citaro with mirrors. When he looks at the mirrors, he has FPS drops. So I thought, that my graphics card has problem with mirrors too, so I set the realtime reflections to none and tried it again. But the same problem is still there.


    I was thinking where could the problem be and I came to the conclusion that Morpheus has something very demanding in his Citaros, which causes fps drops in mirrors and for me, crashing of the whole game.


    Does anyone have experience with this problem? Does anyone know more?

  • Same similar (without crash) problem with the ultimate jelcz citybus pack of kajot .

    My specific: | CPU: AMD Ryzen 5 5600X 3.7 Ghz | MOBO:

    MSI Tomahawk B450 Max | GPU: Nvidia GeForce RTX 3060 12GB | RAM:

    Crucial Ballistix 2x8 GB, DDR4, 3600 MHz, CL16 | Crucial MX500 1000 GB (omsi installed)

    forum.png