Support us on Patreon
PayPal
Update: We have a fix detailed here for you.
Just a heads up, you might want to avoid Nvidia driver 364.12 is you play Shadow of Mordor (or want to play it soon). Nvidia have stated it's an issue Feral Interactive need to fix:
Say hello to my good friend, floaty head (source):
I am still using the 358 driver series myself, as it seems the 355 series doesn't work on Ubuntu 16.04.
Hopefully Feral Interactive will offer up a fix soon. Article taken from GamingOnLinux.com.
Just a heads up, you might want to avoid Nvidia driver 364.12 is you play Shadow of Mordor (or want to play it soon). Nvidia have stated it's an issue Feral Interactive need to fix:
QuoteThis is a known application bug. It has been reported to Feral Interactive, the company that ported the game to Linux.
Say hello to my good friend, floaty head (source):
I am still using the 358 driver series myself, as it seems the 355 series doesn't work on Ubuntu 16.04.
Hopefully Feral Interactive will offer up a fix soon. Article taken from GamingOnLinux.com.
0 Likes
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: EagleDeltaFrom what I gather, it sounds like this is an application bug rather than a driver bug. NVidia has been removing features that allowed developers to take shortcuts with OpenGL (IIRC) and this has been breaking games that used those shortcuts. While I'm sure this is partially NVidia's fault for allowing this in the first place, I hope we can all realize that a vast majority of issues (at least what I've seen) with the new drivers are, in fact, application bugs that the new driver triggers/makes apparent.I would tend to agree with you:
https://www.gamedev.net/topic/666419-what-are-your-opinions-on-dx12vulkanmantle/#entry5215019
But breaking up games is not a solution either. SR4 went from 40-50fps to 20-25fps on my rig.
I'm not sure what's the best to do: get rid of this total mess right now, keep legacy stuff somewhere or count on Vulkan and proper behaviours to let old DirectX and OpenGL die out. Maybe independant and floss frameworks that ease the use of Vulkan without creating havoc inside drivers is the best thing to do, but that will take a looong time before to get results.
0 Likes
Quoting: lucinossupporting only closed source drivers, is of course better than nothing, but is should never considered a job well done that does not need fix.
This example demonstrate why.
It didn't run all that well on closed source drivers anyway. I found the framerate drops made it unplayable.
0 Likes
Quoting: Psycic101QuoteJust a heads up:P hehe, I see what you did there
Hahaha, happy accident!
0 Likes
Good thing then distros usually don't update to newest versions automatically :)
0 Likes
Quoting: EagleDeltaQuoting: NelI'm currently playing Saints Row 4 and I also had missing textures with 364.12. But above all, this driver has a huge performance drop on this game, so I reverted back to 355.11.
I played some other games with 364.12: Sky Force Anniversary, Outland and Little Racers Street, but didn't notice anything wrong. Performance wise, these games are not very demanding for my 660gtx to experience any fps drop.
From what I gather, it sounds like this is an application bug rather than a driver bug. NVidia has been removing features that allowed developers to take shortcuts with OpenGL (IIRC) and this has been breaking games that used those shortcuts. While I'm sure this is partially NVidia's fault for allowing this in the first place, I hope we can all realize that a vast majority of issues (at least what I've seen) with the new drivers are, in fact, application bugs that the new driver triggers/makes apparent.
Is there actual reference when Nvidia acknowledges this? If so, then it is really good news. Considering most of distributions won't autoupgrade to this version gives some time for devs to fix games before issues become more visible.
0 Likes
Quoting: NelQuoting: EagleDeltaFrom what I gather, it sounds like this is an application bug rather than a driver bug. NVidia has been removing features that allowed developers to take shortcuts with OpenGL (IIRC) and this has been breaking games that used those shortcuts. While I'm sure this is partially NVidia's fault for allowing this in the first place, I hope we can all realize that a vast majority of issues (at least what I've seen) with the new drivers are, in fact, application bugs that the new driver triggers/makes apparent.I would tend to agree with you:
https://www.gamedev.net/topic/666419-what-are-your-opinions-on-dx12vulkanmantle/#entry5215019
But breaking up games is not a solution either. SR4 went from 40-50fps to 20-25fps on my rig.
I'm not sure what's the best to do: get rid of this total mess right now, keep legacy stuff somewhere or count on Vulkan and proper behaviours to let old DirectX and OpenGL die out. Maybe independant and floss frameworks that ease the use of Vulkan without creating havoc inside drivers is the best thing to do, but that will take a looong time before to get results.
OpenGL won't die any time soon. In fact, improvements in Mesa stack, fixing AMD sitution and Nvidia will allow OpenGL to shine again. It is beneficial to everyone to root out these shortcuts, even for Nvidia, because it helps with QA later down the road.
0 Likes
Funnily enough Shadow of Mordor renders just fine on my R7 370 with open source drivers. Everything is on as low as it goes and I had to override some missing GL spec but I definitely see more than just the head.
0 Likes
Quoting: SamsaiFunnily enough Shadow of Mordor renders just fine on my R7 370 with open source drivers. Everything is on as low as it goes and I had to override some missing GL spec but I definitely see more than just the head.
Renders fine on a 290x with the cat drivers too.
0 Likes
See more from me