[RESOLVED] ES Returns to menu when RA launches

"Solution/Cause:" The problem seemed to be my Thrustmaster T16000M FCS ST or T16k Joystick

Hello!

Just upgraded to V5 following the update procedures.

Now when I launch a game it will appear to launch and then ES will do that thing where it returns to the menu as if the game failed to launch. The problem is the game -did- launch in the background, and is running.

The menu videos and all of that start playing over the game sound and the RA/Game doesn't come up to the front.

I'm doing some more tests now but this also happened on a 1 rom fresh install I made of V5 in a different folder.


1. Select game
2. the black screen with the game screenshot/title comes up
3. a moment
4. ES goes back to the menu as if the game failed to launch
5. the game is running in the background


Edit: Upon further testing it seems as if the games will not actually launch until I try one time post update. So if I try a game I havent tried after V5, it will fail, if I try again it launches but still has the behavior described above. Edit 1/2: This is apparently not universally true.

Edit2: Retroarch with logging on seems normal, the games actually seem to work fine.

Found this in the es log

Code:

2022-12-10 18:43:22 ERROR Resource path not found: :/locale/fallback/es-features.po
2022-12-10 18:43:22 ERROR Resource path not found: :/locale/fallback/LC_MESSAGES/es-features.po
2022-12-10 18:43:22 ERROR Resource path not found: :/locale/lang/fallback/es-features.po
2022-12-10 18:43:22 ERROR Resource path not found: :/locale/lang/fallback/LC_MESSAGES/es-features.po
2022-12-10 18:43:22 ERROR Resource path not found: :/es_features.locale/fallback/es-features.po
2022-12-10 18:43:22 ERROR Resource path not found: :/locale/fallback/emulationstation2.po
2022-12-10 18:43:22 ERROR Resource path not found: :/locale/fallback/LC_MESSAGES/emulationstation2.po
2022-12-10 18:43:22 ERROR Resource path not found: :/locale/lang/fallback/emulationstation2.po
2022-12-10 18:43:22 ERROR Resource path not found: :/locale/lang/fallback/LC_MESSAGES/emulationstation2.po
2022-12-10 18:43:22 ERROR Resource path not found: :/es_features.locale/fallback/emulationstation2.po
2022-12-10 18:43:32 ERROR Resource path not found: :/gamesplash.xml


emulatorlauncher.log

Code:


2022-12-10 19:03:24.090 [INFO]    --------------------------------------------------------------
2022-12-10 19:03:24.102 [INFO]    [Startup] "D:\RetroBat\emulationstation\emulatorLauncher.exe"  -gameinfo "C:\Users\dan\AppData\Local\Temp\emulationstation.tmp\game.xml" -p1index 0 -p1guid 030000005e040000e002000000007200 -p1path "BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&0002045E_PID&02E0\9&1AD08668&1&E417D8EB8D7F_C00000000" -p1name "Xbox One S Controller" -p1nbbuttons 16 -p1nbhats 1 -p1nbaxes 6  -system n64 -emulator libretro -core mupen64plus_next -rom "D:\RetroBat\roms\n64\Star Fox 64 (USA) (Rev 1).zip" -state_slot 3
2022-12-10 19:03:24.151 [INFO]    [Game] Star Fox 64
2022-12-10 19:03:24.271 [INFO]    [Generator] Using LibRetroGenerator
2022-12-10 19:03:24.551 [INFO]    [SdlGameControllers] 2 SDL controller(s) connected
2022-12-10 19:03:24.554 [INFO]    [SdlGameControllers] Loading SDL controller mapping : 0 => 00000003-045e-0000-e002-000000007200, Xbox One S Controller, BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&0002045E_PID&02E0\9&1AD08668&1&E417D8EB8D7F_C00000000
2022-12-10 19:03:24.556 [INFO]    [SdlGameControllers] Loading Unknown SDL controller mapping : 1 => 00000003-044f-0000-0ab1-000000000000, , USB\VID_044F&PID_B10A\1
2022-12-10 19:03:24.614 [INFO]    [Running] D:\RetroBat\emulators\retroarch\retroarch.exe -L "D:\RetroBat\emulators\retroarch\cores\mupen64plus_next_libretro.dll" "D:\RetroBat\roms\n64\Star Fox 64 (USA) (Rev 1).zip"


ES log verbose

Code:


