We do often include affiliate links to earn us some pennies. See more here.

NVIDIA have released the 415.18.02 Vulkan beta driver

By - | Views: 10,017

For those interested, NVIDIA have now updated their special Vulkan beta drivers with 415.18.02 so they're a little less behind.

They have now added support for the Turing GPU architecture, which includes the RTX 2080 Ti, RTX 2080 and the RTX 2070.

They also noted this release has bug fixes for VK_EXT_transform_feedback, the newer Vulkan extension that was made to primarily help projects like DXVK. This extension is still not supported in their regular drivers, hopefully them rebasing this on their latest driver series is progress towards that.

It's worth noting, some users have seen issues with this newer driver breaking Unity games in Wine. So if you're using Steam Play or DXVK with Wine directly, you may want to hold off or do some extra research before using it. Not just this beta driver, the whole 415 series from NVIDIA seems to be suffering issues.

Personally, I noticed Rocket League performing a lot worse with 415.18 as well.

Article taken from GamingOnLinux.com.
Tags: Drivers, NVIDIA
14 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
8 comments

Xpander Nov 29, 2018
So far so good. except the mentioned unity games crashes.

Performance seems same as 396.54.09 and theres no stuttering unlike previous 415.x drivers

unity issue here: https://devtalk.nvidia.com/default/topic/1044264/linux/415-13-breaking-unity-engine-games-in-wine/post/5297975

make yourself heard, so this gets more attention
mrdeathjr Nov 29, 2018
According nvidia json file:

Quote{
"file_format_version" : "1.0.0",
"ICD": {
"library_path": "__NV_VK_ICD__",
"api_version" : "1.1.92"
}
}



Update:

Cuphead crash

GetThreadContext failed

^_^


Last edited by mrdeathjr on 29 November 2018 at 10:41 am UTC
mao_dze_dun Nov 29, 2018
Yup, sticking to 396.54.09, for now. Damn shame.
Leeo97one Nov 29, 2018
I think the issue is more related to DXVK than to Unity. Because the affected games work if I disable DXVK on Steam with:
PROTON_USE_WINED3D11=1 %command%
dreamer_ Nov 29, 2018
Quoting: Leeo97oneI think the issue is more related to DXVK than to Unity. Because the affected games work if I disable DXVK on Steam with:
PROTON_USE_WINED3D11=1 %command%

It's definitely related to new drivers. Yesterday I could comfortably play The Room 2 and it worked just fine, then after installing new drivers "GetThreadContext failed". There was no game update, no Proton update, no Steam update... only drivers changed.
deathxxx Nov 29, 2018
For me, Nvidia Drivers: 410.78 is run best with SteamPlay and Dark Souls III.
396 --> poor performance
415 --> poor performance
410.78 --> best performance and no lag.

That is how i do it:
This is how to run Dark Souls III on Ubuntu 18.04 via SteamPlay with Steam client beta for smooth play.

Hardware on this system:
CPU: core i7 6700K
GPU: GTX 1060 with 6GB GDDR5 RAM
RAM: 32GB DDR3 RAM

Software on this system:
OS: Ubuntu 18.04 64bit
Nvidia Drivers: 410.78 (from ppa:graphics-drivers/ppa)
Steam client: beta
Proton used: 3.16-4 Beta
Audio Config: analog 5.1 surround (audio channels are important. with only stereo, you may have bad sound, using 2.1, 4.1, 5.1 audio channels gives me clear sound)
Audio Card: Creative X-Fi with 20K1 chipset

#################################################################################################
# Instruction to get best possible FPS and clear audio for this system, and maybe any symilar else.
#################################################################################################

# THIS IS FOR NVIDIA CARDS!

# 1. Install Ubuntu 18.04 64bit with ext4 file system.
# 2. Install Steam Client and opt into the Linux Steam Client Beta. Update client and make sure it's running. Make sure this game will forced to run with Proton 3.16-4 Beta.
# 3. Install ppa for better and newer drivers for Nvidia Cards(use exactly 410 series driver, all other have bad performance or even non-running game):
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt install nvidia-driver-410

# 4. Reboot the system now to finish driver installation.
# 5. Play the game with max settings.


Last edited by deathxxx on 29 November 2018 at 6:55 pm UTC
Leeo97one Nov 29, 2018
Quoting: dreamer_
Quoting: Leeo97oneI think the issue is more related to DXVK than to Unity. Because the affected games work if I disable DXVK on Steam with:
PROTON_USE_WINED3D11=1 %command%

It's definitely related to new drivers. Yesterday I could comfortably play The Room 2 and it worked just fine, then after installing new drivers "GetThreadContext failed". There was no game update, no Proton update, no Steam update... only drivers changed.
Of course, this is a driver issue, but I meant that the error occurs in all DirectX 10/11 games using DXVK, Unity or not.
But never mind, I was wrong because I tested with a non-Unity game like GTA V and it works fine with DXVK.


Last edited by Leeo97one on 29 November 2018 at 8:09 pm UTC
Spyker Nov 29, 2018
Not only it crashes with unity games, but it also freeze The witcher 3 with DXVK (with a mutex deadlock) :
The Witcher 3 Wild Hunt\bin\x64\witcher3.exe: ../nptl/pthread_mutex_lock.c:434: __pthread_mutex_lock_full: Assertion `robust || (oldval & FUTEX_OWNER_DIED) == 0' failed.
AL lib: (EE) ReleaseThreadCtx: Context 0x7d673810 current for thread being destroyed, possible leak!
The Witcher 3 Wild Hunt\bin\x64\witcher3.exe: ../nptl/pthread_mutex_lock.c:434: __pthread_mutex_lock_full: Assertion `robust || (oldval & FUTEX_OWNER_DIED) == 0' failed.
0043:err:ntdll:RtlpWaitForCriticalSection section 0x142936aa8 "?" wait timed out in thread 0043, blocked by 0042, retrying (60 sec)

It's the same with the old DXVK version which was working fine before, so it's not a new bug from the latest DXVK version.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.