Vulkan API – Feedback, Known Issues, and FAQ

Hi Car Killer, I just finished to verify the file integrity on the BeamNG launcher and Steam.
-The BeamNG launcher integrity check finishes with the message "No problems found".
-Steam's "Verify integrity of game files" option finishes with the message "All 9661 files successfully validated"

Now, when I run the game with the Vulkan renderer, and turn on the depth of field option, the game still crashes with the error code 0x00000001.
It does not seems like any of my game files have been modified...
However, there is still the same error at the line 648 of the crash log (the one attached to this message).
It seems like there is a problem with the compilation of the '/shaders/common/postFx/dof/DOF_Final_P.hlsl' shader.
I do not know if this will help, but I attached the file located on my computer at the address:
E:\SteamLibrary\steamapps\common\BeamNG.drive\shaders\common\postFx\dof\DOF_Final_P.hlsl
This file is maybe the origin of the problem.

Anyway, if you have any other instructions, please let me know.

 

Interesting that this is the exact same crash I get on the native Linux build. I will have to try out disabling depth of field.

 

The issue you’ve noticed:
(Game does not launch/show up on screen or on the taskbar but show itself running on task manager, see video and screenshot.)

This happens when:
(When try to launch BeamNG with Vulkan.)

My specs are
Windows 10 22H2, AMD Ryzen 5 5600H with Radeon Graphics 3.30 GHz, NVIDIA GeForce GTX 1650, 24.0 GB (19.9 GB usable), Driver version 32.0.15.6070 or 560.70

 

So ive noticed after updating from 0.32.2 to 0.32.4 that my game is way way more prone to crash with the 0x0000001 error code thing that basically tells nothing much, it can either randomly freeze while driving around and crash (while also crashing my gpu drivers for some reason, which worked on 0.32.2 with no problemo) or whenever i interact with certain ui elements (options menu for example crashes the game)

 

Sorry I was asking for help to fix this not report it. stupid dyslexia. and how the heck do you get beamng.log file?

 

well uhh, vulkan refuses to launch at all with this error, see the window pop in for a split second then crash

--- Post updated ---
it seems to me like sometimes instead of improving for me vulkan gets worse, and this is the last straw for me now, game ran like 2x as fast and way smoother than dx on 0.32.0 and then in .4 it just decided to entirely die and crap its pants, shame

 

Hello! hope all is well and yall are having a great summer, I am unable to open Vulcan render after updating to 0.32 hotfix, normal mode beamng opens fine and has no issues, however vulcan crashes upon trying to launch, here are my system details and a few screenshots that may help
i have tried running Vulcan safe + debug version but that also crashes upon trying to launch
here is the crash details i copied from the 2 crash reports:
Vulcan:
BeamNG.drive 0.32.5.0 0x00000001
Vulcan Safe+Debug
BeamNG.drive 0.32.5.0 0xC0000005 STATUS_ACCESS_VIOLATION

from what i can tell on the threads the vulcan safe +debug's crash report is related to the game exceding its allocated budget, however im not sure why/how that could be the case given that before updating it worked fine and vulcan was performing really well and now it is not even launching

Many thanks -
Jocasta

My specs:

NVIDIA system information report created on: 08/06/2024 02:34:38
NVIDIA app version: 10.0.1.256
Operating system: Microsoft Windows 11 Home, Version 10.0.22631
DirectX runtime version: DirectX 12

