[ceuse]

Bump after quite some absence (completly reinstalling/reconfiguring after a sd card crash sucks so i took a break). is this bug fixed with beta 4 now? and what are the overall changes :-)

[ceuse]

a push on my github issue would be apreciated then ;-)

[ceuse]

Mh that kinda proves my suspicion. but yeah your right without any theme / gamelist new system should be addable almost unlimitled (although the font/tab itself will cost some graphical power). im betting you though that if you would add gamelists / expand your gamelist.xml files your number of systems would go down.

Its a matter of unoptimised code / handling of the data wich fills the ram with alot of unnececary stuff you wont need/only need later.

i hope they change the behaviour to something Kodi like where the metadata gets loaded after you actually enter the according menue / when you scroll to the specific film.

[ceuse]

[quote=95585]I think I may have found a workaround for this. It’s not pretty but it seems to be working pretty well for me. I need to do a bit more testing and I’ll post here if it turns out to be stable.
[/quote]

I cant wait that long :-( whats the trick

[ceuse]

no idea. the initial post is the normal script where the blackscreen can occure. and the other way around i didnt try out / dont want to since i want to boot into emulationstation first :-)

[ceuse]

Sorry for the delay.

im using the SNSP-005 Controllers . hers my Config for the Controlls in /opt/retropie/configs/all/retroarch.cfg

input_player1_joypad_index = "3"
input_player1_b_btn = "2"
input_player1_y_btn = "3"
input_player1_select_btn = "8"
input_player1_start_btn = "9"
input_player1_up_axis = "-1"
input_player1_down_axis = "+1"
input_player1_left_axis = "-0"
input_player1_right_axis = "+0"
input_player1_a_btn = "1"
input_player1_x_btn = "0"
input_player1_l_btn = "6"
input_player1_r_btn = "7"
input_player2_joypad_index = "2"
input_player2_b_btn = "2"
input_player2_y_btn = "3"
input_player2_select_btn = "8"
input_player2_start_btn = "9"
input_player2_up_axis = "-1"
input_player2_down_axis = "+1"
input_player2_left_axis = "-0"
input_player2_right_axis = "+0"
input_player2_a_btn = "1"
input_player2_x_btn = "0"
input_player2_l_btn = "6"
input_player2_r_btn = "7"
input_enable_hotkey_btn = "8"
input_exit_emulator_btn = "7"
input_save_state_btn = "3"
input_load_state_btn = "0"

I dont think though that your configs are the issue if there infact is something wrong with the drivers. my best guess is use jstest to configure it further (finding out device numbers / if it works at all)

[ceuse]

I think its a issue with the retropie v3 image. im running it sucsessfully on 2.6 and im hesitant to update at the moment.

i will post my retroarch.cfg later if you want ( i use 1 mayflash snes & 1 mayflash n64 adapter with 2 controllers each)

[ceuse]

