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 unfortunately can't use this at night, because after a while the game always fails to load tiles.




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

  • If not, try the "4bac3485". Otherwise use the "000000".

    This unfortunately didn't help with my problem.

    Here is the logfile from my last test with the 0000... one

    I had to cut it a little bit, because it exceded the 100.000 characters


    Interestingly, when I was in the free F4 camera view before spawning the bus I was able to fly over those tiles without any problems.


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

  • Is that happening just at night/in the evening? Your OMSI seems having problems creating the light map at some point. Have you tried the same situation at day or tried reinstalling DirectX? Or updating your graphics driver?


    If that's not helping, I don't know what to do left. Try some other things in the "Troubleshooting" area in the description of the mod (first page).

    (Edit: I mean this:)




    PS: For the sake of completeness: You installed the 4GB-Patch, didn't you? Think of reinstalling it after every (Steam-)update

  • It only happens in the night/evening, yes.

    I will try reinstalling DirectX and updating my graphics driver, as you say.


    4GB Patch should be installed, but I wil check


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

  • I updated my graphics driver, reinstalled directx and checked the 4GB Patch, so far the only difference is that this time I could drive a few tiles further, until it broke, and there are even more errors now.



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

  • Hmm.. I'm afraid that I am out of ideas.


    Somehow the light map creation is making your Direct3D-Errors but i'm not "pro" enough to absolutely say why it happens.


    Maybe consider contacting the creators of the mod, as mentioned in the installation guide.

    I think in this case, they could help you the best. If they can solve your problem in any way, feel free to tell us how to fix it, because you're surely not the only one having these problems.




    PS: One last hope, have you edited the keyboard.cfg file as they wrote in the guide?

    The entry is intended so that the D3D-Driver does not cause any problems.

  • Sorry for not responding here for a while. I realised what the bug was several weeks ago, and wanted to update the guide with an explanation but got too busy.


    Its a similar behaviour to something else...


    Before you installed DXVK and were using OMSI 2 without the Windows 7 compatbility mode set, lets say you are in a area with high video memory load, e.g. detailed textures, and have been driving for a few hours. Then, when spawning a new bus, sometimes OMSI will crash with D3DERR_INVALIDCALL, even though you just spawned that same bus with no problems before.


    Nothing is wrong with the bus, but sometimes OMSI will do that after long periods without the Windows 7 compatbility mode set (and rarely, with it set sometimes). It's just OMSI. If you restart the game it will work just fine.


    The same thing is true here. After a while, OMSI won't be able to lock the lightmaps for a tile, which results in the entire tile failing to load. If you relaunch, however, the map will load fine. This never happened without DXVK - all I can say is, maybe DXVK "shifted" the issue over to lightmaps... it is a pretty experimental thing after all. Total stab in the dark, but my only guess is that


    I didn't put this in the guide in the first place because I didnt even realise it was a bug. I have been using DXVK and ReShade for several months, yet only experienced this bug twice on two different maps so far! For others it seems it happens a lot more often. I think it might depend on how powerful your system is, because mine is very powerful.


    What I do right now is just keep the Autosave ticked. This does cause OMSI to freeze while it autosaves, because the function that saves the file doesn't seem to be thread safe. It seems to depend on your drive latency. If you are on a HDD you'll notice it more, but for me on an SSD its fine.

    Then if it happens I just restart OMSI and load the map with "Load latest state of map" ticked. Its a very annoying workaround, but all I can suggest right now. Maybe in future DXVK versions the problem might be alleviated.



    PS: One last hope, have you edited the keyboard.cfg file as they wrote in the guide?

    The entry is intended so that the D3D-Driver does not cause any problems.


    Because of the above, sadly this has no effect. It's only intended for SweetFX users really. And it doesnt always fix black fog on textures.


    Same for DXVK state cache files. It will have no effect because the root cause a problem / behaviour with OMSI itself (even though it doesn't happen without DXVK)

  • Oh, that's really sad to hear. If that really is the only option I have at the moment I think I will have to uninstall DXVK for the time being, at least untiI upgrade my system. I like night driving way too much for this to be worth it I guess


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

  • Would be no problem for me, if i wouldn't have the problem of all of my passengers disappearing after reloading a save state.

    Sad to hear there's no workaround atm, perhaps it can be fixed someday.

  • It seems this is the mod of the year, if not mod of the decade... I came across it and tried it for some days and had NO issues. But still just using the basic configuration, meaningt just having put the two files into the OMSI folder. Performance has massivily increased, I did not see the counter going below 27 despite in some areas during loading.


    Also now it seems that high traffic settings (max cars, max people) have far less impact on performance that they used to have. But still pushing it up too much can cause the textures to blow up and have black or transparent cars, so there still will be limitations.


    Visuals:

    I had 4X or 8X MSAA and some supersampling for transparent textures (SGSSAA) set up in the Nvidia profile. As this is for DirectX this is no longer applied. How can I activate it for Vulkan? What I always tried was to prevent the street markings from flashing all the time. I don't need no ENB stuff etc, but this would be something I'd like to make better.

  • An explanation of why MSAA can not currently be used with DXVK is already present in the guide. You can activate it manually via dxvk.conf (search MSAA in the file) but it will break your rear view mirrors and other things unfortunately

  • An explanation of why MSAA can not currently be used with DXVK is already present in the guide. You can activate it manually via dxvk.conf (search MSAA in the file) but it will break your rear view mirrors and other things unfortunately

    Thx, I read about it today. Because of the rear view issue I will try other AA stuff, but I think I will have to live with the flickering. Is MSAA the real issue for that? What would happen if SSAA would be used combined with SSAA fpr transparencies? From my experience the flicker goes also away with SSAA as the main AA, the key is the transparency AA setting. I did not use SSAA because it was not that good, it made the whole screen a little bit to blurry for me. But maybe there would be a nice combination with SSAA+TSSAA which does not blow up the render pipeline like MSAA does. The GPU would still suffer boredom, like always in this game...

  • Hello, how can I confirm now my OMSI is using Vulkan or not?

    Is the only way I can be sure it's using Vulkan is to re-install Vulkan again?

    Kind of yes... you can follow the DXVK HUD section of the guide (modify dxvk.conf to enable the HUD) and if it shows in-game, DXVK is installed.

    Removing d3d9.dll from the OMSI directory will remove Vulkan from OMSI 2.

    Z5843Jl.png  kjq2JB9.png

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

  • Removed: I was complaining about tiles not loading at night, then I noticed that the issue was already elaborated few posts above.


    This post can be deleted.

    4 Mal editiert, zuletzt von mico ()