Graphics Card
GPU processor: NVIDIA GeForce RTX 4090 Laptop GPU
Direct3D feature level: 12_1
CUDA cores: 9728
Graphics clock: 1815 MHz
Max-Q technologies: Gen-5
Dynamic Boost: Yes
WhisperMode: Yes
Maximum graphics power: 175 W
Resizable bar: No
Memory data rate: 18.00 Gbps
Memory interface: 256-bit
Memory bandwidth: 576.064 GB/s
Total available graphics memory: 32582 MB
Dedicated video memory: 16376 MB GDDR6
System video memory: 0 MB
Shared system memory: 16206 MB
Video BIOS version: 95.03.2b.00.35
IRQ: Not used
Bus: PCI Express x16 Gen4
Driver: Game Ready Driver - 552.12 - Apr 4, 2024
Display: 1920x1080,60Hz(External Monitor)
CPU: 13th Gen Intel(R) Core(TM) i9-13950HX
RAM: 32.0 GB
Storage (2): SSD - 953.9 GB,SSD - 953.9 GB

some screenshots/files that may be useful:

 

Just ran into a weird issue with Vulkan that has to do with fullscreen...

Steps to reproduce:
-Open BeamNG, and run in vulkan safe mode
-Once on the main menu, Alt + Enter for fullscreen
-Then press Alt + Enter again, and switch from one screen to extend with Win + P
-Switch back to just one screen, and then press Alt + Enter
-It fullscreens, but the window is offset, and only takes up a quarter of the screen

 

I'm getting this flikering of decal at night, only when using vulkan backend



nvidia 3060 rtx, driver 560.81

 

Does anyone know how the game switches between vulkan and dx11 and how I can replicate this with my launcher?

 

you can switch from the command line by adding -gfx vk for Vulkan, probably -gfx dx or dx11 for DirectX.

 

ah, thanks. I will need to rewrite the game launching code for my launcher, but this should hopefully work. thanks

 

Not sure if this is a Vulkan issue, but wanted to share it.

 

I have to say... Colour me impressed!!

I haven't had any issues with Vulkan in this new update, and I'm getting pretty substantial uplifts from it.
For example, in Italy, at the default crossroads spawn, with max traffic that I can get (12 cars + 12 pooled in memory + 5 parked, non simplified), I go from an average of ~90-100FPS (around 100-150 max depending on where I am) to ~120-130FPS average, with around 150~200FPS Max - All at max graphics (without dynamic reflections), wow!

Forgot to turn off my framerate limiter so averages may be a little strange - Will re-test with no fps cap when I get time

The lows jump down to about 40-60 on Vulkan but the same happens on DX11 as well, I'm blaming that on the fact I'm chucking everything possible on my system so it'll hitch here and there of course.

I have a Ryzen 7 7800X3D - 32GB 6000MHz CL36 (running at CL30) and an RTX 4070, for reference


I would love to ask, because I'm a bit of a massive nerd for this sort of stuff (not a dev, but I like hearing about the things that have been done) - What work was done to Vulkan to improve the performance of it from 0.32? I don't mind if it's indepth or not, I don't want to waste too much of your time.

 

It is now taking forever just to drag a slider to a certain value and apply a setting, it feels like the UI is slower now

 

Game is stuttering a lot in Vulkan, with FPS constantly bouncing up and down between 40-150fps, but often goes below 60fps (see attached video).

In regular Direct X 11 it's quite smooth, and FPS stays in the 50-90 fps range, but rarely dips under 60fps. I don't really experience any stuttering like with Vulkan.

This is on WCUSA without traffic.

Graphics settings is everything with drop-down menu is on max, while the rest is like this:


2560x1440, 144 MHz

NVIDIA GTX 3060Ti, AMD Ryzen 5800X, 16GB Ram

 

In Vulkan the game is still using about 2GB more VRAM making traffic impossibility while it's very smooth with VRAM to spare under DX. My GPU's 2070 Super with 8GB.
I could do VRAM/general Vulkan vs DX11 tests if I have time and motivation, I don't know...

 

I've noticed this for a while now. For me, it seems to reload the map meshes and textures when I open settings or change a setting, although it doesn't happen all the time. This still happens in 0.33.

This issue is still happening for me as well. It's usually just the screen flashing white, but it also sometimes shows weird colors and artifacts:

Edit - A couple screenshots from 0.33:

 

Nothing happens at all when I start vulkan