Open Bboy486 opened 2 years ago
Hi, could you post a lastrun.log that is generated right after you try to launch a game? (Launch Pegasus, start a game, close the game, close Pegasus, and post the file.)
Also it seems you've pasted the contents of an XML file directly into the metadata txt; it's likely not related to the launch issues, but you will probably not see the game details you expect. You can convert between formats here: https://pegasus-frontend.org/tools/convert/
I re-ran the xml (attached) metadata.pegasus.txt lastrun.log
And here is for Gamecube lastrun (1).log
Also just an FYI https://pegasus-frontend.org/tools/convert/ will error if the gamelist.xml file has an ampersand (&)
Thanks! It seem there is a typo in the launch command: you try to call org.citra.citra.emu
, but according to your first post, that should be org.citra.citra_emu
(note the underscore). This is why you get an ActivityNotFoundException
.
And here is for Gamecube lastrun (1).log
I think you might have posted the same file by accident, it's the same as the one before.
Also just an FYI https://pegasus-frontend.org/tools/convert/ will error if the gamelist.xml file has an ampersand (&)
Yeah, the XML files ES creates/uses tend to be not technically valid. I'll see if I can do some work on it.
Thanks! It seem there is a typo in the launch command: you try to call
org.citra.citra.emu
, but according to your first post, that should beorg.citra.citra_emu
(note the underscore). This is why you get anActivityNotFoundException
.
Well that makes sense. This brings up another question. The emulator loads but doesn't pass through to the game. Is there a step I missed to launch the game and not just launch into the emulator?
A new lastrun file is created after each launch of Pegasus; make sure you post the one created after you try to launch a game, as you can't see the error in the log otherwise.
In this case though I have a guess: could you try replacing file.path
with file.uri
in the launch command?
A new lastrun file is created after each launch of Pegasus; make sure you post the one created after you try to launch a game, as you can't see the error in the log otherwise. New Log That is what I did. Here is a new one. Just launched clicked on GameCube and a game and it crashed.
URI test This was on GameCube with file uri. Trying the same with 3DS just launched into the Emulator. lastrun.log
Ok, in this log I see two launches of Dolphin. The first one has the native file path, but I guess that is the "emulator loads but doesn't pass through to the game" case. The second one has {file.uri}
, but this field was only recently added to Pegasus, which is why you see the issue on the screenshot. Could you try updating to the latest version?
Updated to latest. New logs. Same crash. Also some emulators still don't launch into game. Let me know if you want a separate issue for that one.
Hm I think Android might not presenting you the last created log file. Take a look at the one attached at https://github.com/mmatyas/pegasus-frontend/issues/933#issuecomment-1020686263. If you search for Executing command
, you'll get two matches, and they tell what command ran with what kind of result. Now if I download the one in https://github.com/mmatyas/pegasus-frontend/issues/933#issuecomment-1021747164, I see no such lines, so I cannot tell what happened.
Also some emulators still don't launch into game. Let me know if you want a separate issue for that one.
Yeah, in general many apps that used to work before Android 11 now have troubles. This is often unrelated to Pegasus, but some apps do require a different launch command, and the community is still in the middle of figuring out the best combinations. You might have more luck on the Discord channel, perhaps someone has already run into the emulator issue.
Thanks what is the discord channel link?
On Wed, Jan 26, 2022, 10:36 AM Mátyás Mustoha @.***> wrote:
Hm I think Android might not presenting you the last created log file. Take a look at the one attached at #933 (comment) https://github.com/mmatyas/pegasus-frontend/issues/933#issuecomment-1020686263. If you search for Executing command, you'll get two matches, and they tell what command ran with what kind of result. Now if I download the one in #933 (comment) https://github.com/mmatyas/pegasus-frontend/issues/933#issuecomment-1021747164, I see no such lines, so I cannot tell what happened.
Also some emulators still don't launch into game. Let me know if you want a separate issue for that one.
Yeah, in general many apps that used to work before Android 11 now have troubles. This is often unrelated to Pegasus, but some apps do require a different launch command, and the community is still in the middle of figuring out the best combinations. You might have more luck on the Discord channel, perhaps someone has already run into the emulator issue.
— Reply to this email directly, view it on GitHub https://github.com/mmatyas/pegasus-frontend/issues/933#issuecomment-1022431792, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD53IKIPVOZ5MBEZC6RU2W3UYAWLFANCNFSM5MTU7S5Q . You are receiving this because you authored the thread.Message ID: @.***>
Sorry I should have seen that on the site. I have reached out but it looks like Android 12 just doesn't work well with pegasus
Did the issue get resolved? There have been also some updates to improve Android 12 support (eg. storage access), if it turns out that it was the problem.
No still doesn't work correctly
Did the issue get resolved? There have been also some updates to improve Android 12 support (eg. storage access), if it turns out that it was the problem.
Hello, one thing I noticed, and after this update I was able to run aethers2 from the command line, but only on the internal storage, when I put it on the sdcard it doesn't work, it gives an error, I even posted the error message on discord.
There have been no changes to the game launching, the new settings option only adds a way to ask permission for additional.directories, required by certain emulators. This shouldn't change the file's path – though this is Android so anything can happen. Will see if I can look into it.
Ok thanks. If I can provide any further logs or testing please let me know.
I realize that this is a pretty old issue at this point, but it was never marked as resolved and came across it when googling for my own issues with the metagen tool and the mainline dolphin emu off of the play store. the way I was able to get it launching was changing the following:
-a android.intent.action.VIEW --> -a android.intent.action.MAIN -e AutoStartFile "{file.path}" --> -e AutoStartFile "{file.documenturi}"
hopefully someone can double check that doesn't break anything else, and if not, update the metagen tool, and close the issue. Just for clarification this was with the RG505 running gammaos (android 12)
Hi, and thanks for reporting errors! You can help us locating the bug even more by providing detailed information in the sections below:
The issue
I went to https://pegasus-frontend.org/tools/metagen-android/ and downloaded the configs for each of my systems. I am testing Citra 3Ds and Dolphin.
I use Skraper to collect the needed media and then
I have two Citra emulators: org.citra.citra_emu and org.citra.emu. I can see these package names through APK Extractor. Pegasus sees my ROMs but when I go to launch the game in pegasus I receive an error:
Failed to run the launch command:
I have three dolphin emulators: org.mm.j, org.dolphinemu.mmjr, and org.dolphinemu.dolphinemu. I can see these package names through APK Extractor. Pegasus sees my ROMs but when I go to launch the game in pegasus I receive the following error: Warning "path to rom" is an invalid GCM/ISO file, or is not a GC/Wii ISO. The issue is it opens in all dolphin versions no issue.
System info
Android 10 on Galaxy Note 20 Ultra
Pegasus version
alpha15-85-gfff1a5b2, 2021-10-14
Pegasus log
You can find a log file with detailed information about the launch of Pegasus under the following locations:
<storage>/pegasus-frontend/lastrun.log
lastrun.log metadata.pegasus.txt metadata.pegasus.txtIf possible, please attach the file to this bug report.