1
General / Re: Snes9x and Flycast Primary Montior Position error
« on: March 20, 2023, 07:28:49 PM »
Hey all, I figured it out! Was user error as is often the case. Figured I'd reply to my post to help any other wayward arcade builder.
So, for Flycast and Snes9x, they both use flatpak to install and run. They typical command is like ' flatpak run com.snes9x.Snes9x "[rom path and filename]" '.
What I (incorrectly) did in AttractMode was setup the executable to be 'flatpack run com.snes9x.Snes9x' and then the command argument to be ' "[romfilename]" '. THIS IS WRONG AND WILL GIVE THE NOTES MONITOR ERROR AND A STRAIGHT RUN ERROR.
The *CORRECT* way to set this up is:
executable: flatpak
command argument: run com.snes9x.Snes9x "[romfilename]"
It's a "well duh" moment in retrospect, but the actual executable in this instances is just 'flatpak' so the rest need to be command arguments. It seems that the way that AttractMode pieces it together is really important in this sense even though the log in the terminal will look exactly the same as the erroneous way I had it.
Hope this helps someone down the line!
So, for Flycast and Snes9x, they both use flatpak to install and run. They typical command is like ' flatpak run com.snes9x.Snes9x "[rom path and filename]" '.
What I (incorrectly) did in AttractMode was setup the executable to be 'flatpack run com.snes9x.Snes9x' and then the command argument to be ' "[romfilename]" '. THIS IS WRONG AND WILL GIVE THE NOTES MONITOR ERROR AND A STRAIGHT RUN ERROR.
The *CORRECT* way to set this up is:
executable: flatpak
command argument: run com.snes9x.Snes9x "[romfilename]"
It's a "well duh" moment in retrospect, but the actual executable in this instances is just 'flatpak' so the rest need to be command arguments. It seems that the way that AttractMode pieces it together is really important in this sense even though the log in the terminal will look exactly the same as the erroneous way I had it.
Hope this helps someone down the line!