[petrockblog]

All this information is on the wiki

https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation

[petrockblog]

you updated your retropie-setup script at a point where it was temporarily broken due to a wrongly named file – but this was before the 3.0 image so you are not running with an up to date retropie. I would start from 3.0

You can manually fix this by doing “git pull” in the RetroPie-Setup folder from terminal.

[petrockblog]

If the composite picture is no good and you are sure your cabling quality is ok, then it might just be the screen you have bought. The picture from my pi to old crt via composite is usable.

Have you tried the composite output with any device, or tried the new screen with another device ?

Your question is lacking detail though – you mention nothing regarding cabling, which exact options you have tried etc – so it might be an idea to be more verbose so people can advise and point you in the right direction (and if that direction is a website with a solution, then so be it)

[petrockblog]

actually, you may just be able to put the video in a subfolder in ~/RetroPie/splashscreens/ and it may show up in the retropie-setup splashscreen config

[petrockblog]

you have to manually edit /etc/splashscreen.list and put the path to the video there.

[petrockblog]

I may consider changing the default again – when I initially tested, I didn’t notice major slowdown, but then I didn’t test full screen shaders etc. The reason it is changed is according to the retroarch documentation, perfect sync is not possible with threaded video, and as I didn’t initially notice any performance decrease on the pi2, it got switched.

It’s simple to change of course with the new editor – no need to manually edit files.

[petrockblog]

did you turn off video smoothing and did you try turning on threaded_video ?

you can do this from retropie-setup -> supplementary menu -> Edit RetroPie/RetroArch configurations -> Change common RetroArch options – then choose all/retroarch.cfg

?

[petrockblog]

if you want anyone to help you (especially those involved who put in their free time), it will help not to use language like, whether or not you start the sentence with “i’m thankful but”

[petrockblog]

backup your roms and configurations (if you have changed anything) and start with a fresh retropie image for rpi2

[petrockblog]

did you try passing the width / height resolution parameter to emulationstation as mentioned earlier ?

[petrockblog]

thanks – worth noting rom specific configuration is already supported –

see line ~525

    # if the rom has a custom configuration then append that too
    if [[ -f "$rom.cfg" ]]; then
        conf+="'|'\"$rom.cfg\""
    fi

[petrockblog]

omg, glad to hear that you figured it out!

I will check the solder process to try to enhance it in the future.

[petrockblog]

menu 5 of retropie setup – install individual emulators from binary / source

[petrockblog]

Was fixed a week ago or so.

[petrockblog]

then you probably didn’t update the retropie-setup script first.

[petrockblog]

I’m getting the feeling you perhaps didn’t build it – but thought it would be preinstalled? It is only available in experimental for now.

[petrockblog]

Nope – items in the experimental menu do not come with prebuilt binaries so require building.

[petrockblog]

Not sure what you are asking sorry.

[petrockblog]

libretro – an emulator for the libretro/retroarch system (that uses the retroarch.cfg file)

[petrockblog]

Just once.

All I can say is with my setup, using overscan_scale=1, the framebuffer and emulationstation use the same overscan settings. Without the line, only the console is affected, and emulationstation ignores the settings.

Not sure why it would be different on yours – please post your config – and as pointed out, you need positive numbers to decrease the overscan / add a border.

[petrockblog]

It probably failed to build. It was only added the other day, and although it builds fine for me and herbfargus, it didn’t build for someone else.

Check the logfile and see what the problem is.

[petrockblog]

[quote=105435]
overscan_left / right etc for sure affect ES – I also had overscan issues in ES (the menu button icons ran over the edge of the screen) and used these settings to sort out my overscan – I had to be right up to the screen to get the pixel-perfect settings here’s my config.txt:
[/quote]

Yeh sorry, I should have said, they don’t affect emulationstation unless overscan_scale is set – or at least that’s what I remember reading.

[petrockblog]

the script that gets run on bootup is /etc/init.d/asplashscreen not /etc/asplashscreen as was mentioned.

[petrockblog]

It’s being looked into / worked on (I have a lr-ppsspp but there are problems). As soon as something is ready it will be added.

[petrockblog]

The C64 doesn’t have an ESC button – on Vice, RUN/STOP is mapped to the Rpi Esc key. I guess you need another key to start ?

[petrockblog]

Nothing has changed in retropie relating to that, so it may be firmware / kernel / raspbian related.

Have you tried without Xarcade2Jstick btw ? if the xarcade by default registers as keyboard presses, you can just use it as a keyboard – might work better – also we see where the problem initiates from.

[petrockblog]

This is out of the scope of retropie – but you could request it as a feature for retroarch – https://github.com/libretro/RetroArch – unless the firmware for your input board can be programmed to do it, which would be another option.

[petrockblog]

Not sure what you mean – which rom ? You mean the C64 software you were running or ? From my testing escape works as RUN/STOP – you can also use the on screen keyboard from the controller.

[petrockblog]

Vice isn’t a retroarch emulator and uses its own configuration. retroarch.cfg is unrelated.

[petrockblog]

What do you mean it conflicts ? Have you tried pressing escape ?

[petrockblog]

Glad to hear that you figured it out!

[petrockblog]

what do you have in /opt/retropie/configs/all/retroarch-joypads/ ?

[petrockblog]

the resolution parameter might help the original poster too perhaps.

[petrockblog]

ES has no overscan settings of its own. It has some resolution parameters

See https://github.com/Aloshi/EmulationStation/issues/416

[petrockblog]

you can use the hotkey configuration under supplementary menu – see https://www.petrockblock.com/forums/topic/retro-pie-3-exiting-games/#post-104692

there is no desktop environment installed. startx opens with a terminal at the top left, which is by design. You can install a desktop environment if you need one (this has also been answered before – search the forum for “startx”)

[Author]

Posts