Most consoles emulators games are now slow, help please !!

mediamogul

Also, everyone is operating on a certain amount of guesswork here. Please always remember to post as much information about your setup as possible. The necessary information is detailed at https://retropie.org.uk/forum/topic/3/read-this-first.

darthlink

@TMNTturtlguy said in Most consoles emulators games are now slow, help please !!:

As for overclock @darthlink i assume you have a pi3, if you read the documents, overclocking through the menu is not supported. that is why you are getting the error. Read on how to manually overclock. I suggest you avoid any overclock setting until you figure out what is wrong with your system.

Actually i dont really want to overclock, i was just curious to see it through the menu.

Right now, i just would like to have everything working great before i make a third backup of my pi. It is almost at exactly the point on where i would like it to be ( althought i may still make changes in the futur ) loll . It does not look like it ( because i dont know enough linux commands ) but i am a computer tech loll still thx for all your help, you guys are awesome ;)

dankcushions

@TMNTturtlguy said in Most consoles emulators games are now slow, help please !!:

what is shown is just the memory split that is set through the retropie menu. All this is doing is telling the retropie to always use 256, it basically just overrides gpu_mem_256=128 and forces it to use 256.

pedants' corner: it doesn't override anything since the rest are commented out :)

if they weren't, on a pi3 gpu_mem_1024 would override gpu_mem. see http://elinux.org/RPiconfig

so, as far as i can tell

gpu_mem=256
#gpu_mem_256=128
#gpu_mem_512=256
#gpu_mem_1024=256

and

gpu_mem=256
gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=256

and

gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=256

would all give a gpu memory split of 256MB on a pi3.

/pedants' corner :)

but yeah, either way the change seems pointless.

TMNTturtlguy

@dankcushions Just for my own clarity, and maybe because of my poor communication skills above, when you set a gpu_mem= setting of any amount, it will comment out all of the standard settings, meaning they will all be ignored and everything will run at your new setting. In this case everything will run at gpu_mem=256. So no matter what, you always will run 256......Since the standard settings are 256 for everything except for gpu_mem_256=128, the only thing you are really doing by having this memory split is overriding the 256=128 setting. All other settings are already running at 256 by default anyways. Correct?

dankcushions

@TMNTturtlguy said in Most consoles emulators games are now slow, help please !!:

@dankcushions Just for my own clarity, and maybe because of my poor communication skills above, when you set a gpu_mem= setting of any amount, it will comment out all of the standard settings, meaning they will all be ignored and everything will run at your new setting.

have you tested this? i mean, if you edit the file (in nano or whatever - not via raspi-config, as who knows what that does! plus i think i gets updated every so often and we might not have the latest), and add gpu_mem=blah, reboot, the system comments out those other lines? if so, you're right and they should update their docs!

In this case everything will run at gpu_mem=256. So no matter what, you always will run 256......Since the standard settings are 256 for everything except for gpu_mem_256=128, the only thing you are really doing by having this memory split is overriding the 256=128 setting. All other settings are already running at 256 by default anyways. Correct?

gpu_mem_256=128 should only ever apply to the original raspberry pi 1 which had 256MB, as far as i understand it. those mem_256/512/1024 settings apply to pis with these respective amounts of RAM.

darthlink

@dankcushions said in Most consoles emulators games are now slow, help please !!:

gpu_mem_256=128

I have a question though, since gpu_mem_256=128 and i want to give 256 to the GPU, does this mean that in the file config.txt i have to set it to 512 in order to have 256 for the GPU because gpu_mem_512=256 ???

TMNTturtlguy

@darthlink No, it means you should leave the settings alone. The gpu override you set wasn't really doing anything, but you don't want to mess with those settings.

darthlink

@TMNTturtlguy

ok thx ;)

Sano

Nope, gpu_mem_xxx defines the GPU memory in relation to the quantity of RAM available.
If the Pi has 256 MB of RAM, then 128 MB are reserved for the GPU.
For 1 GB the GPU memory reservation is 256 MB.

darthlink

@Sano said in Most consoles emulators games are now slow, help please !!:

Nope, gpu_mem_xxx defines the GPU memory in relation to the quantity of RAM available.
If the Pi has 256 MB of RAM, then 128 MB are reserved for the GPU.
For 1 GB the GPU memory reservation is 256 MB.

