3DS emulator for Pi users based on "Borked 3DS"

Folly

@roslof
Thanks for letting me know.

@DTEAM @ExarKunIv @gvx64
Do you have the same issue ?

Edit :
Turned off the launch_extension until there is a better solution.

Folly

I added the basic structure for adding a Configuration/Options menu (also viewable from the main Configuration/Tools menu).
You can view the commit here .
Try to play with it and see how it works.
The "build_menu" code is basically code from the docsview script.
I also use that for the mamedev script, with the addition for showing and running stuff that is placed inside a CSV.
Here I used the special char □ as comma so commas can be used in the CSV.
If you somehow need to add " in the commands then use a backslash in front of it.
Let me know if you can work with that.

DTEAM

@Folly

It works, we can see options 1 to 4 . Maybe we could start (option 1 = pi5/pi4 settings and option 2 cheat codes) I didn't test a cheat code yet with that emulator. Here's a forum about it . I don't see sites with all the cheat codes ready to go. For Joystick, is there a way to match ES settings like Lr emulators?

Folly

@DTEAM said in 3DS emulator for Pi users based on "Borked 3DS":

@roslof

I have no games (many games) issue on my side for Pi5. It's probably un 3d parameter selected in the graphic options menu

If you go in

/home/pi/.config/borked3ds-emu

here's my settings

qt-config.ini

sdl2-config.ini

Game language is set to french. Youwill have to change it

You are talking about changing these ini files depending on rpi4 and rpi5 right ?
We might be able to do that without adding full ini-files.
If possible a good idea would be to change just the settings needed for that specific platform.
Something like this (copied from mame.sh) :

       iniConfig " " "" "$temp_ini_mame"
       iniSet "rompath"            "$romdir/$system;$romdir/arcade;$biosdir/$system"
       iniSet "hashpath"           "$md_inst/hash"

Edit :
Using the the cheat messages, from your link, to show up in the menu are likely not possible as the messages seem to be encrypted and only viewable in a browser.

For Joystick, is there a way to match ES settings like Lr emulators?

Don't know, we should do one by one thing, otherwise it's too much ;-)

Btw.
About the config files.
If needed, we can use curl to get the raw files from pastebin.

Folly

@DTEAM

Just made some working code to edit the qt-config.ini file.

"□Enable Gles□□iniConfig \"=\" \"\" \"/home/$user/.config/borked3ds-emu/qt-config.ini\";iniSet \"use_gles\" \"true\"□□□□□printMsgs dialog \"NO HELP\"□"
"□Disable Gles□□iniConfig \"=\" \"\" \"/home/$user/.config/borked3ds-emu/qt-config.ini\";iniSet \"use_gles\" \"false\"□□□□□printMsgs dialog \"NO HELP\"□"

The functions are explained in the inifuns.sh script.

Another example would be :

"□Overwrite qt-config.ini from pastebin□□curl https://pastebin.com/raw/KXEmXpjQ > \"/home/$user/.config/borked3ds-emu/qt-config.ini\"□□□□□printMsgs dialog \"NO HELP\"□"

Seems the user right are still "pi", but it might be that we need to add chown to the command in order to keep the correct rights.

Folly

Added a useful config option.

Retrodade

@Folly Question, I just tried instaling Borked 3DS on my pi5 and I got could not successfully (home/pi/Retropie-setup/setup/temp/build/borked3ds/build/bin not found) How I solve this? thanks

Folly

@Retrodade

What kind of distro version are you running and is it 32 bit or 64 bit ?
Can you add your log to pastebin ?

Retrodade

@Folly pi5 64bit, where is the log? i went to look at dev/shm i dont see any error logs, must be another location? thanks

Folly

@Retrodade said in 3DS emulator for Pi users based on "Borked 3DS":

@Folly pi5 64bit, where is the log? i went to look at dev/shm i dont see any error logs, must be another location? thanks

In /dev/shm you can only find the runcommand.log and not the RetroPie-Setup logs.

RetroPie-Setup gzipped logs are here :
/home/pi/RetroPie-Setup/logs

Find the one from when you tried to install Borked.
It should be the latest, if you didn't do anything else..
These logs can be read with the command zcat, like suggested by @gvx64 in post 6.
Pipe to the command more to pause the output like this :

zcat '/home/pi/RetroPie-Setup/logs/rps_2025-xx-xx-xxxxx.log.gz'|more

(use "enter" and "q" to see next line or to quit)

To get the .log file you can either unzip the file like this :

gzip -d '/home/pi/RetroPie-Setup/logs/rps_2025-xx-xx-xxxxx.log.gz'

Or redirect the output of zcat to a new file :

zcat '/home/pi/RetroPie-Setup/logs/rps_2025-xx-xx-xxxxx.log.gz' > mylog.log