MKDD Tint Issue RPI5

[TPR]

@gvx64 Tried a number of different configurations and file names, rom locations, etc, and nothing seems to work. For some reasons my roms are no longer populating in Dolphin.

[gvx64]

@TPR OK, firstly in your m3u file, please get rid of "/home/pi/RetroPie/roms/gc/" and only include the file names (one file name on each line). The contents of the m3u file should look like this:

RE4_1.ciso
RE4_2.ciso

[TPR]

@gvx64 I tried that also. Same results.

[TPR]

@gvx64 This is what my file currently looks like:

The bigger issue here seems to be that my rom files are no longer showing up in dolphin. Either .iso or .ciso format. I get nothing populated.

I may have to just re-install from scratch again and I can try that this weekend.

[gvx64]

@TPR One thing to also make sure of is that you create your m3u file in Linux not windows. The line-ending characters are different between the two operating systems. For this reason, there will usually be major issues if you try to run a script on linux that was created on Windows.

I only thought of this because you have the file open in WordPad in your screenshot. I really hope that this fixes the m3u issue.

I am trying to think about why the gamelist is not working for you.

[gvx64]

@TPR In regards to the game list can you please try the following command:

sudo chmod +777 -R /opt/retropie/emulators/dolphin-rpi/bin

I am not sure, but it is possible that your binary does not have full privileges. This could be preventing the game list module from properly reading the iso's.

[gvx64]

@TPR The only other possible solution that I can think of regarding your game list issue is that you might want to rebuild dolphin-rpi using the instructions in Post 42 and not use the install script. I have rebuilt dolphin-rpi just now using the procedure in post 42 and I can confirm that the game list is fully functional.

[TPR]

@gvx64 said in MKDD Tint Issue RPI5:

@TPR One thing to also make sure of is that you create your m3u file in Linux not windows. The line-ending characters are different between the two operating systems. For this reason, there will usually be major issues if you try to run a script on linux that was created on Windows.

I only thought of this because you have the file open in WordPad in your screenshot. I really hope that this fixes the m3u issue.

I am trying to think about why the gamelist is not working for you.

All of the other m3u files I have work just fine though on the normal version of Dolphin. I don't think it's the m3u file honestly, it has to be something with why the games aren't populating. I'll try re-instaling rpi from scratch this weekend on a new build.

[gvx64]

@TPR That might be the case for a more current build of dolphin but keep in mind that I implemented a very early version of m3u support in dolphin-rpi that appears to be more finicky about this sort of thing.

Actually, I just tested this theory on my end by creating an m3u file for Tales of Symphonia using my Windows 11 machine and uploaded it to my Pi4 and I got this error message:

This error does not occur if I create the exact same m3u file using nano on the Pi. As a result, I am 90% sure that the source of your problem with the m3u functionality is because it is having issues reading the windows file. It is very easy to create on your pi, you can do it with the following commands:

sudo nano /home/pi/RetroPie/roms/gc/RE4.m3u

type in the following text:

RE4_1.ciso
RE4_2.ciso

You can then save this file by using the keystrokes "CTRL-X" followed by typing "y" and then "ENTER". This creates an authentic Linux m3u text file that should now work in dolphin-rpi.

The bigger and much more confusing problem to me is why your games list is not populating. I rebuilt 3rd copy of dolphin-rpi tonight following the exact instructions in Post 42 and the game list works perfectly for me. I hope that if you follow those steps exactly that it should work for you this time (fingers crossed).

[retropieuser555]

@gvx64 said in MKDD Tint Issue RPI5:

Instructions for Building from Source

cd /home/pi
sudo mkdir ./dolphin-rpi/
sudo git clone https://github.com/gvx64/dolphin-rpi
cd ./dolphin-rpi
sudo git submodule update --init --recursive

I wouldn't use sudo to make the dolphin-rpi directory, you can just git clone straight away. Otherwise it'll mess up all the permissions. Or later in your code the user probably won't be allowed to make the build directory

cd ~
git clone https://github.com/gvx64/dolphin-rpi
cd ./dolphin-rpi
git submodule update --init --recursive

[gvx64]

@retropieuser555 said in MKDD Tint Issue RPI5:

@gvx64 said in MKDD Tint Issue RPI5:

Instructions for Building from Source

cd /home/pi
sudo mkdir ./dolphin-rpi/
sudo git clone https://github.com/gvx64/dolphin-rpi
cd ./dolphin-rpi
sudo git submodule update --init --recursive

I wouldn't use sudo to make the dolphin-rpi directory, you can just git clone straight away. Otherwise it'll mess up all the permissions. Or later in your code the user probably won't be allowed to make the build directory

cd ~
git clone https://github.com/gvx64/dolphin-rpi
cd ./dolphin-rpi
git submodule update --init --recursive

Thanks, I agree with this. I will modify Post 42 to remove the unnecessary directory creation from the instruction set when I have some time.