Ports not working - all other roms working

klein1jo

FWIW I just added "-g/home/pi/RetroPie/roms/ports/duke3d/duke3d.grp" to my Duke3D .sh file and the game started. Like I said I used the automated install for eduke32 (place the files in the appropriate dirs, install eduke32, and it creates the .sh files). This is smelling like a bug.

sleve_mcdichael

@klein1jo said in Ports not working - all other roms working:

FWIW I just added "-g/home/pi/RetroPie/roms/ports/duke3d/duke3d.grp" to my Duke3D .sh file and the game started. Like I said I used the automated install for eduke32 (place the files in the appropriate dirs, install eduke32, and it creates the .sh files). This is smelling like a bug.

The automated install didn't work for me either, but since I wasn't using the Steam versions of the game data (mine came off old install media), I just assumed that was the reason. Are your game datas actually Steam, or do you also have something else?

klein1jo

Original install media from the 90s. The errors are WTF though. Can't find the media, but it's clearly there. Both Doom and Duke3D so I'd say bug. I'm gonna fix my Duke3D .sh files manually. Haven't figured out what to do with Doom yet.

sleve_mcdichael

@klein1jo said in Ports not working - all other roms working:

Original install media from the 90s. [...] I'm gonna fix my Duke3D .sh files manually.

I'm pretty sure the -addon {n} option doesn't work for that, but only with the Steam version data. Here's what I got working manually for duke3d using the original install media data (Atomic Edition and the individual expansion CD-ROMs); no two of them used quite the same set of launch params:

roms/ports:

duke3d.sh
duke-dc.sh
duke-nw.sh
duke-vacation.sh

duke3d/
------| duke3d.grp
------| duke.rts

duke3d/dc/
---------| defs.con
---------| dukedc.grp
---------| game.con
---------| user.con

duke3d/nw/
---------| nwdefs.con
---------| nwinter.con
---------| nwinter.grp
---------| nwuser.con

duke3d/vacation/
---------------| defs.con
---------------| game.con
---------------| user.con
---------------| vacation.grp

duke3d.sh:

#! /bin/bash
"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "duke3d" "-j /home/pi/RetroPie/roms/ports/duke3d/"

duke-dc.sh:

#! /bin/bash
"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "duke3d" "-j /home/pi/RetroPie/roms/ports/duke3d -g dc/dukedc.grp"

duke-nw.sh:

#! /bin/bash
"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "duke3d" "-j /home/pi/RetroPie/roms/ports/duke3d -g nw/nwinter.grp -x nw/nwinter.con"

duke-vacation.sh:

#! /bin/bash
"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "duke3d" "-j /home/pi/RetroPie/roms/ports/duke3d -g vacation/vacation.grp -x vacation/game.con -j /home/pi/RetroPie/roms/ports/duke3d/vacation"

klein1jo

--addon does work for the original files, or at least did. I had these working in 4.7.x using the auto-install. I don't know at what point they broke because I haven't played them in ages. I did a clean install of 4.8 and found this testing stuff.

I did mirror what you did so I can say I tried. Doesn't work either. I have to specify the whole path for -g. Works when I do that. -j to specify the search path and then using the relative path for -g doesn't work. Always complains not a dir or can't find. Same thing with Doom. Can't find the dir. As you can see from my first post it's there. I can navigate there.

sleve_mcdichael

@klein1jo I can't say, then. I am on a Pi 4 though, I suppose that might be the difference.

klein1jo

Reviving this topic as issue is still outstanding. Ports won't run from a network volume. All other roms will. I plugged a USB drive into my RPi, copied the ports to it so it was a local block device, and mounted it on /home/pi/RetroPie/roms/ports. Ports work doing that. So specifically ports won't run from a network volume. Tried both NFS and CIFS. You can see the errors above. I have no clue at all here.

klein1jo

No ideas?

Lolonois

@klein1jo The error message '... for game data...' from eduke stems from the emulator [1].

The version RetroPie is using version dfc16b08 (Sept 2019) for reasons for the eduke emulator. See /home/pi/RetroPie-Setup/scriptmodules/ports/eduke32.sh:

rp_module_repo="git https://voidpoint.io/terminx/eduke32.git master dfc16b08"

You may try to remove that revision thus the line reads:

rp_module_repo="git https://voidpoint.io/terminx/eduke32.git master"

Then reinstall the package.

If it compiles and finds the game files then the issue is likely in the RetroPie playfield.
If you still get the same error message (or the emulator still does not pull in your gamefiles) then reach out to the eduke maintainer for the issue. (You can also reach out to the eduke maintainer rightaway but he most likely will ask you to test with the latest from main branch anyway.)

[1] https://voidpoint.io/terminx/eduke32/-/blob/master/source/sw/src/game.cpp#L3492

Update:
I am not able to reproduce this neither with current HEAD nor with dfc16b08 of eduke emulator.

I am using these NFS settings (server is kernel 5.15 and NFS4; OpenWRT 23.05.2):

/mnt/<some_dir>          <IP-of-Pi>(rw,sync,no_subtree_check)

On Pi side:

<NFS-Srv-IP>:/mnt/<some_dir> /home/pi/_roms_nfs nfs _netdev,soft,rsize=16384,wsize=16384,timeo=14,intr,noauto

Tested with: /opt/retropie/ports/eduke32/eduke32 -j /home/pi/_roms_nfs/duke3d/

You may want to try with these settings.

One more thing: If you want to remove NFS from the mix maybe try sshfs? It is less fuss to setup. For my purposes sshfs serves well.

klein1jo

@Lolonois Those are all excellent suggestions. Lots to try. Thank you. I like the idea of sshfs. I don’t use NFS for anything else so that’s one less service to run server side. That’s interesting about eduke. I just assumed install from source would be the latest. Guess not. Do you know does prboom also not install the latest from source?

Alas shortly before your response I said enough and tossed Recalbox on my Pi. It’s playing Doom just fine from NFS which RetroPie was not. Another thing that points to it being a RetroPie problem. Next time I’m bored, which is pretty much always, I’ll toss RetroPie back on the Pi and try your suggestions. I had updated my RetroPie via retropie_setup. Did you do that? I always wondered if I reflashed and didn’t update if the ports would work fine. I’ll be sure to test that first thing before updating when i do flash.