Announcement

Collapse
No announcement yet.

Here Is What Happens When Trying To Use Non-NVIDIA Drivers To Play XCOM 2 On Linux

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • atomsymbol
    replied
    Originally posted by zeb_ View Post
    The issue was found: LC_ALL was set to French language, which uses comma as decimal separator. LC_ALL should be unset.
    Just something related: I have had problems with uncommon language settings when running Steam games in the past. I solved it by adding "export LANG=en_US.utf8" to the script from which I am usually starting steam.sh.

    Note: That being said, it would be better if Steam and Steam games worked with any valid LC_* and LANG settings.
    Last edited by atomsymbol; 16 February 2016, 10:02 AM. Reason: Add a note

    Leave a comment:


  • zeb_
    replied
    The issue was found: LC_ALL was set to French language, which uses comma as decimal separator. LC_ALL should be unset.

    Leave a comment:


  • zeb_
    replied
    I have further news: it is now working on my "non-working" machine using a brand new user account! So that means the issue is not system wide, but related to some user specific setting. I am quite puzzled, because I had initally reinstalled Steam entirely on my non-working user account and it did not solve the issue. So that means the problem is with another file. It is also a relief, because diagnosing it should be a lot simpler. I will let other users having the same issue know, and see if they see the same thing, and if they can help figure out the cause.

    Leave a comment:


  • zeb_
    replied
    Originally posted by carewolf View Post
    That looks like Chromium debug output, probably just from an embedded webview. Also explains why it is GLES, Chromium uses GLES (or WebGL), to transfer OpenGL commands between their processes.
    Yes, but I do not see these messages when running Alien Isolation for instance.
    These errors seem unrelated, but could they interfere with a game?
    Last edited by zeb_; 09 February 2016, 05:16 AM.

    Leave a comment:


  • zeb_
    replied
    I (and 4 other users on Steam) have the same issue with Nvidia drivers: it does not crash, but main menu and maps are black with some drawing artifacts. Case is discussed here: http://steamcommunity.com/app/268500...6292761093493/

    The GL debug output has these context errors:
    Code:
    [0208/202928:ERROR:gl_context_glx.cc(107)] Couldn't make context current with X drawable.
    [0208/202928:ERROR:gles2_cmd_decoder.cc(3200)] GLES2DecoderImpl: Context lost during MakeCurrent.
    [0208/202928:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0208/202928:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0208/202928:WARNING:x11_util.cc(1490)] X error received: serial 926, error_code 171 (GLXBadDrawable), request_code 154, minor_code 26 (X_GLXMakeContextCurrent)
    [0208/202928:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0208/202928:ERROR:gl_context_glx.cc(107)] Couldn't make context current with X drawable.
    [0208/202928:ERROR:gles2_cmd_decoder.cc(3200)] GLES2DecoderImpl: Context lost during MakeCurrent.
    [0208/202928:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0208/202928:WARNING:x11_util.cc(1490)] X error received: serial 958, error_code 8 (BadMatch (invalid parameter attributes)), request_code 154, minor_code 26 (X_GLXMakeContextCurrent)
    [0208/202928:ERROR:gl_context_glx.cc(107)] Couldn't make context current with X drawable.
    [0208/202928:ERROR:gles2_cmd_decoder.cc(3200)] GLES2DecoderImpl: Context lost during MakeCurrent.
    [0208/202928:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0208/202928:WARNING:x11_util.cc(1490)] X error received: serial 987, error_code 8 (BadMatch (invalid parameter attributes)), request_code 154, minor_code 26 (X_GLXMakeContextCurrent)
    [0208/202928:ERROR:gl_context_glx.cc(107)] Couldn't make context current with X drawable.
    [0208/202928:ERROR:gles2_cmd_decoder.cc(3200)] GLES2DecoderImpl: Context lost during MakeCurrent.
    [0208/202928:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0208/202928:WARNING:x11_util.cc(1490)] X error received: serial 1015, error_code 8 (BadMatch (invalid parameter attributes)), request_code 154, minor_code 26 (X_GLXMakeContextCurrent)
    [0208/202928:ERROR:gl_bindings_autogen_gl.cc(6522)] Trying to call glDeleteVertexArraysOES() without current GL context
    [0208/202928:WARNING:x11_util.cc(1490)] X error received: serial 1044, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
    Feral says they have not been able to reproduce yet.
    The strange thing is that Xpander69 has almost the same system than me (Archlinux 64, GTX970) and it works for him with 361.18 drivers. I also tried 352.63, same issue. Other games like Alien Isolation, Civ V and Shadow of Mordor work fine!

    Leave a comment:


  • efikkan
    replied
    And once again every driver except one struggles as a new title is coming to Linux. These driver vendors really need to get their act together.

    Leave a comment:


  • carewolf
    replied
    Originally posted by JLSalvador View Post
    Crash too with the proprietary NVIDIA v361 980 :'-(

    Code:
    [0204/200309:ERROR:gl_context_glx.cc(107)] Couldn't make context current with X drawable.
    [0204/200309:ERROR:gles2_cmd_decoder.cc(3200)] GLES2DecoderImpl: Context lost during MakeCurrent.
    [0204/200309:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0204/200309:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0204/200309:WARNING:x11_util.cc(1490)] X error received: serial 838, error_code 171 (GLXBadDrawable), request_code 154, minor_code 26 (X_GLXMakeContextCurrent)
    [0204/200309:ERROR:gl_context_glx.cc(107)] Couldn't make context current with X drawable.
    [0204/200309:ERROR:gles2_cmd_decoder.cc(3200)] GLES2DecoderImpl: Context lost during MakeCurrent.
    [0204/200309:ERROR:gl_bindings_autogen_gl.cc(6831)] Trying to call glGetGraphicsResetStatusARB() without current GL context
    [0204/200309:WARNING:x11_util.cc(1490)] X error received: serial 868, error_code 8 (BadMatch (invalid parameter attributes)), request_code 154, minor_code 26 (X_GLXMakeContextCurrent)
    [0204/200309:ERROR:gl_bindings_autogen_gl.cc(6522)] Trying to call glDeleteVertexArraysOES() without current GL context
    [0204/200309:ERROR:gl_bindings_autogen_gl.cc(6512)] Trying to call glDeleteTextures() without current GL context
    That looks like Chromium debug output, probably just from an embedded webview. Also explains why it is GLES, Chromium uses GLES (or WebGL), to transfer OpenGL commands between their processes.

    Leave a comment:


  • pdffs
    replied
    To be honest, even the 'officially supported' Nvidia implementation is pretty sub-par. Due to a combination of Nvidia being intransigent in their opinions about how RandR 1.2 should be used, and Feral's rushed implementation, I can't even change resolution, no matter what I do - the game hard-resets the resolution to whatever is reported via RandR 1.2, and Nvidia only returns native EDID-reported resolutions (they refuse to provide scaled metamodes via RandR 1.2, even though every other driver does it, because reasons). Even if I change the desktop resolution, I end up seeing a fraction of the game viewport, which will only (and always, it overwrites any changes made to the config by hand) render at the native 4k of my panel, and at 4k the game is completely unplayable from a performance perspective on a 970m.

    Really don't know what to do here, because I'd like not to miss my refund window if it's not going to be fixed, but I really would like to play this, if it was playable.

    Leave a comment:


  • Detructor
    replied
    Originally posted by chuckula View Post

    I think that some people around here don't want to actually see any test results Michael. I think they just want a wall of text rant about how AMD GOOD and everyone else BAD.

    There are plenty of other websites out there that cater to their needs.
    Originally posted by Michael
    What are you talking about? The Radeon driver was where most of the tests happened.
    I'm making this real easy for you two: On the first page of the article Michael wrote this:
    Mesa 11.2-devel with LLVM 3.9 (via the Padoka PPA) and the Linux 4.5-rc2 kernel (with AMDGPU PowerPlay enabled) was used for this testing... I don't plan on doing any older Mesa tests, since Mesa Git offers the best OpenGL 4 extension coverage as well as the best performance
    Which is, for obvious reason, untrue. It also means AMDGPU was used for the entire test (unless I'm missing something here).

    Leave a comment:


  • Michael
    replied
    Update: http://www.phoronix.com/scan.php?pag...onSI-G3D-XCOM2

    Leave a comment:

Working...
X