lr-reicast fails to launch (x86/x64)

johnodon

Pi Model or other hardware: Ubuntu 18.04.1 x64 on two different PCs
Power Supply used: n/a
RetroPie Version Used: 4.4.2
Built From: Retropie setup script
USB Devices connected: KB
Controller used: none
Error messages received: none visible when launching in ES. see below for other details.
Log found in /dev/shm/runcommand.log (if relevant):
Guide used: https://retropie.org.uk/docs/Debian/
File: /opt/retropie/libretrocores/lr-reicast/reicast_libretro.so
Emulator: Retroarch (lr-reicast)
Attachment of config files:
How to replicate the problem: Follow the guide above to build RP on Ubuntu. Install the lr-reicast core from experimental. Copy rom and bios to appropriate locations. Try to launch ROM.

lr-reicast is able to launch Dreamcast, Naomi and Atomiswave-->Naomi roms fine on my Win10 install of Retroach. When I try the same roms on my ubuntu build, they fail to launch. If I try to launch via SSH (just to see the output), I see this message but not sure if it is related:

[reicast]: Got size: 640 x 480.
Creating dir: /home/pi/RetroPie/roms/arcade//dc/data
mkdir(/home/pi/RetroPie/roms/arcade//dc/data) error: No such file or directory.
Segmentation fault (core dumped)

Can someone else verify that this is broken on x86?
What else can I provide to help troubleshoot?

I am rebuilding my test box now and will be able to provide the segfault info that is dumped in a terminal when launched manually. Stay tuned...

mitu

@johnodon Are you running RetroArch with --v to get a verbose log ? Maybe you'll see where the crash occurs.

johnodon

@mitu said in lr-reicast fails to launch (x86/x64):

@johnodon Are you running RetroArch with --v to get a verbose log ? Maybe you'll see where the crash occurs.

Will do. Installing the core now. Where will that log be written to or is just output to the terminal?

mitu

@johnodon If you launch from the terminal, it's on the terminal output, if you use the Runcommand launch menu to select verbose logging it will be in /dev/shm/runcommand.log. Why are you rebuilding the core ? Doesn't installation on x86 platforms already rebuilds the core from source ?

johnodon

@mitu said in lr-reicast fails to launch (x86/x64):

@johnodon If you launch from the terminal, it's on the terminal output, if you use the Runcommand launch menu to select verbose logging it will be in /dev/shm/runcommand.log. Why are you rebuilding the core ? Doesn't installation on x86 platforms already rebuilds the core from source ?

I didn't perform a basic install...just the core packages and the lr-reicast package.

When I said 'rebuilding' I meant reinstalling from scratch.

johnodon

runcommand.log --> https://pastebin.com/V1U3y8tB

Guessing that this is the important part:

uniform lowp float sp_ShaderColor; 
/* Vertex input*/ 
void main() 
{ 
#if TARGET_GL != GLES2 
	float w = gl_FragCoord.w * 100000.0; 
   gl_FragDepth = log2(1.0 + w) / 34.0; 
#endif 
   gl_FragColor=vec4(0.0, 0.0, 0.0, sp_ShaderColor); 
}
[libretro INFO] Fatal error : shader compile fail

 in gl_CompileAndLink -> core/rend/gles/gles.cpp : 447 
DEBUGBREAK!

johnodon

Maybe this is the same issue others saw with Retroarch and 18.04? I'll try a different video driver (right now it is gl)

johnodon

Well, this fixed the crash:

https://retropie.org.uk/forum/post/152319 ( have Intel HD graphics so it is at the bottom of that post).

Setting DRI = 2 or 3 have a seriously negative impact on performance, even in the ES gui.

mitu

@johnodon No, it's not because of the renderer, it's a core issue - something similar to https://github.com/libretro/reicast-emulator/issues/199.

johnodon

Is this really just my bad timing to test that core? :)

mitu

@johnodon Maybe, it can also be the build options in the script are not covering all the bases. Just to rule out the build options, you could try installing RetroArch and the core directly and see if it works (using a recent build of RA and the core).

johnodon

@mitu said in lr-reicast fails to launch (x86/x64):

@johnodon Maybe, it can also be the build options in the script are not covering all the bases. Just to rule out the build options, you could try installing RetroArch and the core directly and see if it works (using a recent build of RA and the core).

I'll do that. Stay tuned.

barbudreadmon

@johnodon i answered in https://retropie.org.uk/forum/post/157269 .

johnodon

@barbudreadmon said in lr-reicast fails to launch (x86/x64):

@johnodon i answered in https://retropie.org.uk/forum/post/157269 .

Thanks @barbudreadmon. I saw your answer in the other thread and will manually create the /dc/data folder in the rom path. However, I think @mitu is right and this is a core issue.

I re-installed 18.04 and pulled RA/cores from the testing/nightly PPA which gave me a different version of the lr-reicast core (0.1-r201808021716-31c1caf-7~ubuntu18.04.1) and all worked as expected.