a Upvode on my Topic or a quick shoutout on my github issue would be apreciated :-) the main problem is that the gamelists are loaded on startup. sadly it seems they dont care/work on it :-(

[ceuse]

Bumpedy..

no python guru arround? :-(

[ceuse]

[quote=94233]Default gamelists are sent here:
/home/pi/.emulationstation/gamelists/{systemname}

If you dont use ES to scrape, the gamelists will often be in the rom dir.
[/quote]

I put them in the Rom dirs. I dont know if they are handled diffrently then the ones in the gamelists folders but i think it shouldt.
Just wanted that info for the sake of completing the information to reproduce the issue :-)

[ceuse]

[quote=94192]ceuse – it’s not completely clear from that issue title etc that it is the same problem, but yeh you have already reported it. Hopefully Aloshi will have more time for emulationstation soon.

it’s also possible the gameslistdb branch will help with this (or not).
[/quote]

I Knew more about the issue when i opend the Git Issue. I think/hope it is more clear on the actualy problem there.
Sadly im not savy enough with Linux to actually collector more Information other then the es_debug log beeing the same when its working or freezing.

i edited the inital post to include the git link so its easier to find

[ceuse]

[quote=94143]You could report the problem upstream to emulationstation perhaps ? Maybe there is something that could be improved in the es code to reduce memory usage etc.[/quote]

How would i do that other then by opening my git issue ? (https://github.com/Aloshi/EmulationStation/issues/423)

[quote=94158]yikes, running into lock ups myself as i added more emu’s over the weekend. running 25 and some white box art is starting to show up with garbled text.

i’ll try taking that down to 20 to see if it still does the same thing.
[/quote]
or just remove some gamelist xmls if you have them scraped and see if that fixes the issue (at least for me it does)

[ceuse]

well it seems though it runs the same command in the end (although checks for other stuff). i checked the kodi.log file while a blackscreen occured and it read (at least on my test) “application stopped”. so i think this one should work.

also it basicly does the same thing in the end :

sudo killall /usr/lib/kodi/kodi.bin

i dont think Kodi itself is the issue but “Waking up” Emulationstation.

i gotta check in my free time again where the script fails. although i just think the problem occures in my own modification (killing emulationstation and starting it again)

[ceuse]

[quote=94090]i thought it’s not about retropie/emulationstation but about raspbmc… i think there’s an issue with kodi in raspbmc… !? hopefully this will get fixed soon. there seems to be a lot of confusion about this topic as well [/quote]

I Think you mean Raspbian ;-)
And thats the context where i found the script above that im unable to get to work :-( but it seems like a easy fix if i just would know how to get emulationstation killed and restarted. It wont fix the source problem but it would be a great workaround i think

[ceuse]

Also it happens no matter if its exit or shut down from the kodi menue.
It only occures after a longer period of time though. as far as i read its because emulationstation enters sleep mode and wont react after kodi is quit.

sooo nobody with a bit of python experience ? :-(

[ceuse]

[quote=93265]
The only problem so far is that Emulationstation goes to sleep when you are watching a movie. When you exit out of kodi you just get a black screen and have to shut down the pi and restart.
[/quote]

If you got a way to fix this i would be glad. im suffering from this problem aswell (or a way to completly reboot the pi out of kodi)

[ceuse]

check your /etc/emulationstation/es_system.cfg file.

For psx the run command reads

<command>/opt/retropie/supplementary/runcommand/runcommand.sh 1 "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/psxlibretro/libretro.so --config /opt/retropie/configs/all/retroarch.cfg --appendconfig /opt/retropie/configs/psx/retroarch.cfg %ROM%" "psxlibretro"</command>

check if yours is difrennt / check the path for the appendconfig and edit those config or fiddle around there in general

[ceuse]

try using retroarch-joyconfig -p 1 -j 0 and retroarch-joyconfig -p2 -j1 (P for player. j for joystick number)

[ceuse]

I have it working and it works fine.
Try jstest /dev/input/js0 & jstest /dev/input/js1 to see if there is any input at all.
also try to switch the 2 controllers on the ports to check if one is broken compleltly or if its just a config issue.

[ceuse]

Sadly i dont got any response on my git issue yet. i hope they will look into this. im hesitant to start again with the new 3.0 image before this behaviour is officially resolved since it really kills the fun if your bound to a specific number of system / roms

[ceuse]

[quote=92860] It doesn’t seem to matter how many roms any of them have in them, from one to a thousand.
[/quote]

Try To add some gamelist.xml files with images to your setup and you should see the number decline from 23. Or just remove some if you allready have some scraped.

[ceuse]

[quote=92818]I think you’re right about the ES behaviour – although I have about 10 systems setup and must be over 10,000 roms referenced (lots of mame versions) and it seems to cope (Pi2) – so maybe the number of emulators displayed is more of a factor.[/quote]
also even with a “broken” emulationstation i still get the same es_log.txt which higly indicates that the complete gamelist.xml files are parsed directly at the startup. Pure Numbers of roms doesnt matter that much, but if you add them to a gamelist.xml file with a picture and description etc then the problem starts

i hope they change that soon / is on the radar since atm i cant add another emulator without breaking my intallation (even with 720p backgrounds)

[ceuse]

Ok you are right. If i lower the Resulution of the background images it works fine when i add another gamelist.xml file.

Although adding a new system with more roms breaks the system again in the known too few ram fassion directly at startup.

Still there must be a MAYOR Ram drain if a single gamelist (which shouldt be affecting the overview and should only be read when entering a specific System).
My tests indicates that at the Moment, emulationstation parses every Gamelist.xml file directly at startup and keeps everything in Memory.

[ceuse]

tried that.

with standart allocation (384) + adding a new gamelist. Error.
Changed allocation to 512 + adding a new (1 Game) gamelist . Same error.

Gonna try to check es_log.txt and then respond
Edit:
ok since the ES Log is almost completly the same (compared working / non working es_log)
Only diffrence (parsing a non existing folder/xml file):

lvl1: 	  Unknown platform for system "kodi" (platform "kodi" from list "kodi")
lvl2: 	Parsing XML file "/home/pi/.emulationstation/gamelists/kodi/gamelist.xml"...

Changes to (actual location of a existing gamelist.xml file)

lvl1: 	  Unknown platform for system "kodi" (platform "kodi" from list "kodi")
lvl2: 	Parsing XML file "/home/pi/RetroPie/roms/kodi/gamelist.xml"...

here some more info / screens on what happens :

before i add a new gamelist.xml everything works fine :

[img]http://i.imgur.com/hUeqJvf.jpg[/img]

after i Add My Kodi Gamelist after i try to enter the emulator :

[img]http://i.imgur.com/xKh6cu9.jpg[/img]

after that it freezes

and heres the es_log if anyone is intrested in the full Log

es_log.txt

and heres the xml i try to add

gamelist.xml

To summarize : I add a new gamelist to emulationstation – everything works fine while i dont enter a System.
After i enter a (random) System this above happens and the system freezes.

[ceuse]

bump.. is there anyway to turn on debug mode / collect logs from emulationstation?

[ceuse]

ok i (at least) got the no bios error msg now..

adding system_directory = “/home/pi/RetroPie/BIOS/psx” (and creating a seperate folder) removed the message no bios found, but i still get a segmentationfault when i try to load a savestate and progress in the game
… ok it seems that the loadsate wont work if you switch bios in between.

i (think) its working now

[ceuse]

well i ran into the same error on both my old rpi b with emulationstation 2.1 i think and now with rpi2 and 2.6 installation with the same amount of roms/gamelist.xmls.. i dont really want to start fresh since its working perfectly as long as i dont add a new gamelist.xml file (or another game to a existing gamelist.xml).

i gotta test it out some more by adding more/diffrent games to my gamelist.xml files..

i just thought of something. could it be a encoding problem since i edit it on notepad++ on windows (i use utf8 without bom)

[ceuse]

well it still happend after multiple reboots though :-( im truely at a loss & have no idea how to narrow / log the issue

[ceuse]

just tried to edit a gamelist.xml to add a new game and (almost) had the same error again.

although it only happend after a few browsing, the whole system froze again. not even keyboard input (like f4 etc) would work. after i removed the entry from the gamelist it works again.

something about the gamelist.xml handling seems seriously broken.

[ceuse]

bumpedy.. anybody got an idea.. :-(

[ceuse]

Ok news about this issue :

today i added a gamelist.xml for my kodi roms folder. it worked quite well. After that i noticed that my gb and gbc gamelist.xml were broken. after i reuploaeded those to my pi. the error occured again (white line on top. unresponsive right at startup).

even removing both the gamelist.xml files from gb and gbc wouldt fix the issue. only when i removed the gamelist.xml file for my kodi installation (wich worked prior to the gb and gbc fix) it starts working again

Any ideas how a (even corrupted) xml file can break emulationstation at startup?

I added the xml in question as an attachment since it seems the forum eats my post as soon as i add xml stuff

[ceuse]

Thanks man ! your Kodi.svg really saved me. couldt get a decent one working :-)

[ceuse]

no im still at standart. but can that really be the problem?

as said i had the same problems with the rpi B where mem is set to 256 and now with rpi2 its set to 384 and still the same problem.

also i added n64 again and removed turbograph x16 and its working (even though n64 shows twice now since i have a rom in the n64-rice folder).

I think there might be a hardcap on overall roms/systems (since i have the complete libary on most of my systems).

anyone has an idea how to bugfix / log the issue? as said it freezes directly at startup with half of the gui lodaded

[ceuse]

yeah i thought that aswell. since i ran into the exect same problem on both the pi B and now the Pi2 (both time on 12 emulators).

so im pretty much ruling out a ram issue

[ceuse]

they closed the issue. anyone got any further with this?

[Author]

Posts