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.
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.
Some you may have missed, popular articles from the last month:
Quoting: eddie-fossQuoting: neowiz73oops :P yeah I've been using 364.12 myself. haven't seen anything like that yet though. maybe they should just upgrade it to vulkan :P
it would be interesting to test out.
Well, If they decide to change to Vulkan, possibly they will need to rewrite entire program because of the API architectural difference (opengl4 stands against dx11 as vulkan stands against dx12) and imho this is work for the original developers and not for Feral (which probably doesn't have permission to change so much source code) since Vulkan also works in Windows and overall costs will be less, basically two (or more) platforms at the price of one.
Probably this bug is a buffer allocation conflict and not so hard to fix since character renders comes apart from world and objects render.
I was only joking, thus the :P emote, I understand it would require the source code to make these changes to the original game engine. Which would require Monolith Productions to do so, which I of course *highly doubt* would ever happen.
But it would be nice to see for a rare occasion a few devs get a wild hair up their rear end to do something fun and unexpected.
0 Likes
Can someone try this? I'm not at home:
http://steamcommunity.com/app/241930/discussions/0/385428943467348986/?tscn=1459256286#c385429254950534634
http://steamcommunity.com/app/241930/discussions/0/385428943467348986/?tscn=1459256286#c385429254950534634
0 Likes
Quoting: GuestQuoting: edddeduckferalThat is a theory but it's incorrectWell reading your post you said the same thing I did so I don’t see how it’s incorrect: there were other issues in the non-nvidia drivers so they couldn’t be used to detect that specific bug. Maybe I didn’t express myself clearly. No big deal anyway :).
I was replying to you and the OP you originally replied to.
I thought you were implying that testing AMD (open/closed) drivers would have helped expose this bug in some way and by that you were also implying we didn't test on them during development and that we should have.
Given we did test in them (a lot!) during development the overall premise was false.
Your point about the bug being hidden or untestable was true however it was the overall implications I wanted to clarify as that concerns the effort we spend on AMD/Intel support.
Glad you're in agreement that this made no difference at all given we always develop and test on multiple drivers! :-)
Hope that clears everything up. :-)
Last edited by edddeduck_feral on 29 March 2016 at 6:13 pm UTC
0 Likes
Quoting: leillo1975Can someone try this? I'm not at home:
http://steamcommunity.com/app/241930/discussions/0/385428943467348986/?tscn=1459256286#c385429254950534634
This workaround fix the problem:
In Launch Options add this :
__GL_ShaderPortabilityWarnings=0 %command%
1 Likes, Who?
Quoting: leillo1975Quoting: leillo1975Can someone try this? I'm not at home:
http://steamcommunity.com/app/241930/discussions/0/385428943467348986/?tscn=1459256286#c385429254950534634
This workaround fix the problem:
In Launch Options add this :
__GL_ShaderPortabilityWarnings=0 %command%
I'd contact Feral support for the patch info so you can get a real patch details but that workaround in the meantime should work just fine.
0 Likes
Quoting: edddeduckferalQuoting: PeciskEdwin, I will just say that I will buy Shadow Of Mordor (has been eyeing it for some time now) just because of community support and communication like this. Thanks. Keep being awesome.
Thanks :)
I totally bought Mordor due to the Feral port to Linux - I've learned to trust Feral ports. Trust me when I say this, many of us here want to see you get a LOT more business - I just hope there's enough of us for that to matter :-)
0 Likes
Quoting: HalifaxThen we just need good folks like you and others to buy their ports when they arrive, and not before :)Quoting: edddeduckferalQuoting: PeciskEdwin, I will just say that I will buy Shadow Of Mordor (has been eyeing it for some time now) just because of community support and communication like this. Thanks. Keep being awesome.
Thanks :)
I totally bought Mordor due to the Feral port to Linux - I've learned to trust Feral ports. Trust me when I say this, many of us here want to see you get a LOT more business - I just hope there's enough of us for that to matter :-)
0 Likes
I'd like to add for anyone still following this, that
"force_glsl_extensions_warn=true MESA_EXTENSION_OVERRIDE=GL_ARB_arrays_of_arrays __GL_ShaderPortabilityWarnings=0 %command%"
in the steam launch options box works for me, but
"__GL_ShaderPortabilityWarnings=0 %command%"
unfortunately did not.
Anyone know if Feral are any closer to an official patch? It's been awhile.
"force_glsl_extensions_warn=true MESA_EXTENSION_OVERRIDE=GL_ARB_arrays_of_arrays __GL_ShaderPortabilityWarnings=0 %command%"
in the steam launch options box works for me, but
"__GL_ShaderPortabilityWarnings=0 %command%"
unfortunately did not.
Anyone know if Feral are any closer to an official patch? It's been awhile.
2 Likes, Who?
All they've said is that an update including a fix is in the works. No mention of a release date, but if you have problems you can request access to the beta.
1 Likes, Who?
Just searched for this. I've just decided to be properly bleeding edge and use 367 for my 970. And the floating head exists now :( Also loads of missing textures - it's like some of the ground is kind of glass and seethrough...
I'll see if I can get access to this beta patch I guess by just emailing them?
I'll see if I can get access to this beta patch I guess by just emailing them?
0 Likes
See more from me