@dankcushions I finally figured out what the problem was. I simply used the wrong hdmi on the Pi. For my Monitor and most other Users its the inner hdmi. For my OLED its the outer one..

@raspberry79 this is the retropie forum. we don’t support lakka. try https://forums.libretro.com/c/libretro/lakka-tv-general i guess

The cmdline.txt options in the linked topic will only rotate the console terminal, not the entire display. To rotate also EmulationStation's screen or the emulator video output, you need additional configurations - some details are in this topic.

Press again Ctrl + C ?

@AlphaBetaPie not sure, but mame2010 is a relatively immature core that has a bunch of missing/broken features, hence it’s not the default/recommend mame core. it’s not really had the attention of the recommend ones.

Yeah, it looks like I assumed the official doc was still the page I needed to check. I was able to find that now (although it was a bit confusing since those are two different things...settings vs controls). However, it's working now.

But now I'm wondering about something. None of the other emulators that use the six-button controllers require me to force the six-button settings in the Retroarch core first (or at least the Sega-based ones). With core remapping, I'm able to get them to cooperate. Would there be any benefit to turning on six-button in the other cores (where core remapping is already working fine)?

@mitu Many thanks this sorted it. The game still fails but presumably an unrelated reason. Will try and resolve.

@RetroGenZ basically, no. depends on your local jurisdiction, but you almost certainly need an entertainment/gaming license for the premises, and then individual licenses for all commercial games you're charging people to play (which are basically impossible to get for emulated retro games), and the the emulators themselves may have licenses that forbid commercial use.

Can you add more details about your setup, as requested in https://retropie.org.uk/forum/topic/3/read-this-first ?
What program did you install for i2c ? Or maybe you just enabled i2c through raspi-config ?

Can you post the complete verbose log on pastebin.com ?

@hawkes_84 It isn't too bad. I never had a ZX Spectrum back in the day (I'm from the US), and I also didn't have a computer to have the chance to play the old text-based adventure games. I'm playing this game because it is based off of the first book from my favorite author David Gemmell. I tried this game out via another emulator years ago but didn't really do much. Now, I've decided to play the game all the way through :).

@mitu Actually I've been trying to get that working. I also have a RPI 2 (?) or something, which I've installed Raspberry Pi OS on. If I put that card into my RPI 2 I can ssh in and I still couldn't get the screen working.

If I put the same SD card (AFAIK the image you install is the same? I use Raspberry Pi Imager) in my RPI 4B I can't SSH in because the standard password somehow isn't 'raspberry'? I even reinstalled. Either way I can't get anything to show up on the screen with either of the pi's. I think it's DOA, but the company I got it from is not responding to me anymore.

@mitu thank you for that information, guess I'm not buying it after all.

@Thorr69 said in Why Does My HDD Not Always Load?:

@AlphaBetaPie said in Why Does My HDD Not Always Load?:

@Ashpool said in Why Does My HDD Not Always Load?:

@AlphaBetaPie said in Why Does My HDD Not Always Load?:
However, I may be missing something here.

Yes, yes you are. He said to plug it into a powered USB hub. And when you fire up the system, POWER UP THE HUB FIRST. Then turn on your pi.

This ensures that your HDD is already fully powered and spinning before your Pi tries to access it.

Ah, I see! That is great info to know.

However, while that is useful, I may have found the real culprit in the meantime.

I originally replaced my default USB cable with a shorter one to decrease the excess clutter around the Pie itself. I wondered if maybe this cable was not performing as it should. So I reverted back to the stock cable and it has yet to replicate this issue. So seems like it was a signal thing vs a power thing. So just leaving this here for anyone who might face a similar problem in the future.

Thanks all!

As far as I know is the difference between the versions that the lite variant does not come with any OS preloaded. Which means it is smaller but any selected OS must be downloaded first. So an Internet connection is mandatory.

And I'm not quite sure, but I think Noobs is not actively being developed anymore. But there is PINN https://github.com/procount/pinn which also has a greater selection of systems. You can check https://pinn.mjh.nz/ to see what OS is available for your Pi.

@lukePi-0 you shouldn't be adjusting the retroarch video driver in this circumstance. info on HW rendering in duckstation are here: https://retropie.org.uk/forum/topic/30743/lr-duckstation-experimental-new-playstation-1-emulator - you cannot use duckstation HW rendering on a pi3

i believe lr-pcsx_rearmed has a core option to remove dithering.

Somewhat solved.
I went back into Bluetooth and removed the XBox controller from the paired listing, and then added it back in the usual way, and this time got no error (maybe due to the XPadNeo being installed ?), and then did the Input configuration again, and now the Middle Button + X brings up the menu to quit the games etc, like the Pi3B+ did.

Its super weird as I re-did the Input configuration 3 times and that did not solve it, before I tried removing the controller completely and adding it in again.

There certainly seems to be some sort of issue here, but I am unsure what it is exactly.

@bmn001 yeah the app is not under active development any longer but muldjord (the dev) is pretty quick with these little fixes when they crop up. Cheers!

@nightflyer said in game reset:

@Floob
Thank you for your reaction.
I will try to find that cfg file.
You mean that i have to change the "H"
In that line?

Nightflyer.

If your config is default, that line should have a # in front of it meaning it's commented out (will be ignored) and even if not, it would only be triggered if your controller was detected as a keyboard, anyway.

More likely, your players have inadvertently triggered the reset with joystick hotkey combination (select + B) which is configured in your controller's autoconfig in:

/opt/retropie/configs/all/retroarch/autoconfig/[device_name].cfg

Look for a line in that file that says input_reset_btn=[button value] and either #comment or remove that line.

If that doesn't sort you out, please post the full controller autoconfig profile and global retroarch.cfg (redact your cheevos password if it's in there) so we may review them.