Debugging PORTS Wolfenstein 3D

[fraser]

Hi,

I feel a bit silly posting this but I just can't work out what the issue could be.
I am attempting to play Wolfenstein 3D in retropie on a Raspberry PI 3.
I have retropie installed within OSMC.

I have set up countless systems already, and have even built a fully working gameboyzero without any issues at all.
However my current build is giving me issues specifically with Wolfenstein 3D - whenever I try to run the game, either the shareware or Steam versions, or any of the spear of destiny levels I get the.

"NO WOLFENSTEIN 3-D DATA FILES to be found!" message in the logs.

However if I

cd RetroPie/roms/ports/wolf3d
md5sum *.wl6

I get...
osmc@media:~/RetroPie/roms/ports/wolf3d$ md5sum *.wl6
a41af25a2f193e7d4afbcc4301b3d1ce audiohed.wl6
2385b488b18f8721633e5b2bdf054853 audiot.wl6
aa75133df873b660d2058425ca8539b3 config.wl6
a4e73706e100dc0cadfb02d23de46481 gamemaps.wl6
b8d2a78bc7c50da7ec9ab1d94f7975e1 maphead.wl6
dec8939cff5a4ec27ae7b43e8f52ec28 vgadict.wl6
8b40b5b785f898e229bf1c2f2e3ee003 vgagraph.wl6
8e75e3ffb842ed3d08abe6ffea97b231 vgahead.wl6
b8ff4997461bafa5ef2a94c11f9de001 vswap.wl6

Same for the SOD files - everything checks out and is from my own full legit paid for steam version that have worked on other systems I have built.

For some background the only thing I have done differently in this build is to put my ROMS directory on an external 1TB WD pidrive - I just symlinked "/home/osmc/RetroPie/roms" to "/mnt/pidrive/roms". It is the only thing I can think of - but It would seem odd because as I say every other system and game worts perfectly (I have 9 systems with about 300 games, plus 5 PORTS that do work, quake, doom, cannonball, etc)

So - I have also tried updating all the paths in the "/etc/emulationstation/es_systems.cfg" rather than symlinking - again everything works perfectly except wolfenstein!

Can anyone think what the issue might be - I have tried removing/reinstalling countless times now all with the exact same
"NO WOLFENSTEIN 3-D DATA FILES to be found!" message.

Failing that how else can I debug what is happening to see what the issue might be? More verbose logging options etc?

It is driving me nuts!

Pi Model or other hardware: PI 3
Power Supply used: 3AMP official
RetroPie Version Used: 4.2
Built From: git in osmc
USB Devices connected: WD pidrive 1TB
Controller used: iBUFFALO USB 8 Button Famicom
Error messages received: "NO WOLFENSTEIN 3-D DATA FILES to be found!"

[edmaul69]

@fraser when you are going to play a game and it says press a button to configure are you going into the emulator option and trying all 4 wolf4sdl options? By default it is set on the on the one for the demo version.

[fraser]

@edmaul69 Thanks - Yes I am selecting the correct version for the files - and I have tried the Shareware and SOD files - including all the levels - every time I am selecting the correct emulator for the ROMs. i.e. wolf4sdl-gt-v14 for Steam, wolf4sdl-sw-v14 for shareware, wolf4sdl-spear-v14 for SOD, etc.

Also when I try to run the shareware - without adding/changing anything I get the same error... It is like the binaries are not following the symlink at all or honouring the paths in the cfg file ...

I am going to play around this w/e to see if I can get it working - if I do I will post back to say what the issue was!

[fraser]

Got it working :)

Feeling a bit stupid really - it was the external disk permissions, or rather lack thereof in fstab.
In my haste to get the pidrive connected I had just put a basic automount together but hadn't added umask or uid to the defaults.

Amending the fstab entry to include "umask=000,uid=1000" for EHD did the trick - as soon as I remounted the drive and launched the game it worked AOK.

The bizarre thing is though only wolf3d has this problem - I have pretty much tested every rom on every system with this new set up (hence the 1TB drive :)) and this is the only thing that didn't run first time.

Anyhow hopefully this will help anyone who has similar issues - thanks to @edmaul69 again for getting me to check the obvious things again - it was that that made me retrace my steps and double check everything :)

[edmaul69]

@fraser glad you got it working. I would have suggested permissions next but i know nothing about fstab so i would have been useless on that part.