(2017-06-28, 19:36)Powerhouse Wrote: Retroplayer is not complicated, there just isn't a lot of directions that are easy to understand at the moment. So let me help out a bit.

1. Download one of the builds from the first page of this thread (the ones from Garbear have everything basically setup already). I'm using the Windows version for comparison, and have an Xbox One controller, but have also used an Xbox 360 controller).

2. If you have a joystick (I suggest an Xbox 360, Xbox One, or Playstation controller), plug it in. It should be recognized by your OS.

3. Start Kodi 18 alpha (again the Garbear version).

4. If you have ROMS add them to the system, just like you would add Movies or TV shows (they should be in separate directories, but under a general ROMS folder. For example:
D:\ROMS\NES
D:\ROMS\Atari
D:\ROMS\SNES

5. Search for a game you want to play, and click it (no artwork when scrolling through your ROMS at this time though, so everything is very plain). You will be prompted for what core you wish to play this game with, choose any one you like. If something doesn't work, try a different one next time.

6. For an even better experience, use the Internet Archive ROM launcher (IARL) instead. https://forum.kodi.tv/showthread.php?tid=231339
You will need to install the ZachMorris repo to install this add-on. So add his repo (download the zip file, and add it manually to Kodi). Then from his Repo in Kodi, install the IARL.

7. Be sure to follow the Install Instructions https://github.com/zach-morris/plugin.program.iarl/wiki/0.--Installation, then the Setup section: https://github.com/zach-morris/plugin.program.iarl/wiki/1.--Setup With the setup section, start at Step 2 (unless you are currently using RetroArch). Step two is once you are in Kodi, and you need to make changes to IARL for the program to work correctly. One final thing, you need to RUN THE WIZARD in step 4, this is very important or you get errors when you try to launch any ROM.

8. Once the IARL is installed, you will have access to Tons of systems and thousands of ROMS. These have artwork, and even short video clips on some of them. I've played NES, SNES, MAME and SCUMM games, and all were very easy to launch and play.

Hope this helps anyone struggling with this out.

(2017-06-27, 16:16)cmiller1 Wrote: Would it be crazy to have a binary toggle or two in the settings for "use joystick.xml" and then advanced users can do everything from there?

(2017-06-28, 03:42)Domina Wrote: My suggestions:

Franchise or serie (Street Fighter, Mortal Kombat, Persona, Final Fantasy, The King of Fighters,...)
region (USA, Japan, Europe ...),
rating age (ESRB, CERO, PEGI,...) and
number of players (1 player, 2 players, support online multiplayer,...).

(2017-06-29, 02:18)garbear Wrote: How do you think the advanced settings should look like? Clearly we wouldn't even mention joystick.xml, because if we have alternative settings then we can drop joystick.xml entirely.

(2017-07-03, 12:33)sectune Wrote: garbear sensei, just wanted to ask here as we are nearing completion of alpha 1 Lea - is there any chance we can test out the android build with retroplayer in? Are there still difficulties in compiling it for android and some codebase missing? Thank you!

(2017-07-04, 13:18)CrispyXUK Wrote: Is there still an OSX build coming for the latest revision?

(2017-05-31, 22:18)cmiller1 Wrote: I really like just using a separate IR remote (I use the Apple one) to bring up the OSD from a game... and for controlling the rest of Kodi. Failing that, the many phone apps that can control Kodi work great for bringing up the OSD too. I fear that this is adding loads of complication just so people can use one single controller...

(2017-07-05, 21:01)FoxForceFive Wrote: I don't code, but surely a system where when you press the start button it pauses the game (as per usual) & if the button is held down instead of released it then opens the OSD isn't complicating things massively?

(2017-07-05, 21:01)FoxForceFive Wrote: If it does, then perhaps as was mentioned earlier, adding another button, something all pads have, like 'down' would be the answer, so pressing down & start together would open the OSD.

(2017-07-05, 21:01)FoxForceFive Wrote: Obviously this needs to be able to handle controllers with less buttons (original NES style comes to mind, with very few), so one simple shortcut of a long press or multiple buttons to open the OSD just seems to make more sense.

(2017-07-05, 21:14)garbear Wrote:

(2017-07-05, 21:01)FoxForceFive Wrote: I don't code, but surely a system where when you press the start button it pauses the game (as per usual) & if the button is held down instead of released it then opens the OSD isn't complicating things massively?

(2017-07-05, 21:01)FoxForceFive Wrote: If it does, then perhaps as was mentioned earlier, adding another button, something all pads have, like 'down' would be the answer, so pressing down & start together would open the OSD.

(2017-07-05, 21:01)FoxForceFive Wrote: Obviously this needs to be able to handle controllers with less buttons (original NES style comes to mind, with very few), so one simple shortcut of a long press or multiple buttons to open the OSD just seems to make more sense.

Can you try the latest build with the new Game OSD?



You can activate it by pressing Guide, holding Start, or pressing Select + X. Those three methods should cover most controllers.

(2017-07-05, 19:43)garbear Wrote: New builds uploaded for Windows x86, x64, and OSX. Includes the final Game Menu being merged to master today.