[dankcushions]

memory split has nothing to do with it (or anything much to do with retropie, as the documentation says).

surely if you’ve tested your pi on your pc monitor, then you’ve ruled out the tv/display as your issue?

please look at this thread for all information on this subject: https://www.petrockblock.com/forums/topic/hows-your-input-lag/

[dankcushions]

you didn’t read the thread very well. the issue is with raspian, not retropie. there’s a github issue linked at the end of the thread.

[dankcushions]

read the thread…

[dankcushions]

bluetooth controllers? see https://www.petrockblock.com/forums/topic/regular-freezes-with-raspberry-23/

[dankcushions]

1) the threads about this bluetooth issue are still active over the last day, so why not look in them? dongles apparently work – it’s the onboard which is the problem, which is all in the main thread: https://www.petrockblock.com/forums/topic/regular-freezes-with-raspberry-23/

[dankcushions]

firstly, if you have freezes you shouldn’t be overclocking. take all your overlocks out and see if it still happens. if it still does, it’s probably the bluetooth issue:

Regular freezes with Raspberry 2&3

[dankcushions]

are you talking about a raspberry pi 2 or 3? i’m going to assume you mean a 3, although i played mario kart 64 at 1080p on the 2 in 4 player, although it is fairly choppy on some tracks, and has a lot of sound distortion.

it sounds like yours is already playable at 1080p? i didn’t say it was 100% full speed! right now i’m running it with gles2n64 at 1080p and it is pretty choppy in 4 player but playable, if you don’t mind the sound distortion. in 2 player it only has very minor sound distortion and small amounts of hitches. it seems fine to me.

interestingly, i tried lower resolutions in gles2n64 and it didn’t seem to make any difference. i’m not sure what causes the choppiness there but it’s evidently not the fillrate or CPU (i checked CPU usage throughout and it was pretty low)

[dankcushions]

with help from Buzz, we’ve actually fixed this in the code now :)

https://github.com/libretro/mame2003-libretro/pull/25#event-612809045

so if you don’t mind waiting for about 30 minutes for mame to compile, you could avoid the above instructions by doing a build from source:

1) retropie-setup
2) install individual emulators
3) lr-mame2003
4) from source

[dankcushions]

run retropie-setup, update your script. then run the configuration editor – see https://github.com/retropie/retropie-setup/wiki/Configuration-Editor

the wiki is a bit out of date here, but you want

1 Configure basic libretro emulator options
14 Configure additional options for mame-libretro
1 Aspect Ratio
20 Square

this basically makes all libretro mame games display at 1:1 ‘PAR’ resolution (ie, every pixel is treated as a square), which fixes your issue with vertical games. I think this should probably be the default for mame libretro, but really we should fix the core so it renders these games properly…

[dankcushions]

try other isos, but it seems just a general problem with the emulators that you’d need to take up with them. possibly related to https://github.com/notaz/pcsx_rearmed/issues/25

[dankcushions]

i think all discussion here should be moved to the relevant issue against raspian:

https://github.com/raspberrypi/linux/issues/1360

essentially, onboard bluetooth is not stable on the raspberry pi3

[dankcushions]

fyi it works fine in lr-mame2003.

[dankcushions]

[quote=122185]Now we are almost up to date, so maybe time for questions if people are struggling with the same issues as me. First one, space invaders does not keep my high scores. After looking around there seem to be two options, either install the hiscore.dat file (which might or might not require me to rebuild retropie which is way beyond me right now) or the easier option seems to be to set autosave on so that the state is saved when I exit. I can do this on the PC by transferring the files, but if I was to try to edit a file on the Pi using my keyboard, how would I do that?

[/quote]
to edit a text file you go to to the command line and type
nano /directory/whatever/filename.whatever
then it opens a text editor. it’s ctrl + x to exit and save.

to enable autosave you need to ensure

savestate_auto_save = true
savestate_auto_load = true

are in the relevant retroarch config file, but without knowing what exact mame emulator you’re running (and if it’s even a libretro/retroarch one), i can’t tell you where that would be.

also, you don’t need to rebuild your retropie to enable hiscore support, but again it depends on what emulator you are using.

[dankcushions]

i would probably start with doing
apt-get update
and then
apt-get upgrade

the pi3 wifi drivers/configuration was a bit rubbish on the initial release that was used in retropie 3.6.

[dankcushions]

worked for me also! nice work both :) i have an increasingly large .txt doc with all the things i do post install of a new image, and this totally makes it :)

[dankcushions]

seems about full speed but i haven’t tested 4 player. with my pi 2 i was able to run 4 player at 1080p with only a little bit of slowdown using gles2n64, so i might use that for MK64.

[dankcushions]

i suspect your rom zip is incorrect, somehow, then. additionally i’ve no idea why it would be behaving differently in different folders, as aren’t they both using the same emulator (lr-fba-next) by default? what do they say in /tmp/runcommand.log?

you shouldn’t post bios images as they are illegal to distribute, which is why they don’t ship with retropie.

[dankcushions]