2022-12-10 19:03:23 INFO Attempting to launch game...
2022-12-10 19:03:23 INFO computePlayersConfigs : Player 0 => BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&0002045E_PID&02E0\9&1AD08668&1&E417D8EB8D7F_C00000000
2022-12-10 19:03:23 INFO Configure emulators command : -p1index 0 -p1guid 030000005e040000e002000000007200 -p1path "BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&0002045E_PID&02E0\9&1AD08668&1&E417D8EB8D7F_C00000000" -p1name "Xbox One S Controller" -p1nbbuttons 16 -p1nbhats 1 -p1nbaxes 6
2022-12-10 19:03:23 DEBUG AudioManager::deinit
2022-12-10 19:03:23 INFO SDL AUDIO Deinitialized
2022-12-10 19:03:24 DEBUG fireEvent: game-start "D:\RetroBat\roms\n64\Star Fox 64 (USA) (Rev 1).zip" Star Fox 64 (USA) (Rev 1) Star Fox 64
2022-12-10 19:03:24 INFO "D:/RetroBat/emulationstation\emulatorLauncher.exe" -gameinfo "C:\Users\dan\AppData\Local\Temp\emulationstation.tmp\game.xml" -p1index 0 -p1guid 030000005e040000e002000000007200 -p1path "BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&0002045E_PID&02E0\9&1AD08668&1&E417D8EB8D7F_C00000000" -p1name "Xbox One S Controller" -p1nbbuttons 16 -p1nbhats 1 -p1nbaxes 6  -system n64 -emulator libretro -core mupen64plus_next -rom "D:\RetroBat\roms\n64\Star Fox 64 (USA) (Rev 1).zip" -state_slot 3
2022-12-10 19:03:26 WARNING ...launch terminated with nonzero exit code -1,073,741,819!


So I was chugging along testing roms and configurations etc. For some reason I needed to hard wire my bluetooth controller. The next game I launched went correctly.

Code:


2022-12-11 10:48:57 INFO Attempting to launch game...
2022-12-11 10:48:57 INFO computePlayersConfigs : Player 0 => USB\VID_045E&PID_028E&IG_00\7&18CAA3F4&2&00
2022-12-11 10:48:57 INFO Configure emulators command : -p1index 0 -p1guid 030000005e0400008e02000000007200 -p1path "USB\VID_045E&PID_028E&IG_00\7&18CAA3F4&2&00" -p1name "Xbox 360 Controller" -p1nbbuttons 11 -p1nbhats 1 -p1nbaxes 6
2022-12-11 10:48:57 DEBUG AudioManager::deinit
2022-12-11 10:48:57 INFO SDL AUDIO Deinitialized
2022-12-11 10:48:57 DEBUG fireEvent: game-start "D:\RetroBat\roms\n64\Star Fox 64 (USA) (Rev 1).zip" Star Fox 64 (USA) (Rev 1) Star Fox 64
2022-12-11 10:48:57 INFO "D:/RetroBat/emulationstation\emulatorLauncher.exe" -gameinfo "C:\Users\dan\AppData\Local\Temp\emulationstation.tmp\game.xml" -p1index 0 -p1guid 030000005e0400008e02000000007200 -p1path "USB\VID_045E&PID_028E&IG_00\7&18CAA3F4&2&00" -p1name "Xbox 360 Controller" -p1nbbuttons 11 -p1nbhats 1 -p1nbaxes 6  -system n64 -emulator libretro -core mupen64plus_next -rom "D:\RetroBat\roms\n64\Star Fox 64 (USA) (Rev 1).zip" -state_slot 3
2022-12-11 10:53:06 DEBUG fireEvent: game-end  
2022-12-11 10:53:06 INFO Window::init


I thought surely the bluetooth controller wasn't at fault? And it doesn't seem to be because the next and every other launch after that has the same problem.

Code:

2022-12-11 10:53:16 INFO Attempting to launch game...
2022-12-11 10:53:16 INFO computePlayersConfigs : Player 0 => USB\VID_045E&PID_028E&IG_00\7&18CAA3F4&2&00
2022-12-11 10:53:16 INFO Configure emulators command : -p1index 0 -p1guid 030000005e0400008e02000000007200 -p1path "USB\VID_045E&PID_028E&IG_00\7&18CAA3F4&2&00" -p1name "Xbox 360 Controller" -p1nbbuttons 11 -p1nbhats 1 -p1nbaxes 6
2022-12-11 10:53:16 DEBUG AudioManager::deinit
2022-12-11 10:53:16 INFO SDL AUDIO Deinitialized
2022-12-11 10:53:16 DEBUG fireEvent: game-start "D:\RetroBat\roms\n64\Star Wars - Shadows of the Empire (USA) (Rev 2).zip" Star Wars - Shadows of the Empire (USA) (Rev 2) Star Wars : Shadows of the Empire
2022-12-11 10:53:16 INFO "D:/RetroBat/emulationstation\emulatorLauncher.exe" -gameinfo "C:\Users\dan\AppData\Local\Temp\emulationstation.tmp\game.xml" -p1index 0 -p1guid 030000005e0400008e02000000007200 -p1path "USB\VID_045E&PID_028E&IG_00\7&18CAA3F4&2&00" -p1name "Xbox 360 Controller" -p1nbbuttons 11 -p1nbhats 1 -p1nbaxes 6  -system n64 -emulator libretro -core mupen64plus_next -rom "D:\RetroBat\roms\n64\Star Wars - Shadows of the Empire (USA) (Rev 2).zip" -state_slot 1
2022-12-11 10:53:18 WARNING ...launch terminated with nonzero exit code -1,073,741,819!
2022-12-11 10:53:18 DEBUG fireEvent: game-end  

