Black screen in Open Lara (Tomb Raider) Linux

[ghost]

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!

[ghost]

Just checked to be sure, OpenLara standalone works (build from source).

[i30817]

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 glewInit(). Complaining upstream told me PPSSPP needs a function called to use a egl context but i was not aware i was even using one! Or can force opengl if the driver setting doesn't work.

hrydgard/ppsspp#12145

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).

[i30817]

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 video_driver="gl" on the config.

When i just now tried to remove even opengl-es (and leave opengl) with --disable-egl RA couldn't even start graphics

[WARN] Failed to bind API (#1, version 0.0) on context driver "wayland".
[INFO] [GL]: Found GL context: null
[WARN] Failed to bind API (#1, version 0.0) on context driver "wayland".
[INFO] [GL]: Found GL context: null

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.

[3XistencE]

I have the same problem on Android 32 9pie OpenLara.
I have black screen with white polygons around after the last core update.
I can hear sounds but i pratically don't have graphic, everything is black and there's some white polygon that moves in accord with the camera.
I can assume what's the health bar and there's some kind of white distant lara shapes polygons, if i fire i can see the colored flame sprites in the right position, hear the sounds etc...
Tested both PC and PSX versions

[gouchi]

I can't reproduce your issue on Linux using the demo.

[demonstrable]

I am still having this issue in the current OpenLara core.

[gouchi]

@3XistencE @demonstrable Can you provide some log ?

Thank you.

[jmaneyrol69]

I got the same issue on all my systems (Windows, Linux, Android) using TR1 full game. I have tried using both PC version and PSX and it did not help.

This seems specific to the libretro core; I haven't had the problem using the port from PortMaster (https://portmaster.games/detail.html?name=tomb.raider.1&devices=).

[gouchi]

@jmaneyrol69 Can you try to make a test with using the demo and provide some log ?

Please bear in mind, this core needs OpenGL >= 3.0 or OpenGL ES >= 2.0 and supported extensions are "phd|psx|tr2"

Source

Thank you.

[jmaneyrol69]

Hi @gouchi , this is will not do with the demo : the game starts right into gameplay, and that is not the problem here.

The issue happens when trying to start the full retail game "normally", that is with TITLE.PSX. For instance, if I launch openlara with LEVEL2.PSX, it works as expected. So the problem cannot be reproduced with the demo since it does not have any videos.

The main issue here is when starting with a .PSX that includes a video at start: the screen remains black until we get into the game. If you start the game with TITLE.PSX, for example, the screen is black when playing the intro movie, then remains black in the menu until you start a game.

I have found two workaround to this: either press Start and action twice - this will run the training game in the mansion - and then get back to the menu, or start openlara with GYM.PSX: the screen will remain black when playing the video but everything will get back in order once the game start, and you can get back to the menu and start a new game.

Then everything works at it should: videos are being played normally, etc.

This issue does not make the game unplayable, but it is impossible to watch the opening movie, like on the real game. I do not believe it to be a video driver issue: all my computers and Android handhelds are capable of OpenGL >= 3.0 or OpenGLES >=2.0.

If I had to guess, I would say that something is wrong, or missing, during the core initialization, which makes it unable to play videos at start.

I can provide you with some logs, but you will have to guide me on how to generate them.

Also, I think you should not rely on the demo to reproduce; if you could get a hand on a retail version, that would help a lot in investigating the issue, imo.

Please let me know if you need any more information.

[gouchi]

@jmaneyrol69 Thank you for the explanation. I understand better the issue.

It is a known issue 1 2.

P.S = We should close this issue in favor of the ones in the core repository.