If I compile from git (lr-reicast commit 4a44ef4), I get the crashes. Diegoviola, who opened the original issue for when compiling shaders, has opened a second issue:
https://github.com/libretro/reicast-emulator/issues/203

@mitu thinks this may be the culprit.

John

mitu

@johnodon said in lr-reicast fails to launch (x86/x64):

@mitu thinks this may be the culprit.

I said what you're experiencing might be a similar issue, not the same (since the issue I mentioned was already solved). The issue you posted though seems like the one you're experiencing.
If the PPA works, then there might be a problem with the build options in the RetroPie-Setup script. The setup script will pull the latest version from github, so maybe the PPA was created from a previous commit. You can open the RGUI and the core version should be at the bottom, so you can compare both versions.

EDIT: rephrasing.

barbudreadmon

@johnodon said in lr-reicast fails to launch (x86/x64):

I saw your answer in the other thread and will manually create the /dc/data folder in the rom path

Then you misread my answer, the issue lies in your config, and that's 100% sure from the output you posted. While creating this folder could work, this is not the root issue. Anyway i'm 100% sure your issue is unrelated to rendering stuff, as explained your system directory is not properly handled by your configuration (because of one of the 2 parameters i mentioned), so :

it won't locate your bios
it will try to create a folder it shouldn't and can't.

johnodon

UPDATE: @barbudreadmon I deleted the data folder at /home/pi/Retropie/BIOS/dc and the script was able to create it at that location without error so this indeed looks like that was a configuration issue.

@barbudreadmon as far as the path issue, I performed a fresh RP install on a new a clean build of Ubuntu Server x64 18.04.1 and manually created the paths. The path errors have disappeared. These are the only things I did...

I manually created /home/pi/Retropie/roms/dreamcast/dc/data/. The 'dc' folder has the relevant bios files.
I also copied the bios files to /home/pi/Retropie/BIOS/dc/
As far as RP install, the ONLY things I did that are 'non-standard' are:
- Install the lr-reicast core
I did not make any other configuration changes

I launched the game with verbose logging.

pi@ubuntu:/dev/shm$ cat runcommand.info
dreamcast
lr-reicast
/home/pi/RetroPie/roms/dreamcast/Army Men - Sarge's Heroes (USA)/Army Men - Sarge's Heroes (USA).gdi
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-reicast/reicast_libretro.so --config /opt/retropie/configs/dreamcast/retroarch.cfg "/home/pi/RetroPie/roms/dreamcast/Army Men - Sarge's Heroes (USA)/Army Men - Sarge's Heroes (USA).gdi"

runcommand.log is here: https://pastebin.com/xt2CCzP4

Line 213 is where we start to see the compile failures:

[libretro INFO] Using Recompiler
Sh4 Reset
recSh4 Init
Freeing fpcb
Shader: failed to compile 
0:1(10): error: GLSL 1.40 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES

Shader: failed to compile 
0:1(10): error: GLSL 1.40 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES

@mitu I listed the core versions I was getting with nightly PPA vs GIT here (31c1caf vs. 4a44ef4 respectively): https://retropie.org.uk/forum/post/157385

This was verified by looking at the core version in RA itself. FYI...this last install put me at commit bbcc720c with the same result.

0_1534077100760_f5d734d1-788d-4524-8b40-57a032091754-image.png

barbudreadmon

@johnodon said in lr-reicast fails to launch (x86/x64):

I manually created /home/pi/Retropie/roms/dreamcast/dc/data/. The 'dc' folder has the relevant bios files.

Again, that's not something you have to do if the 2 parameters i mentioned (system_directory and systemfiles_in_content_dir) have the proper values.

It seems you indeed have a renderer issue besides the path issue, those happen a lot depending on hardware/commit, try opening an issue on github, and don't forget to mention your hardware.

johnodon

@barbudreadmon said in lr-reicast fails to launch (x86/x64):

@johnodon said in lr-reicast fails to launch (x86/x64):

I manually created /home/pi/Retropie/roms/dreamcast/dc/data/. The 'dc' folder has the relevant bios files.

Again, that's not something you have to do if the 2 parameters i mentioned (system_directory and systemfiles_in_content_dir) have the proper values.

It seems you indeed have a renderer issue besides the path issue, those happen a lot depending on hardware/commit, try opening an issue on github, and don't forget to mention your hardware.

Sounds good. I just wanted to confirm that this wasn't a retropie script issue before I go posting an issue on the libretro github.

Thanks for the help guys!

John

BuZz

we had one problem with the script and docs which I have fixed in that it said to put the BIOS in the ~/RetroPie/BIOS folder instead of the ~/RetroPie/BIOS/dc folder. I assume the location must have changed at some point. However this issue shouldn't have caused your problem and it's working fine on my system.