As a fruther test I ran that emulator launcher exe command in CMD directly and it launches just fine... for some reason es is reading it as a launch failure?

----

12/12 Edit

So I unplugged EVERY PERIPHERAL and it worked as expected.
I connected my 8BitDo and it worked.
I connected my Razar Tartarus Keypad back and it still worked.
When I plugged my Thrustmaster t16000 flight stick in (I didn't need it, it just happened to be connected), bam there's the error.

Following Caruso's advice there was some stuff in the Windows Application Logs (found in Event Viewer)
Application Error

Code:


Faulting application name: emulatorLauncher.exe, version: 1.0.0.0, time stamp: 0x6387d7b9
Faulting module name: SDL2.DLL, version: 2.24.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0012d635
Faulting process id: 0x3ccc
Faulting application start time: 0x01d90e776ff36c0a
Faulting application path: D:\RetroBat\emulationstation\emulatorLauncher.exe
Faulting module path: D:\RetroBat\emulationstation\SDL2.DLL
Report Id: eb1c9af2-64e1-4889-898b-2f693dfe865f
Faulting package full name:
Faulting package-relative application ID:


.Net Runtime Error

Code:


Application: emulatorLauncher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 7BC3D635


Error Reporting Information

Code:


Fault bucket 1840766823777223552, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: emulatorLauncher.exe
P2: 1.0.0.0
P3: 6387d7b9
P4: SDL2.DLL
P5: 2.24.0.0
P6: 00000000
P7: c0000005
P8: 0012d635
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4A0B.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B55.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B65.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B73.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B93.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_emulatorLauncher_a7b3d7566c93f3a6604bad78e6bd66dccc7fd3f_57502ebe_c1144ce1-d214-4205-8afb-eeddc8ef3786

Analysis symbol:
Rechecking for solution: 0
Report Id: eb1c9af2-64e1-4889-898b-2f693dfe865f
Report Status: 268435456
Hashed bucket: 31e5d745941bdef9598bb7ac6590c380
Cab Guid: 0


Theres a couple posts around the net regarding SDL2 memory crashes (the C0x5 error indicates memory I think) relating to joysticks but also certain gamepads, seems like my particular joystick is the case.

Luckily I need it for DCS and not Retrobat

Hello, i have the same problem with a new install. Did you find a solution?

Flyingp wrote:Hello, i have the same problem with a new install. Did you find a solution?

Not yet spent some more time investigating today.

Ok, if you find a way to fix this problem, share it here if possible. Thanks

Can you precise both what are your specs ?

Windows 10 Pro 22H2
AMD Ryzen 5 4500U 6 cores
Ram 16 Gb
AMD Radeon Graphics

@polyneux
Can you precise which controllers you use, and precise if there is additional software concerning pad running

getupor wrote:@polyneux
Can you precise which controllers you use, and precise if there is additional software concerning pad running

Win 10. Ryzen 3700x Razer 2070 Super 32g ram.

8bitdo SNES Bluetooth...sn30? I'm away from the machine right now.

I do have a Razer Tartarus and a t16000 plugged in that would describe the other entries in the log.

Maybe I should try it with nothing plugged in.

getupor wrote:@polyneux
Can you precise which controllers you use, and precise if there is additional software concerning pad running

Though I should say I don't precisely think the controller is a factor. Sometimes everything works correctly (once) and then doesn't, that I changed a controller I think might have been a red herring.

I have two other machines one with 4.02 still and one with none on to try also

As there is a lot of change in-between (most representative are Retroarch, and SDL), it's hard to compare and point directly who is guilty. And we don't get enough background yet.
Can you, as you mention, try without nothing connected, and navigate with keyboard (when you can, for sure)

As -1,073,741,819 is an InvalidOperation exception (0xc0000005 - generally an access to a null pointer ), it should be logged in windows application logs as an error, and this should indicate the failing module in the details.
Can you provide windows logs details ?

@f.caruso @getupor @Flyingp

With Caruso and Getupor's powers combined I have found some kind of solution. See the edits on my OP

Tl;DR It was my flight simulation joystick causing the error. Unplugging it stops the problem. Posted Windows App logs in the OP

Ok, then it's related to SDL2.DLL 2.24

We're currently working to integrate 2.26. Can you try with 2.26 version and tell us if it's ok ? ( simply replace the SDL2.dll with the x86 version downloaded from their site ).

As they changed the way they generate joystick guids... You'll probably be asked to reconfigure controllers, and controller configuration injection may fail with some emulators with this version, so we're working on it, but it may be intersting to know if it solves your problem

With SDL 2.26.1 it's working as before. To be more clear it's working very well