You may also try the scriptmodules I put together a while ago, but do still work fine. These make ScummVM game setup and switching between ScummVM and the lr-scummvm a breeze.

https://retropie.org.uk/forum/post/275199

With that branch you just have to have a file structure like this in the ~/RetroPie/roms/scummvm/ folder:

... ├── Monkey-Island-1 The-Secret-of-Monkey-Island/ ├── Monkey-Island-1 The-Secret-of-Monkey-Island.svm ├── Monkey-Island-2 LeChucks-Revenge/ ├── Monkey-Island-2 LeChucks-Revenge.svm ...

The actual folder name and .svm filename do not matter per game, they just need to be matching per game like above. The *.svm can also be empty initially, the game id will be filled in by my scripts. Just put the required game files into the respective game folder as per ScummVM wiki.

Start a game with the native ScummVM once, then you may switch at the second launch to the libretro ScummVM in the runcommand menu. And switch back and forth. That's it, that's all. :)

RetroPie-manager has been removed since it's been un-maintained for years and it's not compatible with Python3. The original project repository has been deleted years ago and we kept a copy under RetroPie's Github account.
You can still find it at https://github.com/retropie/retropie-manager/ if you wish to try to make it work/install it.

@CubeSteak said in Doom Help 2024:

What do the permissions need to be for it to work and how do you modify them?

If you copy as you do for the other ROMs, permissions shouldn't be a problem. See our docs for transferring ROMs.

Since it is accessed through the Doom II script and game, is the script I put in for that particular WAD useless and can be deleted?

Yes.

@sugarfree wow, its amazing how you just solved my problem with only two lines of code. Thank you so much, words fail to express the relief you just brought me lol

Yes, you can use it.

I know this is an old thread, but I figured out how to get this working using the GSPLUS emulator. You'll need to create a .gsp file for Flobynoid. I used the sd71 slot and followed the path to another version of the Flobynoid rom with a .po extension. I also used an apple2gs.rom1 when I picked the ROM file. It will run Flobynoid in GS Mode when you do this.

Here is what my .gsp file looks like:

GSplus configuration file version 0.14

s5d1 =
s5d2 =

s6d1 =
s6d2 =

s7d1 = /home/pi/RetroPie/roms/APPLE2GS/Flobynoid.po

g_joystick_scale_factor_x = 281
g_joystick_scale_factor_y = 281
g_cfg_rom_path = ../../../../home/pi/RetroPie/roms/apple2gs/APPLE2GS.ROM1

bram1[00] = 00 00 00 01 00 00 0d 06 02 01 01 00 01 00 00 00
bram1[10] = 00 00 07 06 02 01 01 00 00 00 0f 06 06 00 05 06
bram1[20] = 01 00 00 00 00 00 00 01 00 00 00 00 03 02 02 02
bram1[30] = 00 00 00 00 00 00 00 00 08 00 01 02 03 04 05 06
bram1[40] = 07 0a 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d
bram1[50] = 0e 0f ff ff ff ff ff ff ff ff ff ff ff ff ff 81
bram1[60] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[70] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[80] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[90] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[a0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[b0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[c0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[d0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[e0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram1[f0] = ff ff ff ff ff ff ff ff ff ff ff ff 52 04 f8 ae

bram3[00] = 00 00 00 01 00 00 0d 06 02 01 01 00 01 00 00 00
bram3[10] = 00 00 07 06 02 01 01 00 00 00 0f 06 06 00 05 06
bram3[20] = 01 00 00 00 00 00 00 01 00 00 00 00 05 02 02 00
bram3[30] = 00 00 2d 2d 00 00 00 00 00 00 02 02 02 06 08 00
bram3[40] = 01 02 03 04 05 06 07 0a 00 01 02 03 04 05 06 07
bram3[50] = 08 09 0a 0b 0c 0d 0e 0f 00 00 ff ff ff ff ff ff
bram3[60] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[70] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[80] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[90] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[a0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[b0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[c0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[d0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[e0] = ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
bram3[f0] = ff ff ff ff ff ff ff ff ff ff ff ff 36 2d 9c 87

As far as the BIOS roms go, I could never find the correct apple2.zip, so I copied the set of Apple II roms that were included in a build of Batocera I am currently using with my Pi5. I'm going to replace that with RetroPie once the experts here get around to creating a stable build, but I thought I'd share my solution here for those who want to try Flobynoid with GSPLUS.

I have now gained new insights into the VSync problem, because it seems that the TV or the HDMI detection is really to blame. I just had my Raspberry Pi connected to my 13-year-old Panasonic 3D TV and the VSync option works exactly as it should. What I also noticed is that the screen modes are swapped in the video setup menu, which you can select when selecting a game before starting Amiberry via Retropie. On my old TV, the 50 Hz modes are first in the list and only then do the 60 Hz entries follow. On my Philips TV from 2014, it is the exact opposite, so that I have to set the correct mode every time I change TVs. However, it does not seem to take the 50 Hz modes into account at all or does not switch despite the selection and only runs at 60 Hz instead of 50 Hz, which I find very strange, because the TV is definitely capable of handling both refresh rates. This also works with all other emulators, whether with VICE (C64) or all RetroArch cores such as NES, SNES, Mega Drive, Arcade, etc. Just not with Amiberry, which I find very unfortunate. The Retropie team would probably have to release an update to detect the connected screen in the Amiga Setup Menu. I actually thought that HDMI screens were all standardized by now and the only explanation I can think of is that it has something to do with an error in the setup script for Amiga core.

@stanbu84 said in cant see systems or roms in retropie:

just started getting into pi's and command prompts and what not so i feel very green and dumb. thanks for the assist.

You don't need to use the command line at all. Our docs explain everything, even in video form if you'd like to.

@StonedEdge said in How to run RetroArch cores with DRI_PRIME=1?:

Are you sure about that? I believe we now have "/dev/dri/card0" for NPU and "/dev/dri/card1" for GPU, and have to specify that explicitly… not sure if that’s getting mixed up somehow when launching retroarch.

Yes. I think you're confusing some things here and your MESA/DRM libraries are most likely the issue here - not RetroArch.

@Retrodade What kind of Repository do you use for "retropie-extra", this ?
I think this works fine (but I haven't tested yet Philips CDI games):
https://github.com/Exarkuniv/RetroPie-Extra

But I tested it with many other emulators like:
"AetherSX2 - PS2 Emulators" runs in 60Fps with my Pi5.
"Sega Supermodel 3" runs very well with my Pi5.

Well, I found a solution.
I'll post it just in case anyone runs into my same problem.

I started from scratch using Pi Imager again. This time tho, I've been using the super magic hidden shortcut Shit+Ctrl-X to bring up a hid option panel!
Here I setup the wifi and the country. Then I flashed the sd.

When you first run the system inserting the sd back on the Pi, you'll have no wifi again for some reason. The system suggests to set the country (again) in the rasp-config, just click ok, and lo and behold, this time it works.

I could change the country to my zone, setup my wifi and access the Pi over the network connecting to \retropie

bingo.

@mitu

Solved
I added

mupen64plus-next-cpucore = "cached_interpreter" parallel-n64-cpucore = "cached_interpreter"

in

/opt/retropie/configs/all/retroarch-core-options.cfg