[petrockblog]

good spot. this should be fixed as of https://github.com/RetroPie/RetroPie-Setup/commit/1d8482d88f36602ab455faf069263216aa60b3cf

[petrockblog]

did you quit/restart emulationstation?

[petrockblog]

does it make a difference if you remove the quotes from video_shader_enable ?

Can you put the full configurations you have edited somewhere (pastebin or similar)

[petrockblog]

Looks good thanks. Let’s see what they say.

[petrockblog]

There is a +4 emulator already – use the c64 folder, and switch emulator on launch (to vice-xplus4)

[petrockblog]

(drop to terminal on pi, and see if you can ping that address, and try http://www.google.com etc)

[petrockblog]

oh and you will get a blank page on your phone, as it’s a file download area with no website on it (it has a blank page) ;-) but that’s fine – not an error.

[petrockblog]

Impossible to say – problem with your dns ? temporary network problem ?

resolves fine here. can you access it on other machines on lan ? does rebooting help ? How is your pi connected etc. check router config ? turn router off and back on again ? :)

[petrockblog]

Did you read the documentation detailing romset versions linked earlier in this thread ?

[petrockblog]

Lovely :)

[petrockblog]

Not sure what you mean by “There are no kickstarts as it ask for a kickstart?” – please give me details of what kickstart files you have copied where, and the configuration you are using in uae4all – have you been through the configuration screens ?

[petrockblog]

It may be something they changed intentionally, but it will help me to know what we need to change our end.

[petrockblog]

Please work out which commit the behaviour changed and then open a ticket on https://github.com/raspberrypi/firmware with details of the last commit it worked, the one where it broke, and your config.txt (which really just has the overscan_scale=1 set which is related)

[petrockblog]

Did you try the video mode change also I mentioned earlier?

I suspect this could be down to a firmware change – please can you check https://www.petrockblock.com/forums/topic/emulationstation-screen-dont-fit-after-update/ and perhaps try downgrading the firmware / kernel also ?

[petrockblog]

At least it would help confirm if it is firmware or something else config wise which has changed.

[petrockblog]

I believe it is related to a firmware/kernel update as someone else had the problems too.

you can use rpi-update to roll back firmware and find out when it breaks – backup your system first etc.

https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=19415 has some basic instructions on how to do this.

if we can pin it down to a specific update we can report it back to rpi firmware github.

[petrockblog]

Well, up to now, I hadn’t tried out the images. But now I have – and I’m furious.

The rules on this forum are clear. I know you know the rules on the Kodi forum too. Why would you post an image that contains so many plugins that stream copyrighted content etc. This is not a warez forum. What the hell were you thinking.
You threaten this project with such actions – how can you be so stupid.

[edited] no need for my swearing either – but I was pretty shocked to see the contents of the image.

I have found and removed more links to the images – if anyone notices any that have been missed please PM me.

[petrockblog]

RetroPie 3.1 is the latest.

I suspect your kickstart images are bad.. You can run many games from the built in kickstart derived from AROS.

[petrockblog]

not recommended to save config (if you dont understand how it works) – or at least not telling it to save on exit. it will overwrite system specific config. You can edit this file manually via the config editor – try that. You have have messed up some configs now though and should start from a fresh image.

[petrockblog]

The official release is 3.1.

Your probably have bad romsets. I suspect you need to read the Wiki have not read anything on the Wiki.

[petrockblog]

you are also not in the right folder.

[petrockblog]

you don’t have jstest installed. It’s in the Debian “joystick” package.

[petrockblog]

Have you tried no bios / alternative bios files? What’s the md5sum of your bios ? Are you finding all games crash ? I have not heard from others about major problems with compatibility.

[petrockblog]

For the video mode problem (I think it’s the problem) – can you try adding

hdmi_group=1
hdmi_mode=16

to /boot/config.txt

[petrockblog]

Did you use the commandline I provided? – seems to miss lots of logging. Did you just redirect stdout to a file and not stderr or ?

[petrockblog]

to run it manually from cli

/opt/retropie/emulators/retroarch/bin/retroarch --verbose -L /opt/retropie/libretrocores/lr-pcsx-rearmed/libretro.so --config /opt/retropie/configs/psx/retroarch.cfg ~/RetroPie/roms/YOURISO

replacing YOURISO with the ISO file you are using.

to log the output to a file add &>/tmp/logfile.txt

also the outputs of these command might be helpful

contents of /boot/config.txt

and outputs of

tvservice -s
tvservice -m CEA
tvservice -m DMT

[petrockblog]

ok sorry misread –

Maybe there are some upstream changes that break the PSX emulator for that game? anything in /tmp/runcommand.log ?

can you try launching it from terminal – get the commandline from configs/psx/emulators.cfg and add the parameter “–verbose”

Nothing has changed regarding emulationstation that should affect the display – does your system seem to be starting in the same resolution as before? There is a new kernel / firmware etc with this release – it’s possible something changed. You didn’t modify /boot/config.txt ?

[petrockblog]

Also without any logs or configs files it’s impossible to advise.

[petrockblog]

Start from a fresh image? – there is no “automatic” upgrade route from the beta (which one? the first?) releases – well, there is be but you may need to do some manual config merging – sounds like you would be better off just getting the 3.1 image.

[petrockblog]

3) would also be in runcommand since it launches the game, and then does some cleanup code etc.

[petrockblog]

have you tried launching xboxdrv manually with –daemon and then trying the simple script ? are you testing this on the machine itself or via ssh ?

[petrockblog]

Also – did you try launching the ES binary directly ?

[petrockblog]

you probably still have it running in the background – did you check ? Maybe you have multiple copies running now :)

[petrockblog]

In the specific images above – I guess the first, but it depends which platform/resolution etc.

[petrockblog]

on one on my monitors I prefer 1st, and on the other the 2nd ;-) (One monitor looks a lot more blurry than the other).

[Author]

Posts