Vulkan API – Feedback, Known Issues, and FAQ

4GB is just not enough for new games anymore. Oh well, exciting and expensive purchase here I come!

 

4GB isn't enough for anything these days. Not even web browsing. The internet is bloated to hell and back

 

I have both Jedi: Fallen order and the sequel Jedi: Survivor (both very good game 100% recommend survivor). The older one (Fallen order) was always buttery smooth (50FPS+) no matter what was happening. With Survivor (the newer one) your lucky to get 40+ FPS If anything is going on, and the game practically dies during any cutscene with a lightsaber. The second one looks slightly better, but with a large performance drop. Is it worth it? Absolutely not. I would take Fallen order graphics with 60 FPS over Survivor graphics and 40 FPS if I'm idle.

 

I will try that, and post the log. It's reliably reproduceable on all my AMD hardware. I have tested on the following:

Win 10
R5 3600X
24GB DDR4
RX 5700 XT
SATA SSD

Win 11
R7 5800X
32GB DDR4
RX 6900 XT
NVMe SSD

Linux
R7 5700X
64GB DDR4
RX 6750 XT
NVMe SSD

In vulkan mode, on all those setups, I can reproduce the issue. It's not video ram being depleted either, I actually monitored for that, and see it never exhaust the video ram. On the 6900 and 6750 systems, it never goes over 8GB usage. I've even tried various settings around this, from lowest to ultra. Here is a short clip I captured today of this happening. The game is still running too, but the video output just tanks. VR or not VR, does not matter. Interestingly it only happens once I have loaded a car.

--- Post updated ---

Attached log file.

This is probably the issue, and is repeated a lot:

Code:

174.43411|E|engine::GFXVkDevice::submit::<lambda_f7b834df781f17b5eec4590cba01f1aa>::operator ()| (submit) Failed to submit to transfer queue [ErrorDeviceLost]
174.43414|W|engine::debug_messenger_callback| : Validation Warning: [ UNASSIGNED-BestPractices-Error-Result ] Object 0: handle = 0x23ddd6294a0, type = VK_OBJECT_TYPE_INSTANCE; | MessageID = 0x5f379b89 | vkQueueSubmit(): Returned error VK_ERROR_DEVICE_LOST.
174.43415|E|engine::GFXVkDevice::submit::<lambda_f7b834df781f17b5eec4590cba01f1aa>::operator ()| Failed to submit to graphics queue [ErrorDeviceLost]

 

So on all PCs listed?

 

On the 2 windows ones, yeah, but only with the Canyon Rush map.

Actually got this error a few times too, though logs suggest the same thing as I previously posted:

 

Hello! Back in January I made this post about how GPUs with less VRAM have performance issues in Vulkan. Well I'm back at testing it again and I can happily say that it has improved quite a lot since that date!

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

"With Vulkan my FPS drop drastically in big maps like Italy or WCU but increase in small maps like Gridmap."
This stays the same, but the FPS improvement is massive!

• BEFORE on WCUSA ULTRA: 16 FPS AVG

I was also getting GPU, CPU and Game Engine Bottleneck

• NOW on WCUSA ULTRA: 30 FPS AVG

Now only GPU bottleneck occurs



This is now a PLAYABLE experience, unlike the previous version where it was almost impossible to play.
I also have to mention that in this version, Detailed Mirrors are enabled, unlike before, when this feature wasn't available which gives us a little more advantage with a few extra FPS.

 

Hello BeamNG devs.
I would like to report about a problem I have with the Vulkan renderer.
My game version is 0.32.2.0
My CPU is the Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz
My GPU is the NVIDIA GeForce RTX 2060 SUPER
I have about 24Gb of RAM
I run the game on Windows 11

When I launch the game with the Vulkan renderer (without safe mod), the window of the game appears, stay white for a few seconds, and then a crash occurs.
The error code is: 0x00000001

If I try to run the game with Vulkan in safe mod, the game crashes without any window appearing. I obtain the following error code:
0xC0000005 - STATUS_ACCESS_VIOLATION

I have included the log file in the post.
After looking a little bit at the log, it appears that there is a problem in the compilation of two shaders:
-/shaders/common/specPrefilter.hlsl as we can see at the line 548 of the log
-/shaders/common/postFx/dof/DOF_Final_P.hlsl as we can see at the line 552 of the log

To try to solve the problem, I tried to clear the cache, verify the integrity of the files of the game, but the issue was still here.
I tried after to uninstall/reinstall the game. I still have the problem even with the new installation, so it is probably not an issue caused by a mod.

I would also like to say that I successfully launched the game with Vulkan about one month ago, but since I did not tried again until now, I do not know when the problem started.

I have the latest GeForce Game Ready Driver: version 556.12. The driver may be the issue so I could try downgrading a few versions and see if it solves the problem.

