Not exactly too different from previous Nvidia 364.x drivers, but this now makes the Nvidia 364.19 driver throw off the beta label and is stable enough in their eyes.
If you're going from one stable release to this one, there's a lot of changes, but if you've been keeping up with the beta versions it's still obviously a good idea to update.
It adds official Vulkan support, Wayland & Mir support, reworked PRIME support, OpenGL now uses their GLVND GLX by default and more.
You can download it here (changelog here too), or wait for it to be in your usual repository.
If you're going from one stable release to this one, there's a lot of changes, but if you've been keeping up with the beta versions it's still obviously a good idea to update.
It adds official Vulkan support, Wayland & Mir support, reworked PRIME support, OpenGL now uses their GLVND GLX by default and more.
You can download it here (changelog here too), or wait for it to be in your usual repository.
Some you may have missed, popular articles from the last month:
Quoting: crazyg4merzWayland support without DE support. Is there any link concerning this problem in Nvidia forum? I want to see the answer from Nvidia about this. Thanks :)
idk about the nvidia forums but there was a discussion regarding Nvidia's EGLStreams going on in the wayland-devel mailing list.
The weston guys didn't really like it enough to support it, as did everyone else.
This new update seems to be featuring some extra work towards wayland support. Perhaps they'll like it better this time.
0 Likes
Quoting: kon14This new update seems to be featuring some extra work towards wayland support. Perhaps they'll like it better this time.
They are still using EGLStreams, etc, so nothing has changed at all. So for now, if you want to use nvidia with wayland, the only option is to use the nouveau driver.
Last edited by rune on 23 April 2016 at 9:07 am UTC
0 Likes
Quoting: kon14I'm actually waiting for nvidia to get their shit together so as to be able to run Sway (an i3 compatible wayland wm based on wlc, a wayland compositor library) on my desktop :/
Same here.
0 Likes
Quoting: runeThey are still using EGLStreams, etc, so nothing has changed at all. So for now, if you want to use nvidia with wayland, the only option is to use the nouveau driver.
They are indeed and I don't think they'll be switching to gbm any time soon though depending on their implementation and their inclination towards blink games wayland compositor devs may choose to support them anyway.
0 Likes
The Ubuntu Graphics Team PPA has been updated with 364.19 :D
1 Likes, Who?
In my case this drivers stay working good
For now test saint row the third and works stable in large test
View video on youtube.com
^_^
Last edited by mrdeathjr on 23 April 2016 at 4:01 pm UTC
For now test saint row the third and works stable in large test
View video on youtube.com
^_^
Last edited by mrdeathjr on 23 April 2016 at 4:01 pm UTC
1 Likes, Who?
Quoting: kon14Afaik weston is not used by Gnome and other WM as they have their own compositor. So if Gnome developers decided to support it, we can get it working in Gnome right? Is Nvidia doing it the right way or is it just Gnome doing it using their own way? I really don't understand why are there different ways just to support wayland, so what's working on Nvidia driver if we can't even test the weston itself which is the default compositor of Wayland? Sorry I'm a noob in this kind of thing. :)Quoting: crazyg4merzWayland support without DE support. Is there any link concerning this problem in Nvidia forum? I want to see the answer from Nvidia about this. Thanks :)
idk about the nvidia forums but there was a discussion regarding Nvidia's EGLStreams going on in the wayland-devel mailing list.
The weston guys didn't really like it enough to support it, as did everyone else.
This new update seems to be featuring some extra work towards wayland support. Perhaps they'll like it better this time.
0 Likes
Quoting: crazyg4merzAfaik weston is not used by Gnome and other WM as they have their own compositor. So if Gnome developers decided to support it, we can get it working in Gnome right? Is Nvidia doing it the right way or is it just Gnome doing it using their own way? I really don't understand why are there different ways just to support wayland, so what's working on Nvidia driver if we can't even test the weston itself which is the default compositor of Wayland? Sorry I'm a noob in this kind of thing. :)
I only referenced weston cause it's the example/reference compositor maintained by the wayland devs that's meant to showcase wayland and its capabilities. No serious de is going to use weston as a base (besides most of the big de's wms are already ported over and standalone compositors won't fork it either).
Basically my understanding of the whole situation goes like this: The wayland devs and everyone related decided to go with gbm while nvidia was totally absent and now nvidia comes along with their own alternative after everyone has implemented the solution agreed upon.
In order for EGLStreams to work out wayland compitors are going to have to support them and, apart from software not being written and maintained by its own, that would fragment development and possibly even the wayland compositor scene (an already fragmented place compared to X11 where there's something more substantial besides a protocol for the compositors to implement).
tldr nvidia was late to the party and now they request that the party be restarted for them, the wayland devs are not against eglstreams due to design issues, but rather due to the fact that nvidia are being assholes trying to fix a non existent issue all over again just cause they like their solution better and don't much care about everyone else. (not really a tldr)
Last edited by kon14 on 23 April 2016 at 5:23 pm UTC
0 Likes
Quoting: liamdaweNot exactly too different from previous Nvidia 364.x drivers, but this now makes the Nvidia 364.19 driver throw off the beta label and is stable enough in their eyes.Nvidia seemingly forgot to make an announcement for it, but the previous 364.16 release was also a non beta.
1 Likes, Who?
Der Treiber performt extrem Geil bei mir...klasse Treiber.
In Talos Principle hab ich mit der VulkanAPI fette 67% mehr Leistung...einfach so...gegenüber OpenGL.
Ich muss das morgen mal im Windows per Dx9/11 laufen lassen und zu Vulkan vergleichen.
Aber diese 67% Steigerung find ich enorm...hätte ich so nicht erwartet!
CPU: Intel Core i7-3770K@Stock Frequenz
GPU: nVidia GeForce GTX 660 Ti
Kann den Treiber daher nur jeden wärmsten empfehlen!
Last edited by FlYeRoNe on 23 April 2016 at 9:30 pm UTC
In Talos Principle hab ich mit der VulkanAPI fette 67% mehr Leistung...einfach so...gegenüber OpenGL.
Ich muss das morgen mal im Windows per Dx9/11 laufen lassen und zu Vulkan vergleichen.
Aber diese 67% Steigerung find ich enorm...hätte ich so nicht erwartet!
21:12:30 INF: - benchmark results -
21:12:30 INF:
21:12:30 INF: Gfx API: OpenGL
21:12:30 INF: Duration: 60.0 seconds (5412 frames)
21:12:30 INF: Average: 90.2 FPS (93.5 w/o extremes)
21:12:30 INF: Extremes: 177.8 max, 16.7 min
21:12:30 INF: Sections: AI=6%, physics=1%, sound=1%, scene=62%, shadows=24%, misc=6%
21:12:30 INF: Highs: 824 in 6.0 seconds (137.9 FPS)
21:12:30 INF: Lows: 910 in 14.7 seconds (61.9 FPS)
21:12:30 INF: 30-60 FPS: 5%
21:12:30 INF: > 60 FPS: 95%
22:58:04 INF: - benchmark results -
22:58:04 INF:
22:58:04 INF: Gfx API: Vulkan
22:58:04 INF: Duration: 60.0 seconds (9037 frames)
22:58:04 INF: Average: 150.6 FPS (153.2 w/o extremes)
22:58:04 INF: Extremes: 300.6 max, 46.5 min
22:58:04 INF: Sections: AI=9%, physics=3%, sound=1%, scene=61%, shadows=16%, misc=10%
22:58:04 INF: Highs: 1263 in 6.7 seconds (187.9 FPS)
22:58:04 INF: Lows: 1568 in 12.8 seconds (122.7 FPS)
22:58:04 INF: > 60 FPS: 100%
CPU: Intel Core i7-3770K@Stock Frequenz
GPU: nVidia GeForce GTX 660 Ti
Kann den Treiber daher nur jeden wärmsten empfehlen!
Last edited by FlYeRoNe on 23 April 2016 at 9:30 pm UTC
2 Likes, Who?
See more from me