DXVK (DirectX-over-Vulkan) - stability improvements & potential performance boost: installation guide & details

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!

    I had some issues last time I played OMSI on Hamburg HafenCity with the E-Bus: in the depot Alsterdorf I had to force thne graphic engine with the hotkey to reload almost every 30 seconds. The screen freezed but OMSI was still some kind of running in the background and responded to key pressings etc. The reset with the hotkey helped until I was out there, but I'm wondering what happens here and what is causing this. Once it also happend that OMSI stopped to respond to key pressings, but still could press keys on the dashboard with the mouse.


    Loading problem with a tile also happend once. First I saw an intersection completly lighted at night and the bus was very dark in the outside view. Some 200-300m laters the following tile did not load. this was at early morning when it was still dark. After reloading the situation everything was fine again.


    I wonder what the additional cache files are ment for. Should the one were the folder is called "recommanded" be used?


    Ì also wonder why it is recommanded to set the amount of cache for textures to 0 MB in the OMSI options. I was used to have values at around the half of my VRAM there, and first did not know that it is recommanded to change that value for the use with DXVK. Now I changed it to 0 but do not really see differences.


    OMSI video freezing but audio / simulation continuing is a rare bug with OMSI, I've had it happen sometimes but DXVK shouldn't and hasn't made the issue occur more often, atleast for me. Usually when this bug happens, resetting the graphics device is only a temporary aid, and you should fully restart the game instead - hopefully the issue should not return.


    As for OMSI permanantly losing keyboard focus, same story as above.


    With the tile loading problem, just curious, you set the compatibility mode for Omsi.exe to Windows 7 right?


    The cache files don't really have that major of an effect on OMSI, however it can help with stutter on certain configurations, you could try using the recommended cache (the guide should specify which cache files to use and when). They won't solve the tile bug though.


    Setting the video memory limit for textures in OMSI 2's options to 0.0 (not just 0 - make sure it's 0.0) removes the limit entirely. Since OMSI is way more CPU bound than GPU bound, you shouldn't notice a major difference, however it heavily reduces the chance of other issues such as white/black textures occuring.

    Z5843Jl.png  kjq2JB9.png

    i7 5820K @ 4.1GHz • Zotac GTX 980Ti AMP! 2-way SLI • Full PC Specs

    Zitat von sjain

    With the tile loading problem, just curious, you set the compatibility mode for Omsi.exe to Windows 7 right?

    Uunfortunetly I can't tell it, because during the last months it was set to Windows 8 compatibility, yesterday I have changed it to Win 7 along with setting texture cache to 0.0 and also setting Compatibility to Windows 7 for Steam Overlay like described in the guide, which also has not been set before. So I think now I must investigate it for some time, as I think short tests do not really tell me if everything is now set up well to my configuration. Same with cache files: today I will try without, next time with the recommanded one...

    I've found a way to reduce tile loading problem:

    1 install 4gb patch

    2 open OMSI settings, go to graphics (advanced)

    3 set the Max. Tex. Mem. for high-res tex load to about 3096.0

    this don't fix the problem, just mitigate it but at least i was able to drive for about 8 kilometers at night.


    noticed that this issue is related to lightmap streaming, and is negatively impactated with dds textures.

    maybe a future update of DXVK can fix this issue.

    Thanks for sharing your help. The guide instructions already have the 4GB patch in an FAQ but not the global install instructions, I'll add that. Should be noted (since i shared my experiences above) that I always use the 4GB patch.


    For point 3 the global install instructions already tell users to set the limit to 0.0, which disables the limit, but I was wondering if you experience different results to this compared to 3096.0? And, what graphics card are you using.


    That being said I've never seen OMSI's video memory usage go over 1GB even in the heaviest conditions, still possible it could be contributing though.


    As for negatively impacted by dds textures, do you mean it makes the issue worse/more common or improves it/makes it occur less often?

    Z5843Jl.png  kjq2JB9.png

    i7 5820K @ 4.1GHz • Zotac GTX 980Ti AMP! 2-way SLI • Full PC Specs

    I use an ASUS r7 260x with 2GB and Radeon PRO driver 21.Q1.2, when i set the limit to 0.0 i can drive on 2 or 3 tiles and OMSI stops loading more tiles.

    I've tested with 1500.0, 2048.00, 2500.00 and 3096.0, and every time i've increased this value, the game loaded more tiles.


    When the objects use DDS textures the memory usage of dxvk is increased, as it needs to decode the format and convert it to bitmap, making the loading bug happen earlier.

    Using the F4 camera is easier to see white textures being processed: the mesh is loaded but texture takes some time to be rendered.


    Maybe using more than 3GB can cause problems as OMSI is a 32 bit software, but i did not test, don't know if it will work.

    Thanks for sharing your findings. Sounds conclusive and good, what's odd for me though is, with 0.0 limit, there are several times (even recently on RTX 3060M) where I never had tiles stop loading in evenings or the night, even on 30-45minute long routes on Addon London, ALU, etc. with heavy buses too!


    But other times OMSI simply isn't having any of it and just will not load even a single tile after the spawn, even after several relaunches, and even on lightweight maps and buses. It seems to be spontaneous for me whether it occurs or not (and seems to be rarer than for most others). I'll test out your method!

    Unfortunately I am experiencing a new kind of issue after reinstalling DXVK this time.

    The ALT HUD menu for spawning buses selecting timetables, etc... does not appear anymore. It only appears for a second when I pause the game via ESC and then return to the game or when the "Change to this vehicle" dialog is open and when I leave the game via the Windows Key it becomes visible, too.

    When I click on the spot where the little expand button for that menu would be, it shortly opens, while the screen turns black and the immediatly dissapears again.

    The menu seems to exist but just be invisble though, as the buttons of it remain clickable.

    Any Ideas?


    "The head is for thinking and not just for carrying your brain" - Bohdan Leskiv

    Zitat von Roadmaster '93

    Unfortunately I am experiencing a new kind of issue after reinstalling DXVK this time.

    The ALT HUD menu for spawning buses selecting timetables, etc... does not appear anymore. It only appears for a second when I pause the game via ESC and then return to the game or when the "Change to this vehicle" dialog is open and when I leave the game via the Windows Key it becomes visible, too.

    When I click on the spot where the little expand button for that menu would be, it shortly opens, while the screen turns black and the immediatly dissapears again.

    The menu seems to exist but just be invisble though, as the buttons of it remain clickable.

    Any Ideas?

    Once the map has loaded, click on the main game screen then press ALT on your keyboard 3-4 times (or maybe 6 times) to open and close the ALT menu, as per the instructions. This is the only workaround I know of this issue. It happens to me too. You will need to do this everytime you load a map

    Z5843Jl.png  kjq2JB9.png

    i7 5820K @ 4.1GHz • Zotac GTX 980Ti AMP! 2-way SLI • Full PC Specs

    Doesn't seem to be of any help

    Actually, now no keys are working anymore


    "The head is for thinking and not just for carrying your brain" - Bohdan Leskiv

    Einmal editiert, zuletzt von Roadmaster '93 () aus folgendem Grund: Ein Beitrag von Roadmaster '93 mit diesem Beitrag zusammengefügt.

    Neuerdings tritt unter DXVK das Phänomen auf, dass sich das Spiel selber nach dem Laden der Map auf den Sekundärmonitor verabschiedet, nur das Menü-HUD blendet sich aufm dem Primärmonitor ein. Ohne DXVK tritt dies nicht auf.

    Hat jemand ähnliche Erfahrungen gemacht oder weiß wie ich OMSI zu einem bestimmten Monitor "zwingen" kann?


    // ENG:


    Recently, I got the phenomenon under DXVK that the game itself goes to the secondary monitor after loading the map, only the menu HUD appears on the primary monitor. Without DXVK, this does not occur. Has anyone had similar experiences or knows how to "force" OMSI to a particular monitor?

    NVIDIA anti-aliasing doesn't work with Vulkan.

    And I opened anti-aliasing in DXVK settings, but it also doesn't work.

    Zitat von sjain
    Zitat von hans-johnson

    NVIDIA anti-aliasing doesn't work with Vulkan.

    And I opened anti-aliasing in DXVK settings, but it also doesn't work.

    Please read the Steam guide for details regarding anti aliasing. Everything has been described there.

    I have tried to use Vulkan with SweetFX, but it never works.

    I tried right now, to open the FXAA, and I think it failed.

    Before I used Vulkan, I could use anti-aliasing with NVIDIA, but now it also doesn't work.

    Zitat von sjain
    Zitat von hans-johnson

    NVIDIA anti-aliasing doesn't work with Vulkan.

    And I opened anti-aliasing in DXVK settings, but it also doesn't work.

    Please read the Steam guide for details regarding anti aliasing. Everything has been described there.

    I re-install the Vulkan without ENB or SweetFX effects, it's fine.

    But when I install the 1.9.4 from below, it doesn't work again.

    OMSI With Vulkan - OMSI - WebDisk & Community

    I face an odd problem. When I have set OMSI to launch in Windows 7 compatibility mode, I do not have any sound whatsoever in-game. Is there any solution to this problem? Because when I disable compatibility mode, OMSI crashes as soon as it loads the map.

    After some testing i've found a way to fix the load issue:

    set "Load Whole Map at Start" on OMSI config.

    This will fix this issue (DXVK 2.3) as the full refresh will be made on the start, but there are some drawbacks:

    Loading times will be very long, and your performance would be slightly reduced.

    For the best results you need the 4GB path, a very strong CPU (tested with a Ryzen 7 7700) and a fast SSD.

    Some big maps may not load due to memory limits of a 32bit software.