Vulkan API – Feedback, Known Issues, and FAQ

Any help appreciated. Fresh install of BeamNG. Running with Vulkan API framerate is capped at 45FPS. If I run in DX12 mode it is running 100-200FPS. Doesn't matter if I use borderless, windowed or fullscreen. Tried clearing the cache but nothing appears to fix it. PC specs are 9950X3D, 64GB RAM and RTX 5090 (no overclock or undervolt). Note: playing flat screen, tried resolutions of 1920x1080 and 3440*1440 (monitor default)

IGNORE - Fixed it. In NVIDIA Control Panel, had the max frame rate set to 90 FPS. For some reason having this set, limited the Vulcan API render to 45FPS. Removed it and all good. Now just use the limiter in the game.

 

I wonder if it is something to do with AMD cards. I also have an AMD 6900XT (fully up to date as well).

Ive tried all i can think of, including Nadeox's clean re-install method, changed every graphical setting in game, to no avail. I am not running any AMD 'boost' software of any kind either, just the base setup. I just wanna take pretty screenshots in 0.39 so I'm excited for the fix. I haven't heard new updates on my error report except that its been sent to the team to investigate. I cant find any loading errors in the console or anything, i am at a complete loss.

Derby Arena is the only map where i have no issue, Johnson Valley is nearly unplayable.

Any chance of a dev update in this thread?

---

Specs: Win10, AMD R7 5700G, AMD 6900XT, 32GB DDR4 RAM.
--- Post updated ---
Some more info in case it is helpful! a texturing issue, perhaps?

 

Hi all, new to the forums.

I have an ultrawide monitor with native resolution of 3440x1440. My laptop is running BeamNg 0.39 okay, 45-60fps depending on the map. I wanted to bring it a little bit closer to 60 by lowering in-game resolution, but on Vulkan the only 21:9 resolution I get in the dropdown is the native one. Other resolutions are for 16:0 or 16:10.

I'm on Linux running the native build, as suggested by devs, so Vulkan is the only option. For testing I tried running Beam with Proton enabled, so it uses the Windows build, and funnily enough there I have the option to choose lower resolutions for my monitor's aspect ratio but the game's performance in noticeably worse for me than on the native build.

The only way I managed to set lower resolution is by running the game via gamescope, but I was encountering random freezes on some actions like exiting vehicle or interacting with vehicle parts, so I stopped using it. Maybe not really freezes, because the game was still running and I could hear changing audio when I was doing inputs, just the screen was stuck on specific frame but when I switched to another window and back, the frame was updated to current one, but still stuck. I assume it is gamescope quirk, especially that I have nVidia GPU.

I tried setting the resolution manually in the settings json file, but it seems to revert it back to the native one on game launch.

Tried searching for solution, but without any luck. So any advise would be much appriciated!

 

It wouldnt surprise me if it was specific to the 6000 series AMD cards. Ive had issues a few months ago with my VR specifically because im on a 6000 series card (something to do with liquidVR being old). Hopefully this can be fixed soon.

 

I noticed that this black square issue appears sometimes with my regular graphics settings (High preset with a couple changes), but less severe. In the picture below, I found that enabling the dedicated vehicle shadow makes the squares appear in the rear door windows on the D-Series extended cab. Again, I confirmed that this same behavior happens on Windows as well.

 

V1 materials appear translucent on vulkan and this also seems to occur on DX12 but a vehicle reload works on DX to fix this sometimes

 

Hi.
Just had GPU memory crash playing one of the new challenges on Italy map (TastiCola Driver). Crash happened about a minute after I connected the trailer.
Never had such a crash before. Not sure if its more Vulkan or Linux related.

I've also sent the crash report via game. Anything else needed?
OS: CachyOS x86_64
Kernel: Linux 7.2.9-2-cachyos-bore
Display (34GP950G): 3440x1440 @ 1.2x in 35", 144 Hz
Desktop Environment: KDE Plasma 6.8.0
CPU: AMD Ryzen 7 5800X3D
GPU: AMD Radeon RX 6800 XT
Memory: 62.69 GiB

Drivers are up to date I believe, CachyOS update doesn't show any new Mesa version available.

 

I think it be helpful if you ran the game with the arguments shown in the image to make it possible for the developers to trace your issue.
Im running Linux 7.2.9.2-cachyos-rt-bore-lto kernel with KDE Plasma 6.7.5 and im not experiencing this issue when i run the game natively.