My suggestion would be to use the RetroPie image directly and not through BerryBoot.

@mitu yes

@telmocamargo said in Error on resolution - Desktop Version:

16:9 wide NO

This option seems to be fine for the resolution - are you using it as the current option or did you toggle widescreen on ?
When using a desktop environment, like on a PC, you can use xrandr to adjust the overscan:
https://askubuntu.com/questions/508358/overscanning-picture-problem-using-hdmi-with-intel-graphics.

You can stream to twitch via RetroArch - see here or here on how to configure streaming.

On a PC (Ubuntu & forks, Debian, etc.), EmulationStation should be started from a desktop environment, not from a terminal.

@sirhenrythe5th I completely agree! Needless to say we are very disappointed, but doing our best to make it work. And yes, I would LOVE to learn how to build my own image, that is something I think I would enjoy. I just need to educate myself further....much further to make that happen, which is what led me to this forum. I am just now piecing together all that goes into a proper image so I can explore building one of my own.

@agtrigormortis Dosabian! Thank you... I will check that out. It's all changed from a few years ago.

I'm no good with Linux script. On my acrade build I tried 3 different screens all wider x 16:9 and they all looked awful. I went with a 2000's style 4:3 flat 20inch monitor but I had to get someone to set the PI up for VGA output and resolution and sound output on the headphone jack for the amp. I also used a VGA signal booster. The screen filters on retro arch are amazing for getting the CRT scan lines and barrel shape...I'm still in awe of the display after 3 years!
The guy also took all the things off that take away from a stand alone arcade machine... I found people go for a look in Amiga or PlayStation(keyboard+analogue inputs) and that makes it poor because it doesn't work with pure arcade inputs. I'd much rather get an expert to help with the script though. 😎

@amook11

I had the same problem and with my pi in the network and under

\\retropie\configs\amiga\amiberry\conf\

I opened and edited this file:
rp-a500.uae
it has a line:

kickstart_rom_file

there goes the exact name of your 1.3 rom in the bios folder.
of course you can also rename your existing rom to name that's already there.

same procedure needs to be done for the 3.1 kickstart I 've just noticed..

for people unsure about the correct roms: https://github.com/midwan/amiberry/wiki/Kickstart-ROMs-(BIOS) there you can find information about the versions needed including a crc check code, to see if you've got the right file.

@cayaco 2003- plus is a separate emulator, under experimental packages. The config is probably under your roms/arcade/mame2003-plus/cfg/default.cfg If your mame games use the arcade folder.

@posti85
the workaround is to check you gcc version on your setup for example mine is 9.3
in CLi type
gcc --version

then in the scriptmodule as @mitu advised initially find the 2 entries pointing gcc-6 lines 20 and 32 (im having 4.7.2 rpie setup script) and in my case i added gcc-9 fo example
save, start or restart rpi setup and should compile ok
BUT again as @mitu
i d recommend lr-mgba which is better for gba

@magick81 it's not available for the RPI4.

@chrisdrackett I reinstalled from source and now have sound again.

@xionyus as I’ve told countless others that are new here with prebuilt systems, retropie is not a product you buy, but a hobbyist project that lets people build their own retro console. There is no firmware, there is no single programmer. It’s a mishmash of many different programs and projects by many different people. The retropie developers just brought them all together into a nice tidy little package. But it far from a full retail package.
The reason why we can’t help you is a lot of us know how retropie is supposed to work out of the box, with the base image. And is pretty simple. If something goes wrong, it requires your knowledge of what you did to figure out what’s going on. We have no idea what a 3rd party did, therefore can’t help.
Try starting over and enjoy the journey of how all the pieces work together, like how many of us started.

FIXED
The script from installing the HAT had inexplicably forced the HDMI signal to the other port whilst running emulationstation !
I switched ports and all good !!

Ok so I've found out why, for anyone that could find this thread later on, with the same issue. It is far simple as Skyscrapper, at the time of this posting, does not support Famicom and Super Famicom as a platform. Maybe in a futur update? Maybe never? We'll see in time.

For now I've placed my Famicom in my NES rom and Super Famicom in my SNES folder and did the scrape. Then I moved it back to the famicom and sfc folder respectively, including the gamelist.xml and the media folder.

It's a bit of a hassle, but it get the job done.

URL to the supported Skyscrapper platform :
https://github.com/muldjord/skyscraper/blob/master/docs/PLATFORMS.md

@lupsyn My Dpad keys (contoller is SNES ) are not working on Nintendo64. Can someone paste their \configs\n64\inputsautocfg.ini

@masteryoer
I had the same issue. The games under nes was slow and the audio was laggy.
The solution was not the resolution setting.
The solution was to change the audio driver under the raspiarch config and disable audio synchronization