-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in Pegasus,How to write running commands for each Game console #21
Comments
Hi, I have tried Pegasus in GA as an alternative to AttractMode, so I know it works. I even hard quite a hard time to make it work for both X and KMS but this is solved as of now on my testing rig. As I tried it after using EmulationStation, Pegasus automatically imported my ES emulators configuration files + metadata. So I didn't have to do anything specific. I wanted to write a script to import data from AM, I don't remember if it's finalized or not. |
I saw someone running Pegasus Frontend on GA in February this year |
I use Pegasus Frontend too,because Pegasus have many soruces about rom list,video,pic, IF you use groovymame launch:groovymame {file.path} |
Sorry I never gave a real answer for that issue. I strongly recommend you use galauncher.sh to start the emulator, and not call straight away the emulator. Some optimizations/checks/modules are run if configured (ledspicer for those with led uttons for example, switch the CPU governor to power mode etc ...)) |
I want use Pegasus Frontend,
in metadata.pegasus.txt
collection: MAME
extension: zip
launch: myemulator {file.path}
How to write running commands for each Game console
Can you make metadata.pegasus.txt for each console for GroovyArcade
Except for the game list section
The text was updated successfully, but these errors were encountered: