"Define Joystick buttons" not properly mapping menu buttons

[AceE012]

Hello, I recorded a youtube video (linked below) showing that when I "define joystick button" it does not save the settings and I am still able to access the misters "system settings" from the main OSD. I am confident I am doing this correctly but am a little uncertain if this keymapping only applies while in a game... Everything I have read leads me to believe that I can assign a new "menu" button when I define joystick controls. I tried this using Mr. Fusion version 2.10 but also tried in earlier versions to see if it was a recently implemented bug (issue existted in fusion 2.7 as well).

I am trying to prohibit controllers from accessing the Mister system menu. This will be in an arcade cabinet and I have it dumbed down as much as possible. If anyone knows any kind of work around that stops a controller from accessing the service menu please let me know. This issue breaks my use case.... thanks

https://youtu.be/s034I3P2oZo

[sorgelig]

There is no way to prohibit a system menu in Menu core. You come there by "back" button, so even you skip "menu" button, you still come there by "back" button.
There is kind of workaround for that if you will use last core boot feature, so you will skip menu core.

[AceE012]

There is no way to prohibit a system menu in Menu core. You come there by "back" button, so even you skip "menu" button, you still come there by "back" button. There is kind of workaround for that if you will use last core boot feature, so you will skip menu core.

That makes sense... Are all settings in this menu written to Mister.ini? If so I am thinking I can make this file read only thereby preventing anyone from changing system settings.

[sorgelig]

Mister.ini contains what OSD settings doesn't have.

[birdybro]

https://github.com/MiSTer-devel/Main_MiSTer/blob/master/MiSTer.ini#L354-L358

This option is what you probably want to use.

[AceE012]

https://github.com/MiSTer-devel/Main_MiSTer/blob/master/MiSTer.ini#L354-L358

This option is what you probably want to use.

This option only applies when you are in a game or core. This does not affect the menu.

I think my only work around is to not map a "back" button. The user would have to select "up one directory" to go back. Not the most elegant solution but they should not be able to access settings.... I can't think of anything else.

[birdybro]

The "B" button (positionally) works as a back button by default without a back button being specified pretty sure.

[sorgelig]

I'll think if kiosk mode can be implemented.
You may describe what would you like to prohibit, and then i will see what can be implemented.

[AceE012]

I'll think if kiosk mode can be implemented. You may describe what would you like to prohibit, and then i will see what can be implemented.

The system is already super stable and I used .MGL files for launching all of the console games. With this method there is not much that I am concerned about. When the games are launched there is already a menu lock so all of this is PERFECT. The only thing I think I need to lock people out of is the settings menu when in the main menu and not in a core.

The only other thing is if a game fails to launch it does put you into the cores menu which isn't good because changes can be made here too. This only happens if there is an issue with a game though and I plan to spend a ton of time going through every game and making sure it is stable.

The nice thing is that I can back up the SD card and if there is an issue just swap with a backup. This arcade will be going into a vacation house that I also rent the and it is shocking what tenants will screw with... This is the only reason I am trying my best to lock things down.

I have to note that I am honored to be speaking with the creator! Great work and thanks for caring so much!

[sorgelig]

So, in Menu core you basically want to have list of cores without switching to any other OSD screen?