Also, I have the latest version of the Vulkan SDK installed on my computer for my personal coding projects.
This probably should not affect the game in any way, but it may be possible that there are some kind of conflicts between the SDK and the renderer? I thought it was worth mentioning.
When I compile and run my personal programs with the SDK, it works on my computer, so, my hardware should be compatible with Vulkan.

I hope this will help you figure out what could be going wrong.
Also, I would like to say that I really appreciate you reading this, because this is probably just a weird bug occurring because I did something wrong, and that you must be flooded everyday with questions about "why the Vulkan renderer does not work".

So, anyway. If anyone has a clue about what could be going wrong, I would gladly accept the help.
And if this is a bug, I hope this will help you solve it!

 

Hello again BeamNG devs.
I found the solution to the problem I was facing.

To solve the problem, I did this:
-Start the game with the DirectX renderer.
-Set the graphical setting to lowest.
-Run the Vulkan renderer (this time it launches)
-Load a map
-Put back all the graphical setting to max one by one.
-All graphical settings are okay, except for the depth of field.

When activating the depth of field in the Vulkan renderer, the game crashes instantly.
To restart the Vulkan renderer, I need to launch the game again in DirectX and then, disable the depth of field there.
I do not know if I am the only user with this problem but if it isn't the case, then maybe there is a problem with the compilation of the depth of field shader: "DOF_Final_P.hlsl ", like we could see in the log of my last post.

The game is now running smoothly on my end, except for the depth of field and I appreciate the performance boost that the Vulkan renderer gives me.
And if no one reported this issue before, I am glad to help!

 

Im having problems in vulkan where the UI freezes whenever i open the word editor, and my game ignores all input except movement (no the game isnt in the background), if i force relaod ui well, it doesnt reload ui at all and ui debug throws no errors so im sort of confused (i did launch in safe+vulkan and same thing), this happened after my game hung up when i changed the reflection resolution down (STATUS_APPLICATION_HANG, after waiting for it to respond for 10 minutes)

and this happens on all maps now, i cleared cache and tried DX which works no problem
--- Post updated ---

funny thing that happens to my game is that both my ram or vram arent full to the brim (including OS running in bg) when i encounter slowdowns on my 1660 super, its only after i reach 5650-5750mb of vram usage globally (game in those instances uses 4800-5100mb depending) that fps tanks (ram usage doesnt affect it) and both gpu and cpu utilisation skyrocket, and it doesnt seem to dig into page either just stays at that vram usage until it eventually fills to the full and my graphics driver crashes (yes idk why welcome to samsung vram being funky)

 

Here you go.
What I did:
-Set the launch option on Steam to -gfx vk debug
-Launch the game (automatically starts Vulkan renderer)
-Load the map gridmap v2 (the framerate was very low probably due to the debug launch option)
-Open the settings and activate depth of field
-The game crashes

If now I want to launch the game again with Vulkan it will crash on startup, without even showing the main menu.
To be able to launch it again, I need to start the DirectX renderer, remove the depth of field option, and then relaunch with Vulkan.

(Three files were generated so I put them here anyway)

Hope this helps

 

Any fix yet for the abysmall performance drops when vram runs out?

 

funny thing that happens to my game is that both my ram or vram arent full to the brim (including OS running in bg) when i encounter slowdowns on my 1660 super, its only after i reach 5650-5750mb of vram usage globally (game in those instances uses 4800-5100mb depending) that fps tanks (ram usage doesnt affect it) and both gpu and cpu utilisation skyrocket, and it doesnt seem to dig into page either just stays at that vram usage until it

i hope 0.33 will be the update to optimise everything under the hood and improve the game (pliz make all gui run on the new system it so much better )

 

Running BeamNG as Vulkan will cause a crash right away. I've tried repair, reinstall, and it still causes a crash.
Game, graphics driver, and Windows 11 are all the latest versions

 

Ive found that transparent over transparent object is what vulkan absolutely hates, in DX11 if you se a precipitation object itll work as normal but in VK the transparency is all over the place and whenever a drop passes anything else with transparency both materials become fully transparent

 

Hello KRBW, it seems like you are facing the same issue as I.
I looked at the logs that you attached to your message and it seems like there is a problem with the compilation of the depth of field shader.
What it basically means is that the "depth of field" option in the graphics settings does not work with the Vulkan renderer.

Try launching the game with the normal renderer and change the settings:
-Go to the option menu
-Open the "graphics" tab
-Uncheck the box "Depth of field"
The graphics settings that you select are shared between the two renderers. It means that if you disable the depth of field in the normal renderer, it will also get disabled in the Vulkan renderer.

So now, with depth of field disabled, try to run again the Vulkan renderer.
Hopefully the game will not crash on startup anymore.

I hope this will work for you!