@comet424 You can use the SSD for OS also, but it will be formatted with a Linux filesystem and you'll not be able to read it from Windows/macOS. Using a sdcard for the OS/RetroPie is easier for upgrades, since you'll write the new OS release (when upgrade will require it a full re-image), but you'd still have the ROMs on your external SSD. Using the SSD with a Windows friendly filesystem will also make it easier to copy your games to/from it on another PC running Windows/macOS.

I don't think so - if your desktop is runing and EmulationStation is also running, then the GPU is clearly supported. Ubuntu 21.10 is quite a recent distribution and the Iris Pro 580 (Skylage generation) is from 2015.

Hmmm. Yes, that's a good point. Well I cant understand why I did the very same steps on both NUCs yet no blank screens on my Gen4. Anyway, its not an issue as I'm not using the Skylake anymore.

Anyway. here is the output from a default core, not sure if it can help you decide what the difference is but Im dropping it here for your review if you have time:
https://pastebin.com/rCm2NDf2

@sleve_mcdichael got some nerve saying I abuse my calculators like that lol

@pygamegirl The PC installation needs an internet connection to download RetroPie and the source of various programs needed (emulators/front-end/etc.).

If you're looking for an offline install, you can try other retro-gaming projects like Lakka, Recalbox or Batocera, I think they include everything in their image and don't need an internet connection to complete an installation.

Please add some more details about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Pressing A when the game is loading and changing the resolution for the emulator. Can't seem to find the right one.

Just remove any custom resolution and leave the game/emulator running with the default resolution. Check if you haven't got a 'render resolution' configuration and remove it also.

I saw an answer somewhere to run the command sudo raspi-config. Is that the command, nothing else?

raspi-config sets the global resolution, used when starting the Pi, but it doesn't affect the individual game/emulator resolution if you're changing it from the runcommand menu.

I also saw an answer to go to Settings and choose "Adjust Resolution" but can't seem to find that.

Maybe in the Configuration Editor ?

Thanks for the responses so far. An update on this issue: I gave the analog settings in Retroarch a try but they had no impact on the sensitivity.

I decided to go back and dig deeper into mouse polling. I came across more information about mouse polling in Linux: https://wiki.archlinux.org/title/Mouse_polling_rate#Polling_rate_and_polling_interval

I added usbhid.mousepoll back to the boot config file, set the GRS spinner to pulse at 512, and did some testing. Without that command or when I set it to value 0 (system use polling rate requested by device), my spinner runs slow. When I force the system to poll at either 1, 2, 4, or 8, the spinner runs at a much faster speed. The spinner moved at the same speed with all four values, so I left it on 8 to save CPU cycles on the Pi.

I set MAME sensitivity according to the formula (14%) and the blaster now free spins at the familiar speed. I can also properly adjust Major Havoc. Interestingly when I do a 5-space full turn test, a full turn with the GRS is exactly 10 spaces. The blaster isn't moving twice as fast; the blaster clicks at the same speed as this guy's setup with a turbotwist:

I wonder if the GRS is reporting a half turn as a full turn.

In any case, I'm willing to call this issue resolved to my satisfaction.

@Drdave79 the .CD1/.CD2 are not standard extensions, they're probably renamed .cue or .chd files, just to hide them from the list in EmulationStation. If they're really small files, they're certainly .cue files.

@kotif92 Probably not without additional configuration. Judging by the name, it's probably based on a Compute Module 4 (CM4), which implies custom hardware, hence it might need additional drivers and/or configuration. If the vendor/creator of the hardware provides instructions on how to configure it, you can use it with the RetroPie base image.

@stonewind please supply a verbose log as per https://retropie.org.uk/forum/topic/3/read-this-first

@Folly said in Moving art/video-snaps/gamelists/and-other-settings to USB Drive ALONG with ROMs?:

you also have to copy the media and change the locations in the gamelist.xml otherwise your media isn't found.
You can simply do that with find and replace in a text editor.

Thank you for that information, but TBH the entire point of me making this post is basically to NOT have to manually edit .XML files (and like 30+ of them for all the systems I run). Just trying to see how in RetroPie you can turn on the feature to have the gamelist.xml's and the media folder w/ artwork switched over to the individual rom folders. Skyscraper seems to do this, but that process can take days or WEEKS even (when it's acting up and timing out 99.99% of the time) – so it is possible, just don't know how...

@cdaters said in Moving art/video-snaps/gamelists/and-other-settings to USB Drive ALONG with ROMs?:

What you are proposing is very cool, you are looking for a portable RetroPie set-up much in the same vein as a Portable Apps USB flashdrive. I don't know if this is realistic in the sense that your emulators on each Pi that you run that USB drive on would have to be configured the same way. This includes your controller configs, etc.

Right now I'll be happy if I can get my first step figured out: how to get my games + scraped art onto the USB drive, and have a fresh system read from the USB for those two things (nobody yet has been able to tell me a good way to point RetroPie to the USB drive for those things...).

