+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27)
+---- Forum: Game Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=291)
+---- Thread: Beta Advanced Emulator Launcher - Multi-emulator frontend for Kodi (/showthread.php?tid=287826)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - TheTimeWalker - 2019-01-20
Not quite, you're starting an activity from an app. That means you have to specify the activity that's been programmed in the app:
Sanshiro Yabause is called org.uoyabause.uranus but the action to start an emulator is org.uoyabause.android.Yabause
Retroarch is called com.retroarch but the action to start an emulator is .browser.retroactivity.RetroActivityFuture
Every app is different and every app needs different arguments! It's like when I'm saying retroarch.exe -startNES -ROM %file% or yabause.exe -goemulator -FILE %rom%.
You can't just drop in replacements like you did, you have to check what arguments every emulator needs. The best way would be to search around or check the XML files from chrisism
You should use the first example I've given which would come out as:
start --user 0 -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -e ROM "%rom%" -e LIBRETRO /data/data/com.retroarch/cores/[CORE .so FILE] -e CONFIGFILE [retroarch settings folder]/retroarch.cfg -e IME com.android.inputmethod.latin/.LatinIME -n com.retroarch/.browser.retroactivity.RetroActivityFuture
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Shadow128 - 2019-01-20
Hi there
first I've to say, great work!
I'm using AEL since a few days, and it works really good to start RetroArch with the selected ROM (OS is Win10).
But I've one question, which is going more to RetroArch, but maybe someone can help me.
After selecting the ROM RetroArch is starting - no problem.
But if I want to quit the game I select "close content" and I see the RetroArch menu.
It is possible to completely quit RetroArch with "close content"?
Or another way to go directly back to Kodi?
Thanks for a suggestion :-)
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - C0mm0tari64 - 2019-01-20
Hi so this is exactly the add-on I need and it nearly works, it finds the Lnks and populates the directory, and they all launch with no issues, but it wont scrape Artworks at all, just gives a notification "No Artwork Found" - I'm running 18 Leia, as using the Netflix Add-on, I tried 17.6 previously and had the same issue, I thought maybe updating to 18 would magically fix my issue, is there a specific option, config to use when using Lnks for PC games? BTW these are common games like Arkham Knight, Skyrim, Tomb Raider, Moto GP, etc... I've confirmed they are indeed on Moby Games & The Games DB, and the add-on seems to connect, it starts the Scraping Process and goes through the Games 1 by 1, but fails to download anything at all.
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - C0mm0tari64 - 2019-01-20
Nevermind, finally found a part of this thread that indicates a API change so things are currently Broken, waiting on next release.
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - filigran - 2019-01-23
I tried using the retroplayer cores, but reverted back to the .emu emulators by Robert Broglia because I like them better.
I have one issue though, which is really why I tried retroplayer at all: I cannot get them to launch directly to the rom anymore. It just launches to the main app screen.
This used to work, but I guess something changed in android 8 Oreo?
This is the line I'm using to launch SNES roms:
Code:
/system/bin/am start -n com.explusalpha.Snes9xPlus/com.imagine.BaseActivity --user 0 -a android.intent.action.VIEW -eu Uri "file://%ROM_PATH%"but instead of launching the Uri/rom it just goes to the main screen.
Do I have to provide something else, or has something changed in the way they interpret command line arguments perhaps? This is the line I find all over the web, but it won't work anymore...
Tried contacting the dev, but no response unfortunately.
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2019-01-23
@filigran Why you don't use the official Retorarch for Android? A few post earlier some user posted a working configuration and you have some more configurations for Android on the AEL Asset Library.
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - filigran - 2019-01-23
(2019-01-23, 11:13)Wintermute0110 Wrote: @filigran Why you don't use the official Retorarch for Android? A few post earlier some user posted a working configuration and you have some more configurations for Android on the AEL Asset Library.Yeah, I know, and I've tried it. But I find it less smooth than the .emu emulators. Image is a little choppy (NES, not sure which core I used atm), and the UI is extremely clunky. Old habits I guess.
Probably something that can be fixed with settings for retroarch.
I guess I will have to get used to it, because getting the .emu apps to work seems to be a lost cause.
Found this line, same thing, goes to main menu:
Code:
am start --user 0 -a android.intent.action.VIEW -n
com.explusalpha.Snes9xPlus/com.imagine.BaseActivity
-d "file://{file.path}"RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - filigran - 2019-01-23
I tried your suggestion; using retroarch.
Not the easiest task though.
0.9.7 doesn't work with the Shield (the os.system launching thingie).
Found in the forums I should use "0.9.8", but that link gives me a 404.
Found chrisisms post to download https://github.com/chrisism/plugin.program.advanced.emulator.launcher/tree/feature/refactor_to_repositories instead. That gives me a "global name 'ROM' is not defined", and no roms added to the launcher, probably due to the 0.10.0 changes.
So, I solved it like this, for future reference for anyone else running a Shield TV on Oreo 8.1:
Code:
1. Install the 0.9.7 official version
2. Edit /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.program.advanced.emulator.launcher/resources/main.py (i use Mobaxterm to connect to my Shield through SSH, then edit it that way, adb is an alternative (there are other guides for that)).
3. Find line 7487: "elif sys.platform.startswith('linux'):"
4. Edit line 7490 and remove the hash and the blank space after ("# ") to uncomment it. Make sure it lines up with everything else indentation wise (hence removing the blank space too, python might be picky), this line: os.system('"{0}" {1}'.format(application, arguments).encode('utf-8'))
5. Comment out the lines starting from 7495 to 7503 (everything in the "new way of doing things" block)
6. Save file and make sure it's uploaded to the shield if edited remotely.
7. Add your launcher as usual, using the line posted in the assets (https://github.com/Wintermute0110/AEL-asset-library/blob/master/Launchers%20XML%20Android/NES%20-%20Retroarch%20(Android).xml - substitute your core and what not, of course) and retroarch should launch.Now to the other task: making retroarch do things my way.
Keep up the great work guys, AEL is awesome, and 0.10.0 will probably be even better once finished!
PS: if someone knows why my .emu launchers won't work using the old approach, please let me know.
DS.
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - ErAzOr2k - 2019-01-24
is this addon compatible with Estuary MOD V2?
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - denseye - 2019-01-25
is this project still under development ?
I don't see any commit in the github since 2 months
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - JamesMP - 2019-01-26
Wintermute0110 is the dev he just posted here 2 days ago and has mentioned he is still working on it and that he was gone for the holidays
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2019-01-27
(2019-01-24, 20:35)ErAzOr2k Wrote: is this addon compatible with Estuary MOD V2?
AEL is compatible with all skins. However, if a skin supports AEL you will get more metadata and artwork displayed (AEL specific views), that's is.
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - Wintermute0110 - 2019-01-27
(2019-01-25, 13:17)denseye Wrote: is this project still under development ?
I don't see any commit in the github since 2 months
Project is under development. Development time, though, strongly depends on my free time and how real life goes. AEL 0.10.0 is somewhat behind schedule but it is under way.
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - dmakk - 2019-01-27
Hi Wintermute, I'm looking to change the text in my parent/clone from "x clones" to "x games" for aesthetic purposes. Can you point me to what code I'd need to change to do this? I don't update often, so I wouldn't mind doing this manually.
RE: Advanced Emulator Launcher - Multi-emulator frontend for Kodi - mechevarria - 2019-01-28
(2019-01-08, 23:34)Wintermute0110 Wrote:Wow, really? Nice!(2019-01-08, 18:01)mechevarria Wrote: I am curious if Advanced Emulator Launcher is able to launch a PDF viewer (manuals) similar to the HyperLauncher Plugin. To show along with all the other artworkAt the moment no. However, Advanced MAME Launcher includes a PDF reader that is able to read PDF files composed of scanned images. I will port the feature from AML to AEL ASAP.
https://forum.kodi.tv/showthread.php?tid=258159&highlight=Hyperlauncher