Forum Replies Created
-
AuthorPosts
-
joyrider3774Participant
you might want to run something like “while true; do date && vcgencmd measure_temp && vcgencmd measure_clock arm && sleep 2; done;” in an ssh terminal when overclocking and running demanding games, if you overclock too high witouth proper cooling and i do not mean heatsinks alone then you might hit the temprature throtlling limit of 80-85 which lowers your cpu frequency and thus speed of the rpi3.
just blindy overclocking withouth checking this with demanding emulators is not that good of an idea.
about heatsinks in my opinion they do not really help, they seem to help but in almost all video’s i saw people don’t wait long enough to reach the temprature threshold. Eventually with heatsinks the same temp will be reached (when you are doing of course the same thing with the pi3) but it just takes a bit longer to reach that threshold.
The best thing is heatsink + fan a heatsink is not very effective without fresh air transported in and hot air transported out.
so the only positive side imo of heatsinks is that it takes more time to reach the same tempratures which depending on the action your doing could have an impact but if doing things like make -j4 when the 4 cpu’s are stressed 100% it doesn’t matter much just takes longer to reach the threshold.
my stock pi3 reaches 79°C while sitting in my picade playing tekken on ppsspp for a while so no small closed case but plently of room surrounding my pi3.
ah well i just wanted to point out it that it might be a good idea to monitor temprature and cpu frequency while overclocking and running demanding games and no 2 rpi3 are the same due to silicon diffrences which make some pi reach higher temps doing the same thing
joyrider3774Participanti have a hard drive (my old ps3 phat 80gig drive) runnig with retropie. Although i did a fairly simple thing.
Basically i first checked if the drive worked (got powered / came out of sleep) correctly with the pi once that was done i created a “roms” folder on the drive with the same subdirectories as the ones that are availible on the sdcards rom folder (~/RetroPie/roms)
then i moved all my roms to that folder on the hard drive (you could do this beforehand as well, i mean not using the pi). One i was sure all my roms were moved / copied to the hard disk i removed the folder on the sdcard and then basically just created a symbolic link to the hard disk. (ln -s path/to/harddisksystemsromfolder originalromfoldername when being in the directory where the subdirectory existed) and then it seems as if the folders exist in the same location on the sd card except they are linking to the roms folder on the hard disk. this seems to work fine for me and i’m not doing it for all systems just a few.you could probably do this for the complete roms folder instead of system per system.
i also edited /etc/fstab to make the harddisk Always mount on the same point, make pi user the owner of the folder (otherwise it was read only access only with me).
that’s what i did but i was lazzy :)
joyrider3774Participantreboot and shutdown time can be bypassed. In older retropie versions it rebooted / shutted down immediatly not saving the gamelists file, so any changes to them (like playcount, meta data from scraper etc) are not saved. They changed this to wait for emulation station to save all gamelists.
but you can easily get the original behaviour without waiting for emulationstation to shutdown and thus not saving the gamelists by adding 2 .sh scripts in the ports folder. in one you set the command sudo poweroff in the other sudo reboot along with the bin/sh or was it bin/bash stuff (have a look at one of the other files in the ports rom folder it’s normally the 1st line i’m talking about)
that’s what i do to reboot / shutdown my system immediatly and whenever i do want gamelists to be saved for example if i ever edit metdata data i just using the normal quiting way using start -> quit otherwise i go to the ports sections and select either one of those scripts
joyrider3774Participantif your still on wheezy not sure what to do if you are on jessie normally you normally also need to da a sudo apt-get update sudo apt-get upgrade to update your firmware and update retropie using the retropie-setup script. I believe update retroie pie script and then install from binaries.
however i was still on wheezy and using retropie 1.6 !! so i just downloaded the new retropie 3.6 image and copied over al of my roms en setted up everything from beginning again since i wasn’t sure config’s could be copied without changes.
About save games you’ll have to find out where they are saved (psp / psx / n64 etc think like actually saving ingame not save states) and probably will work again
About save states you’ll also have to find out where they are saved (other emulators) and copy those over.
If for some reason you were using old emulator versions and in the newer versions being used now there have been changes to savestates or save games it is possible if they are not backwards compatible that it won’t work. I have no info on that though and did not try to do this.
My guess is that save states might break quicker then save games (memory card files etc) but not sure if there are changes. if you only have save states it might be a good idea to also make sure you have save games also depening if the system / emulator used these (again think like memory cards used).
i think retroarch emulators show you the location of the save state when you save a save state on the screen, at least it does so with me so for those you can quickly find out where they are saved. Other might be saved in the roms directory or config directory in certain directories all depends on the emulator used though.
you can also install the new retropie 3.6 on a new card already with some of the games where you have save states / save games from and copy everything over and test it before actually doing the upgrade(s) on your old retropie card.
maybe someone else already did this ? but for me i started from scratch to be save
joyrider3774Participanti have the official 7inch screen, but did not test touch inside emulators never used it nor needed it. I did test latest scummvm (1.8) on raspbian on pi2 with the screen attached and touch does not work there. Display works fine for the rest as well, i think i tested it with retropie 3.5 on a Pi2, a PI3 should not be diffrent.
pitft is not the official screen and i think OP was refering to the official one, if not i’m using the official one.
Screen works fine in raspbian as well but you’ll need an updated image or update it yourselve before using it.
joyrider3774Participantjust tested your link in the post above, downloads / works fine here (from belgium)
joyrider3774Participantyou have to watch out with overclocking and the pi3 not because of the usual precautions but because the PI starts throtteling the cpu speed (down) when it reaches 80°C if it reaches 85°C or above it will throttle cpu speed to 600mhz (half of the speed) and i know they are going to let it throttle even lower (in a test firmware they did this already)
the pi3 reaches these tempratues fairly easy with some benchmark tools / cpu stressing tools and i noticed when i was running tekken 3 (actually playing) for a while i had tempratues near 75-80°C this is while the pi3 just sits in my picade so it has more air then in normal closed enclosure.
if you overlock you will reach 80-85°C and you will have lower speed then when you would not reach those temps. It happend with me with ppsspp, did not test other emulators but i guess it could happen with N64 depending on the game as well. this was wit a bit of overlocking as well as turbo mode etc, but it depends on the game and if the pi struggles with the game or not.
Using heatsinks probably doesn’t help much (it will make it go slower to those tempratrues and might give you 0-2°C diffrence, but if you are stressing the cpu it will reach those temps eventually) unless your also using a fan to blow cool air through the heatsink that probably helps a lot at least a lot more than just using a heatsink.
I created a simple script to show me the tempratures as well as the cpu speed in a loop. It’s based on code i found in retropie’s (login details info) script.
basically you put this in a file and chmod the file with for exmaple chmod 777 filename
then you can execute it.
The way you should execute it is by opening an ssh connection and let it run there and then start testing playing games / overlocking etc. you can then easilly see the cpu throttling if it eaches those temps, you exit the script by pressing ctrl+c
edit: if you want to see it reach those tempratures and throtteling sudo apt-get install stress (i think it was stress) and then run it with stress -c 4 that will use 4 threads to keep the cpu busy and with my pi3 i can easily reach those temps then
#!/bin/bash function cputemp() { local cpuTempC local cpuTempF local gpuTempC local gpuTempF if [[ -f "/sys/class/thermal/thermal_zone0/temp" ]]; then cpuTempC=$(($(cat /sys/class/thermal/thermal_zone0/temp)/1000)) && cpuTempF=$((cpuTempC*9/5+32)) fi if [[ -f "/opt/vc/bin/vcgencmd" ]]; then if gpuTempC=$(/opt/vc/bin/vcgencmd measure_temp); then gpuTempC=${gpuTempC:5:2} gpuTempF=$((gpuTempC*9/5+32)) else gpuTempC="" fi cpuFreq=$(/opt/vc/bin/vcgencmd measure_clock arm) fi echo "cpu temp=$cpuTempC°C gpu temp=$gpuTempC°C $cpuFreq" } while true; do cputemp; sleep 2; done;
joyrider3774Participanti’m not certain if it’s valid for usb thumbdrives but there is a setting that you can place in config.txt to give the usb ports their maximum current (1200 instead of 600 i think it was) the setting is the following : max_usb_current=1
i had some problems with harddisk (not thumbdrives) that did not get enough power to boot up or stay booted up that setting “can” help. Also a good power supply is especially needed.
on side note i’m currently using my old ps3 phat 80 drive in an enclosure with my pi and that setting is not needed with this drive it was with 2 other drives i tried.
not sure if it would make a diffrence though but you could try it once.
Also watch out if you overclock and enable that setting it might be your pi becomes unstable while it was not before without that setting. Have read some issues about this but could be it’s a powering problem as well then.
03/12/2016 at 14:24 in reply to: Optimize Emulation station's ram usuage .. It's using 100MB+ on my system #120100joyrider3774Participant[quote=120035]<p abp=”241″>You should have your gpu mem split be at 128MB or more.
[/quote]
any idea as to why it should be 128mb or higher ? I have not noticed any problems (yet). Does it improve performance ? (did not notice it when i tried it out at least not with ppsspp). Emulationstation is also NOT showing a white screen of death with the pixel theme (which is very small compared to some other themes)
joyrider3774Participantdon’t know about changing that but with me all retroarch / libretro emulators exit by pressing the buttons that have been assigned to “select” and “start” at the same time. Have no idea if it’s possible to switch this to just one button
joyrider3774Participantsound worked out of the box, did not have to change anything to make it work. But the sound is very very choppy probably due to the fact the pi can’t handle it
joyrider3774Participantjust tested it out as well on a raspberry pi 3. on final fantasy xii i was getting 20 fps with frameskip 9 4 cores enabled in core options still very stuttery. Haven’t tried any 2d games yet though, don’t actually know any plus can’t “playtest” all games would need games that can be played without the stylus as i don’t have a mouse attached.
03/11/2016 at 19:53 in reply to: Optimize Emulation station's ram usuage .. It's using 100MB+ on my system #119992joyrider3774ParticipantOkay Did some more testing:
when i booted up my retropie emulation station was using 113 MB of ram. I temporary renamed the roms folder to roms.bak and started emulationstation it was still using 90 MB of ram even though not one single gamelist was loaded and i only saw the retropie section.
Then i ran “pmap -x <PIDofEmulationstation>” this showed me where emulationstation was using the memory for. It seems emulation station is using lots of libs one in particular takes 22MB of ram being “libicudata.so.52.1” i have no idea what this lib is used for though, there are a few chunks of 8188 KB but it says anon so i have no idea where this is comming from.
I guess not much can be done then since removing all roms only freed up about 10 – 20 mb (had uninstalled some themes as well that i did not use, no idea if this has an impact)
pi@retropie:~ $ pmap -x 4991 4991: ./emulationstation Address Kbytes RSS Dirty Mode Mapping 00010000 3360 3136 0 r-x-- emulationstation 00367000 244 244 12 rw--- emulationstation 003a4000 4 4 4 rw--- [ anon ] 004ec000 1472 1344 1344 rw--- [ anon ] 71a7f000 516 312 312 rw--- [ anon ] 71b00000 4 0 0 ----- [ anon ] 71b01000 8188 8 8 rw--- [ anon ] 72300000 4 0 0 ----- [ anon ] 72301000 8188 8 8 rw--- [ anon ] 72b00000 4 0 0 ----- [ anon ] 72b01000 8188 8 8 rw--- [ anon ] 73300000 136 44 44 rw--- [ anon ] 73322000 888 0 0 ----- [ anon ] 73445000 4 0 0 ----- [ anon ] 73446000 8188 8 8 rw--- [ anon ] 73cb6000 1572 404 0 r---- locale-archive 73e3f000 48 48 0 r-x-- libudev.so.1.5.0 73e4b000 60 0 0 ----- libudev.so.1.5.0 73e5a000 4 4 4 r---- libudev.so.1.5.0 73e5b000 4 4 4 rw--- libudev.so.1.5.0 73e6a000 24 24 24 rw--- [ anon ] 73e70000 24 24 0 r-x-- libffi.so.6.0.2 73e76000 32 0 0 ----- libffi.so.6.0.2 73e7e000 4 4 4 r---- libffi.so.6.0.2 73e7f000 4 4 4 rw--- libffi.so.6.0.2 73e80000 4 4 4 rw--- [ anon ] 73e81000 52 52 0 r-x-- libgpg-error.so.0.13.0 73e8e000 60 0 0 ----- libgpg-error.so.0.13.0 73e9d000 4 4 4 r---- libgpg-error.so.0.13.0 73e9e000 4 4 4 rw--- libgpg-error.so.0.13.0 73e9f000 56 56 0 r-x-- libtasn1.so.6.3.2 73ead000 64 0 0 ----- libtasn1.so.6.3.2 73ebd000 4 4 4 r---- libtasn1.so.6.3.2 73ebe000 4 4 4 rw--- libtasn1.so.6.3.2 73ebf000 176 172 0 r-x-- libp11-kit.so.0.0.0 73eeb000 60 0 0 ----- libp11-kit.so.0.0.0 73efa000 20 20 20 r---- libp11-kit.so.0.0.0 73eff000 4 4 4 rw--- libp11-kit.so.0.0.0 73f00000 16 16 0 r-x-- libXdmcp.so.6.0.0 73f04000 28 0 0 ----- libXdmcp.so.6.0.0 73f0b000 4 4 4 rw--- libXdmcp.so.6.0.0 73f0c000 8 8 0 r-x-- libXau.so.6.0.0 73f0e000 28 0 0 ----- libXau.so.6.0.0 73f15000 4 4 4 r---- libXau.so.6.0.0 73f16000 4 4 4 rw--- libXau.so.6.0.0 73f17000 4 4 4 rw--- [ anon ] 73f18000 88 60 0 r-x-- libsasl2.so.2.0.25 73f2e000 60 0 0 ----- libsasl2.so.2.0.25 73f3d000 4 4 4 r---- libsasl2.so.2.0.25 73f3e000 4 4 4 rw--- libsasl2.so.2.0.25 73f3f000 72 64 0 r-x-- libresolv-2.19.so 73f51000 60 0 0 ----- libresolv-2.19.so 73f60000 4 4 4 r---- libresolv-2.19.so 73f61000 4 4 4 rw--- libresolv-2.19.so 73f62000 8 0 0 rw--- [ anon ] 73f64000 8 8 0 r-x-- libkeyutils.so.1.5 73f66000 28 0 0 ----- libkeyutils.so.1.5 73f6d000 4 4 4 r---- libkeyutils.so.1.5 73f6e000 4 4 4 rw--- libkeyutils.so.1.5 73f6f000 32 32 0 r-x-- libkrb5support.so.0.1 73f77000 60 0 0 ----- libkrb5support.so.0.1 73f86000 4 4 4 r---- libkrb5support.so.0.1 73f87000 4 4 4 rw--- libkrb5support.so.0.1 73f88000 4 4 4 rw--- [ anon ] 73f89000 568 64 0 r-x-- libgcrypt.so.20.0.3 74017000 60 0 0 ----- libgcrypt.so.20.0.3 74026000 4 4 4 r---- libgcrypt.so.20.0.3 74027000 16 16 16 rw--- libgcrypt.so.20.0.3 7402b000 4 0 0 rw--- [ anon ] 7402c000 388 64 0 r-x-- libgmp.so.10.2.0 7408d000 60 0 0 ----- libgmp.so.10.2.0 7409c000 4 4 4 r---- libgmp.so.10.2.0 7409d000 4 4 4 rw--- libgmp.so.10.2.0 7409e000 188 180 0 r-x-- libnettle.so.4.7 740cd000 60 0 0 ----- libnettle.so.4.7 740dc000 4 4 4 r---- libnettle.so.4.7 740dd000 4 4 4 rw--- libnettle.so.4.7 740de000 156 64 0 r-x-- libhogweed.so.2.5 74105000 64 0 0 ----- libhogweed.so.2.5 74115000 4 4 4 r---- libhogweed.so.2.5 74116000 4 4 4 rw--- libhogweed.so.2.5 74117000 984 468 0 r-x-- libgnutls-deb0.so.28.41.0 7420d000 64 0 0 ----- libgnutls-deb0.so.28.41.0 7421d000 20 20 20 r---- libgnutls-deb0.so.28.41.0 74222000 8 8 8 rw--- libgnutls-deb0.so.28.41.0 74224000 4 4 4 rw--- [ anon ] 74225000 16 16 0 r-x-- libXfixes.so.3.1.0 74229000 28 0 0 ----- libXfixes.so.3.1.0 74230000 4 4 4 r---- libXfixes.so.3.1.0 74231000 4 4 4 rw--- libXfixes.so.3.1.0 74232000 32 32 0 r-x-- libXrender.so.1.3.0 7423a000 28 0 0 ----- libXrender.so.1.3.0 74241000 4 4 4 r---- libXrender.so.1.3.0 74242000 4 4 4 rw--- libXrender.so.1.3.0 74243000 40 36 0 r-x-- libjbig.so.0 7424d000 60 0 0 ----- libjbig.so.0 7425c000 4 4 4 r---- libjbig.so.0 7425d000 12 12 8 rw--- libjbig.so.0 74260000 120 60 0 r-x-- liblzma.so.5.0.0 7427e000 28 0 0 ----- liblzma.so.5.0.0 74285000 4 4 4 r---- liblzma.so.5.0.0 74286000 4 4 4 rw--- liblzma.so.5.0.0 74287000 268 64 0 r-x-- libjasper.so.1.0.0 742ca000 60 0 0 ----- libjasper.so.1.0.0 742d9000 4 4 4 r---- libjasper.so.1.0.0 742da000 12 12 12 rw--- libjasper.so.1.0.0 742dd000 28 4 4 rw--- [ anon ] 742e4000 200 60 0 r-x-- libjpeg.so.8.4.0 74316000 60 0 0 ----- libjpeg.so.8.4.0 74325000 4 4 4 r---- libjpeg.so.8.4.0 74326000 4 4 4 rw--- libjpeg.so.8.4.0 74327000 4 4 0 r-x-- libboost_atomic.so.1.55.0 74328000 60 0 0 ----- libboost_atomic.so.1.55.0 74337000 4 4 4 r---- libboost_atomic.so.1.55.0 74338000 4 4 4 rw--- libboost_atomic.so.1.55.0 74339000 88 64 0 r-x-- libxcb.so.1.1.0 7434f000 28 0 0 ----- libxcb.so.1.1.0 74356000 4 4 4 r---- libxcb.so.1.1.0 74357000 4 4 4 rw--- libxcb.so.1.1.0 74358000 12 12 0 r-x-- libuuid.so.1.3.0 7435b000 60 0 0 ----- libuuid.so.1.3.0 7436a000 4 4 4 r---- libuuid.so.1.3.0 7436b000 4 4 4 rw--- libuuid.so.1.3.0 7436c000 36 36 0 r-x-- libvcos.so 74375000 64 0 0 ----- libvcos.so 74385000 4 4 4 rw--- libvcos.so 74386000 20 20 0 r-x-- libvchiq_arm.so 7438b000 64 0 0 ----- libvchiq_arm.so 7439b000 4 4 4 rw--- libvchiq_arm.so 7439c000 264 64 0 r-x-- libldap_r-2.4.so.2.10.3 743de000 60 0 0 ----- libldap_r-2.4.so.2.10.3 743ed000 4 4 4 r---- libldap_r-2.4.so.2.10.3 743ee000 4 4 4 rw--- libldap_r-2.4.so.2.10.3 743ef000 4 0 0 rw--- [ anon ] 743f0000 40 40 0 r-x-- liblber-2.4.so.2.10.3 743fa000 64 0 0 ----- liblber-2.4.so.2.10.3 7440a000 4 4 4 r---- liblber-2.4.so.2.10.3 7440b000 4 4 4 rw--- liblber-2.4.so.2.10.3 7440c000 8 8 0 r-x-- libcom_err.so.2.1 7440e000 60 0 0 ----- libcom_err.so.2.1 7441d000 4 4 4 r---- libcom_err.so.2.1 7441e000 4 4 4 rw--- libcom_err.so.2.1 7441f000 172 60 0 r-x-- libk5crypto.so.3.1 7444a000 64 0 0 ----- libk5crypto.so.3.1 7445a000 4 4 4 r---- libk5crypto.so.3.1 7445b000 4 4 4 rw--- libk5crypto.so.3.1 7445c000 4 0 0 rw--- [ anon ] 7445d000 628 132 0 r-x-- libkrb5.so.3.3 744fa000 60 0 0 ----- libkrb5.so.3.3 74509000 24 24 24 r---- libkrb5.so.3.3 7450f000 8 8 8 rw--- libkrb5.so.3.3 74511000 224 64 0 r-x-- libgssapi_krb5.so.2.2 74549000 64 0 0 ----- libgssapi_krb5.so.2.2 74559000 4 4 4 r---- libgssapi_krb5.so.2.2 7455a000 4 4 4 rw--- libgssapi_krb5.so.2.2 7455b000 1296 1160 0 r-x-- libcrypto.so.1.0.0 7469f000 64 0 0 ----- libcrypto.so.1.0.0 746af000 52 52 52 r---- libcrypto.so.1.0.0 746bc000 32 32 32 rw--- libcrypto.so.1.0.0 746c4000 16 12 12 rw--- [ anon ] 746c8000 272 176 0 r-x-- libssl.so.1.0.0 7470c000 60 0 0 ----- libssl.so.1.0.0 7471b000 8 8 8 r---- libssl.so.1.0.0 7471d000 16 16 16 rw--- libssl.so.1.0.0 74721000 128 60 0 r-x-- libssh2.so.1.0.1 74741000 4 4 4 r---- libssh2.so.1.0.1 74742000 4 4 4 rw--- libssh2.so.1.0.1 74743000 92 60 0 r-x-- librtmp.so.1 7475a000 64 0 0 ----- librtmp.so.1 7476a000 4 4 4 r---- librtmp.so.1 7476b000 4 4 4 rw--- librtmp.so.1 7476c000 188 60 0 r-x-- libidn.so.11.6.12 7479b000 32 0 0 ----- libidn.so.11.6.12 747a3000 4 4 4 r---- libidn.so.11.6.12 747a4000 4 4 4 rw--- libidn.so.11.6.12 747a5000 16 12 0 r-x-- libXxf86vm.so.1.0.0 747a9000 28 0 0 ----- libXxf86vm.so.1.0.0 747b0000 4 4 4 r---- libXxf86vm.so.1.0.0 747b1000 4 4 4 rw--- libXxf86vm.so.1.0.0 747b2000 8 8 0 r-x-- libXss.so.1.0.0 747b4000 28 0 0 ----- libXss.so.1.0.0 747bb000 4 4 4 rw--- libXss.so.1.0.0 747bc000 28 28 0 r-x-- libXrandr.so.2.2.0 747c3000 28 0 0 ----- libXrandr.so.2.2.0 747ca000 4 4 4 r---- libXrandr.so.2.2.0 747cb000 4 4 4 rw--- libXrandr.so.2.2.0 747cc000 48 48 0 r-x-- libXi.so.6.1.0 747d8000 28 0 0 ----- libXi.so.6.1.0 747df000 4 4 4 r---- libXi.so.6.1.0 747e0000 4 4 4 rw--- libXi.so.6.1.0 747e1000 8 8 0 r-x-- libXinerama.so.1.0.0 747e3000 28 0 0 ----- libXinerama.so.1.0.0 747ea000 4 4 4 r---- libXinerama.so.1.0.0 747eb000 4 4 4 rw--- libXinerama.so.1.0.0 747ec000 32 32 0 r-x-- libXcursor.so.1.0.2 747f4000 28 0 0 ----- libXcursor.so.1.0.2 747fb000 4 4 4 r---- libXcursor.so.1.0.2 747fc000 4 4 4 rw--- libXcursor.so.1.0.2 747fd000 8 8 0 r-x-- libdl-2.19.so 747ff000 60 0 0 ----- libdl-2.19.so 7480e000 4 4 4 r---- libdl-2.19.so 7480f000 4 4 4 rw--- libdl-2.19.so 74810000 80 76 0 r-x-- libgomp.so.1.0.0 74824000 64 0 0 ----- libgomp.so.1.0.0 74834000 4 4 4 rw--- libgomp.so.1.0.0 74835000 400 64 0 r-x-- libtiff.so.5.2.0 74899000 64 0 0 ----- libtiff.so.5.2.0 748a9000 4 4 4 r---- libtiff.so.5.2.0 748aa000 8 8 8 rw--- libtiff.so.5.2.0 748ac000 4 0 0 rw--- [ anon ] 748ad000 256 64 0 r-x-- liblcms2.so.2.0.6 748ed000 28 0 0 ----- liblcms2.so.2.0.6 748f4000 4 4 4 r---- liblcms2.so.2.0.6 748f5000 16 16 16 rw--- liblcms2.so.2.0.6 748f9000 340 64 0 r-x-- libraw.so.10.0.0 7494e000 60 0 0 ----- libraw.so.10.0.0 7495d000 16 16 16 r---- libraw.so.10.0.0 74961000 264 68 12 rw--- libraw.so.10.0.0 749a3000 16 16 0 r-x-- libIlmThread.so.6.0.0 749a7000 60 0 0 ----- libIlmThread.so.6.0.0 749b6000 4 4 4 r---- libIlmThread.so.6.0.0 749b7000 4 4 4 rw--- libIlmThread.so.6.0.0 749b8000 76 64 0 r-x-- libIex.so.6.0.0 749cb000 64 0 0 ----- libIex.so.6.0.0 749db000 8 8 8 r---- libIex.so.6.0.0 749dd000 4 4 4 rw--- libIex.so.6.0.0 749de000 264 12 0 r-x-- libHalf.so.6.0.0 74a20000 60 0 0 ----- libHalf.so.6.0.0 74a2f000 4 4 4 r---- libHalf.so.6.0.0 74a30000 4 4 4 rw--- libHalf.so.6.0.0 74a31000 16 16 0 r-x-- libImath.so.6.0.0 74a35000 60 0 0 ----- libImath.so.6.0.0 74a44000 4 4 4 r---- libImath.so.6.0.0 74a45000 4 4 4 rw--- libImath.so.6.0.0 74a46000 620 164 0 r-x-- libIlmImf.so.6.0.0 74ae1000 64 0 0 ----- libIlmImf.so.6.0.0 74af1000 4 4 4 r---- libIlmImf.so.6.0.0 74af2000 4 4 4 rw--- libIlmImf.so.6.0.0 74af3000 4 0 0 rw--- [ anon ] 74af4000 120 60 0 r-x-- libopenjpeg.so.1.5.2 74b12000 60 0 0 ----- libopenjpeg.so.1.5.2 74b21000 4 4 4 r---- libopenjpeg.so.1.5.2 74b22000 4 4 4 rw--- libopenjpeg.so.1.5.2 74b23000 404 64 0 r-x-- libmng.so.1.1.0.10 74b88000 28 0 0 ----- libmng.so.1.1.0.10 74b8f000 12 12 12 rw--- libmng.so.1.1.0.10 74b92000 208 60 0 r-x-- libjpeg.so.62.1.0 74bc6000 60 0 0 ----- libjpeg.so.62.1.0 74bd5000 4 4 4 r---- libjpeg.so.62.1.0 74bd6000 4 4 4 rw--- libjpeg.so.62.1.0 74bd7000 64 0 0 rw--- [ anon ] 74be7000 124 124 0 r-x-- libpng12.so.0.50.0 74c06000 60 0 0 ----- libpng12.so.0.50.0 74c15000 4 4 4 r---- libpng12.so.0.50.0 74c16000 4 4 4 rw--- libpng12.so.0.50.0 74c17000 88 84 0 r-x-- libz.so.1.2.8 74c2d000 60 0 0 ----- libz.so.1.2.8 74c3c000 4 4 4 r---- libz.so.1.2.8 74c3d000 4 4 4 rw--- libz.so.1.2.8 74c3e000 22956 1372 0 r-x-- libicudata.so.52.1 762a9000 64 0 0 ----- libicudata.so.52.1 762b9000 4 4 4 r---- libicudata.so.52.1 762ba000 4 4 4 rw--- libicudata.so.52.1 762bb000 1696 1208 0 r-x-- libicui18n.so.52.1 76463000 64 0 0 ----- libicui18n.so.52.1 76473000 28 28 28 r---- libicui18n.so.52.1 7647a000 4 4 4 rw--- libicui18n.so.52.1 7647b000 1192 900 0 r-x-- libicuuc.so.52.1 765a5000 60 0 0 ----- libicuuc.so.52.1 765b4000 40 40 40 r---- libicuuc.so.52.1 765be000 4 4 4 rw--- libicuuc.so.52.1 765bf000 16 4 4 rw--- [ anon ] 765c3000 24 24 0 r-x-- libboost_chrono.so.1.55.0 765c9000 60 0 0 ----- libboost_chrono.so.1.55.0 765d8000 4 4 4 r---- libboost_chrono.so.1.55.0 765d9000 4 4 4 rw--- libboost_chrono.so.1.55.0 765da000 76 64 0 r-x-- libboost_thread.so.1.55.0 765ed000 60 0 0 ----- libboost_thread.so.1.55.0 765fc000 4 4 4 r---- libboost_thread.so.1.55.0 765fd000 4 4 4 rw--- libboost_thread.so.1.55.0 765fe000 24 24 0 r-x-- librt-2.19.so 76604000 60 0 0 ----- librt-2.19.so 76613000 4 4 4 r---- librt-2.19.so 76614000 4 4 4 rw--- librt-2.19.so 76615000 1196 1060 0 r-x-- libc-2.19.so 76740000 64 0 0 ----- libc-2.19.so 76750000 8 8 8 r---- libc-2.19.so 76752000 4 4 4 rw--- libc-2.19.so 76753000 12 12 12 rw--- [ anon ] 76756000 116 64 0 r-x-- libgcc_s.so.1 76773000 60 0 0 ----- libgcc_s.so.1 76782000 4 4 4 rw--- libgcc_s.so.1 76783000 420 304 0 r-x-- libm-2.19.so 767ec000 64 0 0 ----- libm-2.19.so 767fc000 4 4 4 r---- libm-2.19.so 767fd000 4 4 4 rw--- libm-2.19.so 767fe000 772 768 0 r-x-- libstdc++.so.6.0.20 768bf000 60 0 0 ----- libstdc++.so.6.0.20 768ce000 16 16 16 r---- libstdc++.so.6.0.20 768d2000 8 8 8 rw--- libstdc++.so.6.0.20 768d4000 24 12 12 rw--- [ anon ] 768da000 56 56 0 r-x-- libXext.so.6.4.0 768e8000 60 0 0 ----- libXext.so.6.4.0 768f7000 4 4 4 r---- libXext.so.6.4.0 768f8000 4 4 4 rw--- libXext.so.6.4.0 768f9000 1068 220 0 r-x-- libX11.so.6.3.0 76a04000 28 0 0 ----- libX11.so.6.3.0 76a0b000 4 4 4 r---- libX11.so.6.3.0 76a0c000 12 12 12 rw--- libX11.so.6.3.0 76a0f000 76 64 0 r-x-- libICE.so.6.3.0 76a22000 28 0 0 ----- libICE.so.6.3.0 76a29000 4 4 4 r---- libICE.so.6.3.0 76a2a000 4 4 4 rw--- libICE.so.6.3.0 76a2b000 8 0 0 rw--- [ anon ] 76a2d000 24 24 0 r-x-- libSM.so.6.0.1 76a33000 28 0 0 ----- libSM.so.6.0.1 76a3a000 4 4 4 r---- libSM.so.6.0.1 76a3b000 4 4 4 rw--- libSM.so.6.0.1 76a3c000 80 80 0 r-x-- libGLESv2.so 76a50000 64 0 0 ----- libGLESv2.so 76a60000 4 4 4 rw--- libGLESv2.so 76a61000 160 152 0 r-x-- libEGL.so 76a89000 64 0 0 ----- libEGL.so 76a99000 4 4 4 rw--- libEGL.so 76a9a000 76 72 0 r-x-- libbcm_host.so 76aad000 60 0 0 ----- libbcm_host.so 76abc000 4 4 4 rw--- libbcm_host.so 76abd000 12 12 12 rw--- [ anon ] 76ac0000 792 128 0 r-x-- libasound.so.2.0.0 76b86000 64 0 0 ----- libasound.so.2.0.0 76b96000 12 12 12 r---- libasound.so.2.0.0 76b99000 4 4 4 rw--- libasound.so.2.0.0 76b9a000 376 284 0 r-x-- libcurl.so.4.3.0 76bf8000 60 0 0 ----- libcurl.so.4.3.0 76c07000 8 8 8 r---- libcurl.so.4.3.0 76c09000 4 4 4 rw--- libcurl.so.4.3.0 76c0a000 80 80 0 r-x-- libpthread-2.19.so 76c1e000 64 0 0 ----- libpthread-2.19.so 76c2e000 4 4 4 r---- libpthread-2.19.so 76c2f000 4 4 4 rw--- libpthread-2.19.so 76c30000 8 4 4 rw--- [ anon ] 76c32000 800 660 0 r-x-- libSDL2-2.0.so.0.4.0 76cfa000 64 0 0 ----- libSDL2-2.0.so.0.4.0 76d0a000 8 8 8 r---- libSDL2-2.0.so.0.4.0 76d0c000 16 16 16 rw--- libSDL2-2.0.so.0.4.0 76d10000 8 8 8 rw--- [ anon ] 76d12000 536 468 0 r-x-- libfreeimage-3.15.4.so 76d98000 64 0 0 ----- libfreeimage-3.15.4.so 76da8000 4 4 4 r---- libfreeimage-3.15.4.so 76da9000 24 24 24 rw--- libfreeimage-3.15.4.so 76daf000 528 520 0 r-x-- libfreetype.so.6.12.0 76e33000 60 0 0 ----- libfreetype.so.6.12.0 76e42000 16 16 16 r---- libfreetype.so.6.12.0 76e46000 4 4 4 rw--- libfreetype.so.6.12.0 76e47000 760 728 0 r-x-- libboost_locale.so.1.55.0 76f05000 60 0 0 ----- libboost_locale.so.1.55.0 76f14000 12 12 12 r---- libboost_locale.so.1.55.0 76f17000 8 8 8 rw--- libboost_locale.so.1.55.0 76f19000 56 56 0 r-x-- libboost_date_time.so.1.55.0 76f27000 60 0 0 ----- libboost_date_time.so.1.55.0 76f36000 4 4 4 r---- libboost_date_time.so.1.55.0 76f37000 4 4 4 rw--- libboost_date_time.so.1.55.0 76f38000 80 80 0 r-x-- libboost_filesystem.so.1.55.0 76f4c000 60 0 0 ----- libboost_filesystem.so.1.55.0 76f5b000 4 4 4 r---- libboost_filesystem.so.1.55.0 76f5c000 4 4 4 rw--- libboost_filesystem.so.1.55.0 76f5d000 8 8 0 r-x-- libboost_system.so.1.55.0 76f5f000 60 0 0 ----- libboost_system.so.1.55.0 76f6e000 4 4 4 r---- libboost_system.so.1.55.0 76f6f000 4 4 4 rw--- libboost_system.so.1.55.0 76f76000 28 28 0 r--s- gconv-modules.cache 76f7d000 4 4 4 rw--- [ anon ] 76f7e000 128 128 0 r-x-- ld-2.19.so 76f9e000 60 60 60 rw--- [ anon ] 76fad000 4 4 4 r---- ld-2.19.so 76fae000 4 4 4 rw--- ld-2.19.so 7e7e3000 132 44 44 rw--- [ stack ] 7eaa0000 4 0 0 r-x-- [ anon ] 7eaa1000 4 0 0 r---- [ anon ] 7eaa2000 4 4 0 r-x-- [ anon ] ffff0000 4 0 0 r-x-- [ anon ] -------- ------- ------- ------- total kB 91680 21208 3004
joyrider3774Participantyeah i’ve been using putty a well without a problem on windows 10
joyrider3774Participanti also have no issues using 32x on my picade, everything seems to run smooth but haven’t figured out how to display fps yet. Have not searched for enabling the quick menu in retroarch (if the 32x is retrarch based). I only quickly tested it though like that sonice game and mk2.
joyrider3774Participantthink it should be ./giana instead of just giana (last line) and perhaps you could try using an absolute path not sure about the cd error. Rather weird that it does not work in emulation station.
hmm one more thing i can think of is that emulation station is logged in with a diffrent user hence not finding the directory? using an absolute path should fix it then though. Although i always thought there was just one user, just don’t know if emulation station is started as the user pi
joyrider3774Participantfound some settings that more or less make tekken 6 work although far from perfect. created a little video of it showing the settings as well. I guess it’s more or less playable like this although on certain stages there are slowdowns the one with those fountains / lights.
Sorry for the bad quality it’s done with my Phone and wasn’t easy to film the picade using my Phone
i guess some people want to play it like this.
Street fighter alpha 3 is the only game i came across yet that works full speed without frameskip it’s also in the video a bit
the settings in the video do not really work well for other games though well i’m not sure if it’s the settings or the emulation itselve causing the glitches.
joyrider3774Participant[quote=119600]<p abp=”799″>I’ve tried everything, configure in emulationstation only keyboard, only pad, first keyboard and then pad and viceverse, and no work.
<p abp=”800″>It seems that both keyboard and pad are retropad 1. So what I need is that my pad was retropad 2.
[/quote]
this is what i have in my retroarch.cfg for my gamepad (ps3 one) and keyboard. Basically i switched my keyboard to be joystick index 0 (first pad) and my keyboard to be joystick index 1 (second pad) the rest of the confiruation needs to be done in mame itselve using tab / escape en assignments to buttons
input_player1_joypad_index = "1" input_player1_a = shift input_player1_b = z input_player1_y = alt input_player1_x = ctrl input_player1_start = s input_player1_select = c input_player1_l = space input_player1_r = x input_player1_left = left input_player1_right = right input_player1_up = up input_player1_down = down # input_player1_l2 = # input_player1_r2 = # input_player1_l3 = # input_player1_r3 = input_player2_joypad_index = "0" input_player2_analog_dpad_mode = "1" input_player2_b_btn = "3" input_player2_y_btn = "1" input_player2_select_btn = "8" input_player2_start_btn = "9" input_player2_a_btn = "0" input_player2_x_btn = "2" input_player2_l_btn = "4" input_player2_r_btn = "5" input_player2_l2_btn = "6" input_player2_r2_btn = "7" input_player2_l3_btn = "10" input_player2_r3_btn = "11" input_player2_l_x_plus_axis = "+0" input_player2_l_x_minus_axis = "-0" input_player2_l_y_plus_axis = "+1" input_player2_l_y_minus_axis = "-1" input_player2_r_x_plus_axis = "+2" input_player2_r_x_minus_axis = "-2" input_player2_r_y_plus_axis = "+3" input_player2_r_y_minus_axis = "-3"
joyrider3774Participantbtw had to dig up the thread on the arhcive.org since gp32x seems to be down / not exist anymore. I’m talking about these profiling options with gcc / g++ 4.XX
not sure if anyone with a pi ever tried that, it won’t magically run full speed all of a sudden but would be nice if gcc / g++ on the pi supports it to see if it makes a diffrence
joyrider3774Participantyou have to press esc and then goto the controller options and (re)assign your controls (specifically for ppsspp)
joyrider3774Participanttboheeren try ppsspp not lr-ppsspp it’s wee bit faster.
labelwhore yeah i guess it’s subjective, problem is some games seem to start ok but after a while or later in the game’s progress speed crumbles for example with star ocean 2 if you just quickly start everything seems to be running full speed until you can first control your character then you notice the frame drops (a lot) can’t remeber how much but i do remeber the number on the 1st town it was at 12 – 15 fps and i had frameskipt set to 3 and 4 once (which the pi could not held steady) 60/4 = 15 fps 60/3 = 20 fps so 100% at those frameskips so in order i to make it playable i would need to have it set to at least 5 or perhaps 6 to be safe. Which is way to much to my liking frameskip 1 i can live with (constant 30 fps) for 100% speed but even that is not reachable in all games. I do understand though that a lot of it depends on the game and even where you at (progression) in the game.
I might try messing around some more with self building the binaries and trying out perhaps profiling options (if they even work) of gcc / g++ i used those when i ported emulators (not ppsspp but things like sms-sdl gnuboy etc) to the dingoo and canoo in the old days and i do remeber that helped a fair bit 1-3 fps on a system with much lower specs then the pi although i don’t know if it’s actually the cpu or gpu that can’t handle it, my guess is gpu since when i looked at htop not all 4 cores where at 100% actually far from it when running a game
joyrider3774Participantprobably in 6-10 years or so with PI version 9 or 10 ;)
joyrider3774Participanthtop shows cpu usage per core as well (sudo apt-get install htop) although if i remeber correctly not per proces not sure though but cpu load on the cores is visible
joyrider3774Participanteven mortal kombat 2 3 and umk3 are very playable with lr-mame2003 couldn’t try it before though since i had retropie 1.6 with only mame4all set up before i upgraded to retropie 3.6 with a pi3 now i use both mame4all and lr-mame2003 so i only see the diffrence from pi model b+ to pi3 although i do have a pi2 and one of the things i want to see is how psp ran on the pi2 since (at least for me) it’s not impressive on the pi3 had expected more. But comming from my 1.6 model b+ picade setup to retropie 3.6 pi3 does make a (huge) diffrence for other roms / emulators and i like lr-mame2003 as well it has nice speeds as well lr-mame2010 on the other hand does not but that’s probably because it’s a newer, haven tried the current mame versions from experimental but i doubt it’ll run decent.
Will try to switch my sd card from picade to my pi 2 once and compare a few emulators. i’m wondering about the differences myselve
joyrider3774Participantbecause i’m not certain it will speed things up and i just had everything said up (sd card is full) on my sd card so not willing to do everything again from scratch although i could probably make a new image from the 32gig sd card and use that image to put on my harddisk. Anothear reason is that i had just copied all my psp iso’s to the disk and applying the disk immage to the harddisk means i’ll have to copy them all over again and it did take up to an hour. So before i go that route i want to be sure it would make a diffrence. I just (still) think the pi3 is not capable of running (all / demaninding) games full speed for psp some will work with frameskip some won’t.
I also noticed using htop that the cpu’s were not fully utilised which makes me believe its the graphics part of the pi that can’t handle it
joyrider3774Participanti have done exactly the same thing and that works without a problem.. my picade (usb keyboard encoder) is set to player 1 and player 2 i using my gamepad it works fine for all retroarch emulators. For mame4all you have to set it up manually using tab config.
I think although not certain withouth looking at my config (can’t check at work atm) is that you need to change / play with input_player1_joypad_index = “0” input_player2_joypad_index = “1” in retroarch.cfg i manually edited that file and it works fine. I can post my file if i come home if you like or you can try and have a look at those joypad indexes but i’m not certain it was that setting
Also in the tab config pressing Select ui button (default enter i think or a certain gamepad button) and the cancel button (default escape) sets the input to none so you can start cleanly to assign a button / direction i think i did that as well for every button where the joypad was also mapped to player 1 i just deleted those (set those to none) and then reassigned the keyboard (only) controls for player 1 for player 2 (gamepad) i did the same also
03/08/2016 at 09:56 in reply to: [Help] Can't delete files off of Pi. Permissions Error Code 3 #119564joyrider3774Participantyou can use rm -rf ./directoryname do watch out it will not ask for confirmation using those settings.
Also i have seen the error and it’s probably due to the fact that some files are created with a user with more rights. You can also try chmod 777 directory or file on the file you can’t delete not sure if it works recursive though but that’s what i did when i could not edit gngeorc file (had same error).
also prefix the commando’s with sudo if you still have problems
joyrider3774Participantin some games you can test the input in their test menu’s (F3 i think is the default key) that’s how i configured the mortal komcat games, you can clearly see which button does what (if you ever played in an arcade) it makes it easier to set it up using TAB Interface
joyrider3774Participantyeah i still have to test more but i already noticed once of the hacks (which said speedup) actually decreased performance when i last tested before going to work. Didn’t had time to test other games yet, cause i seem to be having an input problem as well before i left. for some reason one of my button presses on my picade doesn’t register constantly making acceleration in games like ridge racer and toca race driver 2 not work. Don’t know why though but it did work with my joypad hooked up to the pi. I’m not that concerned about it.
1500mhz on a pi 2 isn’t that like a huge overclock ? i have a pi2 as well did not try yet to boot my sd card in the pi2 to see what the diffrence is like.
I might start with a clean config again when i get home and test each setting individually using savestates on for example star ocean 2 in the town after the 1st (little) fight cause that game out of all the ones i tested had the worst performance. Not sure if it’s a good way to go though settings that work for one game might not work for others and certain games have problems with certain hacks like mediëval resurrect with the timing hack as far as i can remember without testing. It locked up on the main menu well just before the main menu appears if i had that enabled. But would need to check again to be sure if that was actually the setting. It was one of the 1st games, besides tekken that i tested.
Also i’m not certain if this could have an impact on performance but i removed the roms/psp folder and made a symblic link for roms/psp to /media/usb0 i’m not certain but i do not think symbolic links could have a performance impact can it ?
i’ll try y’s series as well to see if there’s a diffrence, i noticed ridge racer 2 was running already a lot better then any other game i tried although could not really test due to the input problem and possibly bugs due to hacks / speedups checked (the road / surroundings was all black).
I’ll post again when i tested more games / played more with the settings
joyrider3774Participantyup running retropie over sd card using samsung evo 32gb class 10 micro sd. My iso’s are on a hard disk.
I don’t know really maybe i’m looking to hard at the fps but fully playable should be running smoothly at 60/60 fps withouth frameskip well that’s fullspeed at least. Pi3 can’t handle that (probably can for certain 2d games) Even frameskip 1-3 is not showing 100% speed in fps counter i can see the percentage going down quite a lot.
So i’m not certain what the problem might be either i’m too focused on the fps counter or others are not ? Later today i’m going to test a few other / older games and see how they perform
joyrider3774Participanti’ve got a rpi3 and retropie 3.6 and i must say i’m not impressed what so ever with the psp speed. I’m using ppsspp not lr-ppsspp which is supposedly faster. I tried messing with all the settings and hacks but none seem to be good working for me. Some do have possitive impact like of course the multhithreading, some speed hacks (i tried all of them).
Games i tried were tekken 6, medievil resurection, star ocean 2. In star ocean 2 even with 4x frameskip the pi3 still doesn’t manage to run it smoothly and even slows down (you have to play it till the guy gets teleported to another world and rescue’s that girl, so after the 1st fight, it gets worse when you get in the girls home town) when you just start the game it looks good at the beginning but just after the first fight the slowdown begins. none of the above games run full speed with my pi3 and need a high frameskip. Sometimes they start off good but quickly become a slow motion mess.
I even made some ppsspp builds myselve with -mtune=cortex-a53 & mcpu=cortext-a53 flags as well as a few other optimasation flags but i did not see any noticeable diffrence (i do see a diffrence between lr-ppsspp and plain ppsspp lr-ppsspp’s performance is far worse although that was noted in the wiki as well).
Could it be that the overlocked rpi2’s with the settings above are faster than a raspberry pi 3 ? Also when it comes to overclocking a raspberry pi 3 i’m not certain if there’s a lot of margin. When i was buildin ppsspp on the pi 3 itselve using 4 cores (there all 4 almost constantly at 100% my pi3 (internal) temprature sensor showed 82 °C !!! so heatsinks will probably be needed if any overclocking might be done.
I also have not tried overlocking the pi3 but by default, by using the raspberry pi config item it says “this pi can’t be overclocked” not sure about specifing settings config.txt though but i’m not keen on trying that when the pi3 gets that hot on stock settings (under full load for a while)
-
AuthorPosts