-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Black screen in Open Lara (Tomb Raider) Linux #9546
Comments
Just checked to be sure, OpenLara standalone works (build from source). |
PPSSPP is also crashing here (on wayland, with RA built with Wayland support and without X11 - because it's slow in wayland since it goes through a emulation) because of libglew for some reason. Note that i'm using the 'gl' driver not 'egl' but it's still crashing on I think it might be because some cores are assuming a 'core' profile (4 ish) not a compatibility one (3.3 ish) and my card only works in 'compatibility' because it's super old on mesa support to support even 3.3 (mesa being a hybrid cpu/gpu graphical driver). |
Ok the 'root' cause of this and the other ppsspp problem is probably this (if you're using wayland like i am): https://unix.stackexchange.com/questions/511134/why-wayland-is-using-opengl-es-instead-of-opengl to remove awkward dependencies (X11), wayland uses currently only opengl-es, which probably means RA is probably using it in 'on the sly' my case where i compiled without X11 (X11 emulation slowed down the menu) and with wayland support and i still used When i just now tried to remove even opengl-es (and leave opengl) with
Which looks to be supporting evidence that the 'gl' driver is more like a 'gles/egl' driver on this situation and as was already mentioned by unknownbrackets in the link he gave, PPSSPP doesn't like that without a further setup. OpenLara might be on the same situation on a wayland context. |
I have the same problem on Android 32 9pie OpenLara. |
I can't reproduce your issue on Linux using the demo. |
I am still having this issue in the current OpenLara core. |
@3XistencE @demonstrable Can you provide some log ? Thank you. |
Black screen in TR1,2,3. The games runs and i can hear music and moving around in the menu.
Tried different drivers (those who work),switching windows fullscreen and exclusive mode enabling HW context, different resolutions. Shell output returns in all three games:
Loaded game!
Context reset!
OpenLara (Jul 29 2019)
Vendor : X.Org
Renderer : AMD RAVEN (DRM 3.27.0, 5.0.0-29-generic, LLVM 8.0.0)
Version : 4.5 (Compatibility Profile) Mesa 19.1.4
cache : /home/user1/Roms/openlara/tr2/data/openlara/cache/
supports :
variyngs count : 16
binary shaders : true
vertex arrays : true
depth texture : true
shadow sampler : true
discard frame : false
NPOT textures : true
3D textures : true
RG textures : true
border color : true
clip distance : false
anisotropic : 16
float textures : float = full, half = full
shader: cache warm-up...
shader: cache is ready
meshes: 12
atlas: 512 x 1024
MegaMesh (i:57006 v:10507 a:3, size:450236)
Read Slots...
Protocol error: bad 3 (Window); Sequence Number 11
Opcode (20, 0) = GetProperty
Bad resource 0 (0x0)
at -e line 16.
Other 3D games and emus using OGL work fine. Searched for the issue in OpenLara before RA , but couldn't find anything related. TIA!
The text was updated successfully, but these errors were encountered: