FpseCE Forum

Hello, Finally got play store to install FPSE64 (whole lot of GP family sharing shenanigans there) and now it works amazing on my retroid pocket 2. I am trying to use the DIG frontend which has the setup for FPSE on there, but I can not get it to load any games within FPSE64. Can someone please check if I have any of the variables wrong for FPSE64? I will include the variables for FPSE that are included within DIG for reference.

FPSE64 (Not working):
Package: com.emulator.fpse64
Activity: com.emulator.fpse64.Main
File Path Key: path
Data Type: */*

FPSE (Stock):
Package: com.emulator.fpse
Activity: com.emulator.fpse.Main
File Path Key: path
Data Type: */*

Thank you,

let me check what's happening

Any tutorial ? I cannot get it discovering games ?

schtruck wrote:Any tutorial ? I cannot get it discovering games ?

here is a decent tutorial: https://www.maketecheasier.com/configur ... d-android/

You can also join the DIG frontend discord, I know the devs are more than happy to help. https://discord.gg/rM5cAuB4

debugged today and found since Android 10 the call from launchers is like a shortcut and not like previously intent between apps.

path is well set by DIG

what is missing then is settings for video mode :

to set software smooth you must add

glblit=true

but DIG doesn't allow us to add other params

so what i did is if no param is set but FPse is called from a shortcut then Software smooth video mode will be set by default

it will be available for Version 1.6 i should release shortly with really 30% of speedup.

if you want to test the beta version send me email at schtruck@gmail.com

schtruck wrote:what is missing then is settings for video mode :

to set software smooth you must add

glblit=true

but DIG doesn't allow us to add other params

so what i did is if no param is set but FPse is called from a shortcut then Software smooth video mode will be set by default

Thanks, I will wait for the public release. Though, from a programming perspective, shouldn't the per game or emulator settings be what sets the renderer? With the override in the params being prioritized over that built in param only when it is present?

Just food for thought from one engineer to another.

Also, the device in question was on Android 6 not 10.

you can set param in any order you want

path set to a string with full path of iso to run
glblit set to true to run FPse in software smooth mode
softopengl to true added to gliblit to run in High definition Software mode
etc...

i already gave params in the tutorial section

Launcher devs should add many possible param settings

Understood, but what I was referring to was make that an optional param in the frontend and let the preferences set in the app by the user take priority, unless specified in the launcher. Allows flexibility while not requiring users place the param in 2 places.