If we're talking about emulated games, the date/time of the emulator may not have an influence on the RNG the game implements - most of the emulated systems didn't have a real time clock or the concept of the system date/time.

@Addison it all depends on how the game implemented the RNG, some of the games relied on the RAM contents to initialize the RNG. On an emulator, the emulated RAM may get initialized to the same value (zero for instance) and thus there's no RNG at stake. Some emulators cater for this kind of situation with options - for instance Snes9x has a Randomize Memory option for this kind of situations, others may initialize the RAM directly with random values to prevent RNG failures.

Funny enough, some games' RNG can be manipulated, a technique used in speedruns to get a predictable set of events/weapons/etc. An example is below, where the runner saves and resets the game during startup

@mitu
thx it works.

Ps.
I checked. Can also just create normal file .cfg and edit with notepad++
custom-(theme name).cfg

:)

Some of the palettes are built-in into the emulator and they don't have a file on disc associated. Only when you choose custom as the core option you need to provide a palette file in the BIOS folder.

The name of the file depends on the emulator, if you're using the default NES emulator (fceumm), then the file must be named nes.pal, see https://docs.libretro.com/library/fceumm/#custom-color-palettes. If you're using the nestopia core, the file is named custom.pal.

@yewox50273 no, alsathread has always (at least, for longer than this issue) been used for pi3, which is why i was clarifying what @nesfredo was using. the change you refer to only made it the default on pi4.

it didn’t cause the skipping issue on pi3 in years past, so clearly alsathread/RA has had some kind of change causing the issue. we should bisect this to a specific retroarch commit (version is not specific enough) to find the culprit, but it would be tricky to do so since the issue seems to occur after a game has been running a while and is sometimes hard to spot.

@sirhenrythe5th No worries, the issue was resolved as mame2003plus worked with all the games.

I just upgraded to a Pi 4 and Atari 5200 works now!

However I still get segmentation faults in runcommand on a Pi 3.

Both are running Retropie fully upgraded with the latest lr-atari800 binary.

So I guess if this is happening to you, ditch the Pi 3 like I did.

Please add some actionable info to your post - what games/emulator are you using ? Also, when asking for support, please include the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu I understand. I really appreciate all your help. It appears to be working well enough to use. I tested between a 12 year old Visio 1080p and a 3 year old 4k Sony Bravia and it works equally well on both.
Only complaint I have now is a nitpicky one. When in the menus the audio click I hear when scrolling is delayed and has inconsistent tonalities that are grating to the ear. Can only be described as sometimes scratchy and sometimes clicky. Lol. I can live with it if no ideas on that one. When in games the audio is fine and right on time.

@mitu Ill give that a go. Thank you

@marisubopa are you still experiencing the issue reported here with the latest picodrive ?

@mitu Thank you very much! It's all working now. I apologize, I totally missed the "But be aware that if "Launch Menu Art"..." part. Thanks again.

@RaspFox said in Help Needed: Can I have RetroPie and RaspberryPi OS on the same SD card?:

So it won't work for Bullseye?

Well it can work on bullseye but you have to edit some files.
Without a lot of experience it could be quite difficult for you and you can encounter some more problems.
Take a look at this thread/post :
https://retropie.org.uk/forum/topic/31924/could-not-successfully-build-sdl2-on-bullseye/8

Is there a way to save some apps that I have downloaded such as Pi Apps.

if you go with Buster these Pi Apps should probably work too.
Just use a second SD card and try it before you wipe your first SD.
Than you can work out if it will work.

These configs will not be defaulted by reinstalling the emulator. These will be stored in the default.cfg and game.cfg files. These should be located in a "mame2003/cfg/" directory in the location you load your mame roms from.

@mitu the method is still in config.txt so I guess it refers to Raspi OS as you said.

For the touchscreen it uses a command in the file usr/share/X11/xorg.conf.d/40-libinput.conf

Thank you @mitu

I will have to chase an older model pi. Now I regret not buying the 3b that I saw gathering dust at one shop a couple of months ago.

@iLouzze I don't know if there's any way to turn it on automatically without an external timer. You could probably set up a "cron job" to shut it down (I don't know how to do that, though, I have only heard of it as a way you can set up scheduled events.)

@ChaosEffect said in Tips for RetroArch 1.10.0:

@mitu I am not sure how often RetroPie's RetroArch will sync with upstream RetroArch. This is more of a typo correction than a new feature, but it makes the lightgun input operate as intended.

Thanks for the heads up. We don't update too often and we base the update on RetroArch's point releases, I guess it's one more reason to consider the next release for inclusion :).

@Floob That worked. Thanks.

I was able to sort this out.

The "PS3 Controller" driver in the driver packages causes a conflict with the Atari VCS Classic Controller over Bluetooth. Uninstalling it allows the VCS Classic to work.

Obviously, this makes it so the only way you can use a PS3 controller wirelessly is to add it using the native driver, which doesn't provide rumble/force feedback. But the controller still operates file as a gamepad.

Not ideal, but I'd rather have both controllers available, instead of rumble.