Vulkan API – Feedback, Known Issues, and FAQ

Is there any official response on this? I'm not the only one having this issue, I've had reports (2) from people experienceing this on Linux (I'm on Windows) as well. Do you need a log of any kind to help the diagnose? Please let us know since Vulkan is currently unusable in my opinion.

 

Decided to give Vulkan an other try, on my now likely one of the older rigs here.

On East Coast (what probably was my last test as well, oops ) performance is between 41 and 47 fps, so about the same value as last year.
With traffic performance has subsistentially improved, from well below 20 now in the 32-38 fps range. I consider that playable, especially if you start lowering settings as well.

In my quick test frame drops still existed tho, even without any traffic, and they were quite frequent. They seem to drop into single digits, similiar to as if you would spawn vehicles in.

Stats still unchanged: I5-8400, GTX 1060 3GB, 16GB RAM, Windows 10

 

The issue you’ve noticed:
A black screen upon starting with Vulkan. Tried Safe Mode with Vulkan, same issue. DirectX is still fine.

This happens when:
Starting the game using Vulkan.

My specs are:
CPU: i7-11700K @ 3.60 GHz
GPU: NVIDIA RTX 3060 12 GB
RAM: 32 GB @ 3600 MHz

 

Relating back to what i wanted to report here but then didnt because it seemed that it was gone. However just the conditions have changed and given that i saw alot of reports of it in various discords i thought it was already reported here, but hasnt been or so it seems.

Bug
Heavy graphical glitches that get worse the more vehicles are spawned and the lower the fps go.
See video.


Please not just note the obvious graphical glitches! Also see how the ui sometimes vanishes, how the lod in the background changes and how the debug spheres spazz out.
There is more to it, sometimes vehicles also go invinsible for a moment and objects appear at higher positions then they actually are. Imagine the blue balls suddenly appearing a meter higher in the air for a moment.

How to reproduce
1. Spawn into any map
2. Spawn a bunch of vehicles
3. See graphical spazz

Before you ask, yes this also happens on every other map and in safemode. The more vehicles spawned and the worse the fps -> the worse these glitches get on my end.

My specs are:
OS: Windows 10 Pro 22H2 (19045.5487)
CPU: i5 9600K (6 core)
GPU: AMD Radeon RX 7700 XT (Driver v.25.3.1)
RAM: DDR4 32Gb @ 2666Mhz
Dxdiag: Shows 0 errors

This gets so bad at times that i fear of getting a epileptic attack

 

Hello!
I want to know what minimum version of vulkan need for Beamng.drive because GTX 600-700 series doesnt support version 1.3

 

This somehow fixed itself...

 

Just wanted to add some info related to this issue. It definitely happens more often with lower fps. What I've done is set the unfocused fps limit to 5 fps, and when I click out of the game, it starts happening almost immediately. I have found this to be a repeatable way of making the bug appear.

Here's a weird one I got recently:

 

Bump, this Vulkan precipitation particle issue still exists in the newest game version.

 

This issue is still present in 0.36. If i can do anything to help debugging this, then please let me know

 

Gave Vulkan another go in 0.36.
Good news: Vulkan is pretty stable and the game can load any map now
Bad news: Performance is worse than DirectX.

While with DirectX I can get 30FPS in WCA on normal settings...


...with Vulkan that drops massively.

 

If you have a weak GPU, vulkan isn't going to be a performance increase for you.

Here is a perfect example. Identical systems, only a GPU change.

RTX 5070



RTX 5070Ti



If you run out of Vram in Vulkan the performance absolutely tanks

Its interesting though because the RTX 5070 in D3D mode was totally playable.

 

This is still happening for me and it feels like its worst this update (0.36) A list if things I have tried:
cache clean both deep and normal, disable mods, unistall mods, clean install Beamng, clean install windows 10 on a new boot drive, move beamng to main drive (C: ), have beamng and its user folder on same drive, reinstalling VS 2015 redistribute, reinstall graphics drivers before and after new drive, countless verify files of both steam and beamng launcher and safe mode.
None of these attempts have fixed. This is only happening on my main computer. This doesn't happen on my old prebuilt which has 2070 and i7-9700, doesn't happen on my steam deck but it happens on my main with a 3080ti and i9-10850k, game is now installed on a 990 evo plus 4TB ssd. No other game with vulkan has this problem and this used to not happen before 0.31 with this computer. It doesn't matter if its full screen, windowed or what I normally play windowed borderless. locking frame rate has no noticeable difference in the glitch and the only fix I can find is to turn lighting to the lowest setting.
Please tell me if there is anything more I can do or show to help, this bug is driving me crazy.

 

I didnt play that much recently but from the few hours I played under 0.35, I dont think I had any graphical issues. But with the new update, Im getting basically constant screen flickering. D3D11 is okay. Im running modified Fedora 42 (Nobara) and Radeon 6800XT, Mesa 25.1.3, Vulkan 1.4.313.
Unable to test the native linux version since it will immidiately crash after loading the map and default vehicle.

 

maps take ages to load



this happens when I try to play on any map

my specs
CPU: AMD Ryzen 7 5800H
GPU: RTX 3070 Laptop
OS: Windows 11 Home

 

if I switch between traffic cars, my fps drops to 20 frames per second and sometimes lower. This also happens when creating other cars. FPS is usually reduced on a 6-7 machine. Sometimes, if you delete this car, everything will return to normal. I noticed that this is happening because of the dynamic mirrors. If I turn them off before creating new cars and turn them on after creating them, then everything is fine. Also when enabling fullscreen mode

 

I have the same issue under KDE Wayland on Arch, however the native version starts just fine in the KDE X11 session. 0.35 ran fine on Wayland. idk it might be a driver or KWin issue

 

Here's a positive for Vulkan..............

10 year old CPU i7 5775c with 16GB DDR3 2133 Ram..........with a 5090.....yes not a normal combination but Vulkan makes the game 100% playable

 

Hey! It's time to review the latest Vulkan update in 0.36.

Specs recap:
NVIDIA GeForce RTX 3050 Laptop GPU
11th Gen Intel Core i7 - 11800H (2.3GHz)
16GB of RAM

• 0.31 on WCUSA ULTRA: 16 FPS AVG

I was also getting GPU, CPU and Game Engine Bottleneck

• 0.32 on WCUSA ULTRA: 30 FPS AVG

Now only GPU bottleneck occurs

• 0.33 on WCUSA ULTRA: Game gets stuck in loading screen
• 0.34 same thing as in 0.33
• 0.35 on WCUSA ULTRA: 4FPS AVG

0.36 on WCUSA ULTRA 7FPS AVG

• GPU usage is below 50% at all times due to the dedicated GPU RAM being maxed out
• CPU usage is non existent
• RAM stays at 65% percent
• In summary: same issues with VRAM still occur