no, the only reason to put them in neogeo/ or fba/ is to have them come under the ‘neogeo’ or ‘fba’ menu in emulationstation. either way, the bios and Roms should be in the same folder.

[dankcushions]

https://github.com/retropie/retropie-setup/wiki/runcommand

select the default videomode for mupen64plus-GlideN64 – choose CEA1 (640×480)

[dankcushions]

https://en.m.wikipedia.org/wiki/Shell_script

[dankcushions]

gliden64 is the slowest (but most accurate and compatible) plugin and runs at your displays resolution by default which no pi GPU can cope with. change the display mode to CEA1 for n64 using the runcommand menu.

[dankcushions]

do you have neogeo.zip in your /fba/ folder? i personally run neogeo roms on lr-fba-next via the /neogeo/ folder.

i have neogeo.zip in my /neogeo/ folder. other than that i don’t know what i’m doing differently, but shock troopers 2nd squad works fine here.

[dankcushions]

cute! what does it sound like??

it seems to me like the pi range would really suit a metal case that directly touches the heatsink with a heatpipe, using the the case itself as a large heatsink, just like the various phones and stuff that use similar ARM chips do. the problem with a lot of cases is that they just hotbox the poor thing.

[dankcushions]

both of these are retroarch issues IMO. although i suppose cloud syncing could perhaps be achieved by scripts at the retropie side. i SWEAR i saw someone on either the retropie or retroarch side talking about achieving this very thing recently, but i can’t find it :(

i did find this, though: https://github.com/libretro/RetroArch/issues/2028

[dankcushions]

easiest way is to follow the project on github. that way you see all the updates that come in, and you can make the call to see if it’s worth updating.

https://github.com/retropie/retropie-setup/

[dankcushions]

samples are supported in lr-fba-next in /roms/fba/samples/xyz.zip

see https://github.com/libretro/libretro-fba/issues/60

[dankcushions]

you should run
apt-get update
apt-get upgrade
after install. wifi is busted on the 3.6 raspian release.

[dankcushions]

i’m interested in what the GPU overclocks yield. the pi2 had a strange relationship with the GPU and core (L2 cache) clock speed, but i’m not sure how it is the pi3. you can also clock the v3d speed separately, but again, there were ratios involved. it wasn’t always as simple as ‘make it higher. see http://elinux.org/RPiconfig#Clocks_relationship and http://linuxonflash.blogspot.co.uk/2015/02/a-look-at-raspberry-pi-2-performance.html and

dreamcast, n64 and ppsspp don’t max the pi3 CPU at standard clock speeds so i don’t see any sort of CPU overclocking helping that sort of emulation on the pi3, but it depends on the various relationships at play.

[dankcushions]

/var/log/syslog ?

[dankcushions]

you can set up overlays on a per core basis by adding the overlay configuration to:
/opt/retropie/configs/SYSTEMNAME/retroarch.cfg

you can set up overlays on a per-game basis by adding the overlay configuration to
/home/pi/RetroPie/roms/SYSTEMNAME/gamename.zip.cfg (not all systems used zipped game files, but you get the idea)

the actual overlay configuration would depend on your overlay image, location, resolution, etc.

In regards to objective 2 I understand that MAME4ALL is likely the most reliable source of ROMS on retro pie (I had previous problems getting Mame Roms to work at all). With this in mind I believe those overlays in objective 2 have been created to use Retroarch (Liberto not Mame4all). Is there a way to get them working with Mame4all?

the link objective 2 already has the config files needed included in the zip, but they’re likely for current libretro mame, not the older version we use (lr-mame2003). i imagine the config would be the same but something to consider…

also, i don’t agree mame4all is the most reliable (limited rom set), although it is good if you only have a pi1, i suppose. if you want to use overlays you will need to use the libretro version of it (lr-imame4all), in any case. the other version of mame4all is not libretro and and does not support overlays.

[dankcushions]

sounds like your initial issue is this bluetooth one: https://www.petrockblock.com/forums/topic/everything-crashes-after-about-5-mins/#post-121818

as for the pi2, i wouldn’t start playing with overclocking until you have a system that does not crash. overclocking does not increase system stability…

[dankcushions]

it’s all on the link..

https://github.com/raspberrypi/linux/issues/1360

looks like we need someone to provide a full log of the issue

[dankcushions]

interesting about the different NES cores having slightly different latency. i will make nestopia my default, now.

i also wonder if raspian can be run in KMS mode? if so, perhaps retropie could, in the pre-built images?

again i think there’s further testing worth doing regarding vsync, input drivers, display drivers, etc.

[dankcushions]

which roms? are the compatible with the version of FBA? see the fba compatibility spreadsheets on the wiki.

[dankcushions]

the libretro version of mupen64plus just has one entry on the runcommand menu – you have to set plugins on this one up using the internal retroarch GUI (select+X) and go to quick menu > core options.

however you probably shouldn’t be running the libretro version (out of date, worse performance). choose the standalone version for each plugin via the runcommand.

[Author]

Posts