haaaa ok so since i have the Pi3 and 1GB of RAM, it means that by default it reserve 256MB for the GPU ?

So why is there even a memory split setting ? Just curious ;)

Sano

Exactly.
Once again, we all here use retropie on our RPi, which demands quite an amount of graphic memory.
Imagine you just install a raspbian with only CLI through SSH in order to run a webserver, NAS, domotic, or anything else beside a MediaCenter. Graphic memory would be useless, so you could modify the memory split to allow more RAM to your web server/tomcat/whatever.

darthlink

@Sano

thx ;)

darthlink

I have just transfered 2 psp roms from my network external HDD to my microsd and the result it the same :( I dont know what happened ?? The audio is crapy and game are so slow. i can start them ( little big planet and lego start wars 2 ) but way to slow to be properly playable. I know for a fact that little big planet does work great because i had played when i had at first install lr-ppsspp and it was my first psp rom and it was perfectly ok.

Now the only diference i can think of ( since it is not the HDD the problem ) is that could the installation of drastic may have caused this ? Drastic is the last emulator i have installed and i know that before that, every console games where working properly excep N64 and NDS.

Well from what i have read, nobody as made it possible yet for N64 roms to be playable with retropie yet.

TMNTturtlguy

@darthlink PSP is very hard to run. I am not surprised Leto Star Wars is not running. I can't speak to what happened to little big planet.

Have you tried other emulators to see if they are still running? Nes? Genisis? Do you have a backup of your system from before installing drastic? How about just unisnstalling drastic and seeing what happen? You can always reinstall it.

darthlink

@TMNTturtlguy said in Most consoles emulators games are now slow, help please !!:

@darthlink PSP is very hard to run. I am not surprised Leto Star Wars is not running. I can't speak to what happened to little big planet.

Have you tried other emulators to see if they are still running? Nes? Genisis? Do you have a backup of your system from before installing drastic? How about just unisnstalling drastic and seeing what happen? You can always reinstall it.

I have just uninstall drastic then rebooted and still no improvement :(

Yes i have a backup of my PI but the backup was before i had setup my network external HDD and i had a sort of hard time to set that up so i want to try to not go this way unless i have no other option.

nes does still works ok though but i have not tried genesis. SNES does not work good anymore either. I have not tried them all but they where all working ok not too long ago.

I have to leave now but will comeback later to make more test with yall with your helps. thx again in advance.

darthlink

So beside putting back my previous backup, does anyone have any idear to help me solve that problem please ?

TMNTturtlguy

@darthlink I am afraid there are just to many variables for us to be able to help you with an unknown problem and no other information except poor performance. If you could specify an error code, or specific issue we could trouble shoot, but the fact that all we know is your games started to run slow does not help us much. Before doing a full restore of your last backup, you could try to update all your packages from the retropie startup menu. Also confirm you are using a 2.5A power supply. that is about it all i can help with given the information you have provided.

darthlink

2.5A micro usb power supply: yes
raspberrypi 4.9.24-v7 : with uname -a
256MB : for gpu
error messages: none ( unles in a log file that i dont know of )
uptaded all packages: done
apt-get dist-upgrade : done ( already the newest version)
apt-get update : done
OS: Raspbian with pixel ( installed manually without noob )
emulationstation also installed manually after raspbian with pixel
command: free -h ( mem = 733M total and 562M used and 170M free )
the raspberry pi 3 board is inside the closed black box with 2 heat sink that came with it

darthlink

i have just tested all other emulators ( nes, snes, genesis, mastersystem, playstation, gameboy advance, psp ) i have not tested ( megadrive, game boy color, neo geo, sega 32x, N64 ). i already know that N64 are unplayable yet.

they all worked ok beside PSP witch little big planet is sort of playable, still slow but playable and sound is still crapy and lego star wars is still unplayable. SNES did shut down 1 game that i tested but it may be the rom, i will have to test other game too on snes.

The 2 psp roms where played directly from the microsd since i have copy them there to test earlier

darthlink

i have just manage to copy the log file from /dev/shm/runcommand.log so here it is, hope it can help:

Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-ppsspp/ppsspp_libretro.so --config /opt/retropie/configs/psp/retroarch.cfg "/home/pi/RetroPie/roms/psp/Little_Big_Planet.iso" --appendconfig /dev/shm/retroarch.cfg
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500
glGetError 0x500