My premise to do this is simple: scraping is STILL a nightmare, ~SIX years later (since my 1st build). Granted these last two spats have been the best ever, but with a six year history of it timing out forever (even with extra threads on Screenscraper.fr), and taking me literally, no joke, days to even WEEKS to scrape my 30+ systems properly, I have very high doubts it'll continue to be good.

So, when I can get an entire Pi setup, ALL my customizations, all roms working, everything – in a couple hours, minus artwork... but then it can STILL take anywhere from like 6-12ish hours (best case scenario), to DAYS to WEEKS to scrape the art for 30+ systems. This is why I want a USB drive with all games, then in each individual rom directory have the gamelist.xml + 'media' folder with all the art/videos so I never, ever, have to deal with a scraping nightmare ever again.

...I'll deal with the settings later (which BTW, the gamelists have NOTHING to do with any of my other tweaks - they literally just say the game name + where to find the art/videos-snaps... so they work on ANY emulator on ANY model of Pi!).

The font in the message blurb is not set by theme, it's the default EmulationStation font - the size is not configurable.
It would be nice if the size would be bumped on smaller resolutions, could be a nice addition.

I've put a guide up here for SORR 5.2 and RetroPie 4.7.x - although this is with a Pi 3.
I'll do another one when I get a Pi4.

@ecto Thanks for the configs, I did some analysis. First: I should have mentioned that after the change of this line to make -j4 PLATFORM="rpi4-sdl2" the amiberry must be rebuilded and installed (sudo ./retropie_packages.sh amiberry), please also make sure you use v4.1.6 of Amiberry and not the current master, just in case you missed it.

From the configs I found these differences to mine:

In amiberry.conf:
Diffs mine (which are also the default amiberry.conf settings) starting with - (red), yours starting with + (green)

$ diff -bB -u --color amiberry.conf amiberry.conf_usr_ecto --- amiberry.conf 2022-03-04 18:10:15.818541075 +0100 +++ amiberry.conf_usr_ecto 2022-03-04 17:57:08.000000000 +0100 @@ -5,7 +5,7 @@ rctrl_as_ramiga=no gui_joystick_control=yes use_sdl2_render_thread=no -default_multithreaded_drawing=yes +use_drawing_thread=no input_default_mouse_speed=100 input_keyboard_as_joystick_stop_keypresses=no default_open_gui_key=F12 @@ -15,11 +15,11 @@ rotation_angle=0 default_horizontal_centering=yes default_vertical_centering=yes -default_scaling_method=-1 +default_scaling_method=0 default_frameskip=no default_correct_aspect_ratio=yes default_auto_height=no -default_width=640 +default_width=720 default_height=512 default_fullscreen_mode=2 default_stereo_separation=7 @@ -38,49 +38,3 @@ default_whd_buttonwait=no default_whd_showsplash=yes default_whd_configdelay=0

You may change them one by one to my settings and retest after each change.

In config.txt:
I have seen you run a high overclocking. Maybe you can disable it for the tests on amiberry. I had different downside effects on Amiberry (3.3 and 4.1.6 when OC over 1950Mhz) (on my 4.19 kernel with fake KMS).
I assume you are using a (4k?) TV for the Raspberry. Can you try with a full HD computer monitor?
E.g., set hdmi_group=2, hdmi_mode=82 or set only hdmi_group=0, I guess you know the switches. --> https://www.raspberrypi.com/documentation/computers/config_txt.html#hdmi_group

And I did not review/change the WHDLoad file. I just let it sit there. You should however update it from time to time (within the Amiberry UI menu), if you haven't done it recently.

HTH

@Xorcode in this case, please provide a log from running the game - see here. EmulationStation closing is normal, it minimizes itself so that the game can start.

You're running a very old 3rd party image which may not be compatible with your Pi.

Start with the image from retropie.org.uk/download and we'll be able to assist you - we don't support 3rd party images in the forums, as noted in the https://retropie.org.uk/forum/topic/3/read-this-first topic (see point 4.).

Can you give more details about your system ? See https://retropie.org.uk/forum/topic/3/read-this-first; you don't have to list all gamepads in the info, but what is important is what platform are you running on and how are the gamepads connected.

EmulationStation should save the controller info after the gamepad is configured, this is stored in $HOME/.emulationstation or (if you're using file shares to access your system) in \\retropie\configs\emulationstation. The filename is es_input.cfg and you can check its contents after each controller is configured to see if an entry for it is added.
It's better to add them one by one and - after adding one controller - restart EmulationStation and check that the controller works fine.

[..] when I run games it goes to the 4 arcade joysticks.

That's probably because they're added as Player 1 - 4 in the order of their detection and they're always detected first.

I have set retroarch to show 13 ports so I can finally see all the controllers

Not sure how useful this is unless you want to play a 13 player game - not a very common scenario.

. I also have the setup of the controllers get mixed up in emulation station and I have to go back into setup each one or restart the system.

That may happen if different controllers have the same name and Vendor/Product IDs. The name and VID/PID serve as an identifier to the configuration of the controller (not only in EmulationStation, but emulators also). That's not something that can be fixed easily or by configuration: if 2 different controllers identify themselves similarly, then how can the system tell them apart ?