Kodi Community Forum
RetroPlayer Test Builds (updated for Nexus) - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Game support (https://forum.kodi.tv/forumdisplay.php?fid=292)
+--- Thread: RetroPlayer Test Builds (updated for Nexus) (/showthread.php?tid=173361)



RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-02-08

Builds for OSX, Android ARM and Android ARM64 posted!

EDIT: Do'h. Builds didn't pull in the latest commit. Rebuilding now.

EDIT2: Fixed


RE: RetroPlayer Test Builds (updated for Leia) - zachmorris - 2018-02-10

I played with this new build for a while today.  Here's some notes:

1)  My controller was not recognized in this alpha build (OSX).  It is recognized in v17.6, but not this latest alpha.  Testing the controller on the same computer with both versions installed (using the same userdata folder):

Kodi 17.6 (works)
xml:
13:19:24.801 T:123145311502336   ERROR: AddOnLog: Joystick Support: Device "PS® Ga`epad": can't find <controller> tag
13:19:24.836 T:123145311502336  NOTICE: Register - new joystick device registered on addon->peripheral.joystick/0: PS® Gamepad

RetroPlayer 18 alpha1 2018-02-08 (no input, not recognized as an available peripheral)
xml:
13:25:00.056 T:140735224840192   DEBUG: USB Device AttachTongueS® Gamepad, 336592896
13:25:00.057 T:140735224840192   DEBUG: USB Device Attach:Bluetooth USB Host Controller, 338690048

Here's what OSX provides for info on the gamepad for what its worth:
xml:
PS® Gamepad:
Product ID: 0x0268
Vendor ID: 0x054c  (Sony Corporation)
Version: 1.00
Speed: Up to 12 Mb/sec
Manufacturer: Gasia Co.,Ltd
Location ID: 0x14100000 / 6
Current Available (mA): 1000
Current Required (mA): 500
Extra Operating Current (mA): 0
2)  Settings work again for IARL!
3)  Context menus aren't working anymore (at least in my addon) - not sure if Kodi changed something for how context menu's are handled?

4)  Game systems that seemed to work well in conjunction with IARL (I only got about 1/3 of the way through available cores):

4DO - Worked as well as external retroarch.  Note that BIOS files had to be placed into ..path_to_userdata/addon_data/game.libretro.4do/resources/system

Atari Lynx - Worked with Handy

Atari Lynx - Black screen with Mednafen Lynx, no error message:
xml:
13:49:56.040 T:140735224840192    INFO: AddOnLog: Atari - Lynx (Beetle Handy): [Mednafen Lynx]: Samples / Frame: 1929.38071
13:49:56.040 T:140735224840192    INFO: AddOnLog: Atari - Lynx (Beetle Handy): [Mednafen Lynx]: Estimated FPS: 22.85708
13:49:56.040 T:140735224840192   DEBUG: SECTION:UnloadDll(/Applications/Kodi_Retroplayer.app/Contents/Resources/Kodi/addons/game.libretro/game.libretro.1.0.37.dylib)
13:49:56.040 T:140735224840192    INFO: ADDON: Dll Destroyed - Atari - Lynx (Beetle Handy)
Edit:  Worked after I realized BIOS was required in ..path_to_userdata/addon_data/game.libretro.beetle-lynx/resources/system.  This core did not show the "The Required Files cannot be found" window however.

FBA / FBA 2012 - Worked great with both respective game lists and cores (FBA and FBA2012)

SCUMMVM - Worked great - I think the reported error is resolved with SCUMMVM and they launched straight away

DOSBOX - Worked great - However for Win3.1 games, I needed to change the settings for the Machine Type to svga_s3, and for other games I had to set it back to vgaonly.  There was no easy way to do that, unless you went into Addons>My Addons>Game Addons>Emulators>DOSBOX>Settings.  Is it possible to be able to bring up the emulator settings from the quick menu that appears when a game is running?

Atari 2600 - Worked Great with Stella

Atari 7800 - Worked Great with ProSystem

Atary Jaguar - Worked as well as Retroarch does (buggy depending on the game)

Atari ST - The system starts, but I'm unable to get past the "Cant Load TOS file" window from the emulator, even after placing the tos.img file into ..path_to_userdata/addon_data/game.libretro.hatari/resources/system

Cave Story - Worked great with NXEngine

ColecoVision - Worked great with BlueMSX.  Note that Database and Machines folders/files had to be placed into ..path_to_userdata/addon_data/game.libretro.bluemsx/resources/system

C64 - Worked the same as Retroarch with Vice core.  Note that it takes a really long time to load the game if the default settings for 'Enable TrueDrive' is enabled.

Dinothawr - Worked great

Doom - Worked great

Game and Watch - Worked, but not with default IARL settings to attempt to launch the zipfile.  I had to change IARL to unzip the file, but it worked great after that.

Gameboy Advance - I could not get this to work.  Kodi gives me an error:  "The Required Files cannot be found".  Attempting to put the BIOS files into the correct folder:  ..path_to_userdata/addon_data/game.libretro.mgba/resources/system, etc does not resolve the issue.
EDIT:  This did work after restarting Kodi.  I guess it doesn't currently check to see if the BIOS is available at every game launch?

Gameboy and Gameboy Color - I could not get this to work.  Kodi gives me an error:  "The Required Files cannot be found".  Attempting to put the BIOS files into the correct folder:  ..path_to_userdata/addon_data/game.libretro.gambatte/resources/system, etc does not resolve the issue.
EDIT:  This did work after restarting Kodi.   I guess it doesn't currently check to see if the BIOS is available at every game launch?

I'll keep playing and post notes.  It's getting pretty darn good though  Laugh


RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-02-10

Awesome! Now that the new input system is done, it's just a matter of hunkering down and hammering out the bug fixes. I'll keep popping out builds as I tackle your list.


RE: RetroPlayer Test Builds (updated for Leia) - zachmorris - 2018-02-10

More notes on testing:

The in game menu:  Clicking reset option with the mouse or pressing enter when reset is highlighted not seem to do anything

In an addon in Kodi:  Clicking on the '..' to exit top directory does not work the first time.  Have to click it twice now.  Maybe this is different functionality in the new Kodi version?

Game Gear - Worked great (genesis plus GX)

Master System - Worked great (genesis plus GX and picodrive)

NES - Worked in Nestopia

NES - Crashed every time with FCEUm, log just before it crashes:
xml:
19:30:04.053 T:140735224840192    INFO: AddOnLog: Nintendo - NES / Famicom (FCEUmm): Frontend supports RGB565 - will use that instead of XRGB1555.
19:30:04.053 T:140735224840192   DEBUG: AddOnLog: Nintendo - NES / Famicom (FCEUmm): CORE: ----------------------------------
19:30:04.053 T:140735224840192   DEBUG: AddOnLog: Nintendo - NES / Famicom (FCEUmm): CORE: Library name:    FCEUmm
19:30:04.053 T:140735224840192   DEBUG: AddOnLog: Nintendo - NES / Famicom (FCEUmm): CORE: Library version: (SVN)
19:30:04.054 T:140735224840192   DEBUG: AddOnLog: Nintendo - NES / Famicom (FCEUmm): CORE: Extensions:      fds|nes|unf|unif
19:30:04.054 T:140735224840192   DEBUG: AddOnLog: Nintendo - NES / Famicom (FCEUmm): CORE: Supports VFS:    true
19:30:04.054 T:140735224840192   DEBUG: AddOnLog: Nintendo - NES / Famicom (FCEUmm): CORE: ----------------------------------
19:30:04.054 T:140735224840192   DEBUG: AddOnLog: Nintendo - NES / Famicom (FCEUmm): Settings port "1" (libretro port 0) to controller "game.controller.gameboy" (libretro device ID 1)

NES - Worked in BNES.  The first time I launched a game I had some very strange video artifacts.  Closed the game and couldn't recreate it no matter what game I launched.

NES - Worked great with QuickNES

Genesis - Worked great (genesis plus GX and picodrive)

SNES - Worked great (BSNES, SNES9X, SNES9X2010)

TG16 - Worked great (PCE Fast)

Lutro - Worked great

Magnavox Oddysey - Worked Great (O2EM)

MSX1 / MSX2 - Worked great after I updated the IARL default settings to unzip the rom (BlueMSX, I can fix this in IARL).

MSX1 / MSX2 - Black screen with fMSX.  Even after putting Machines/Databases folders in the correct folder.

NeoGeo Pocket Color - Worked Great

PCE SuperGrafx - Worked Great (SGX)

Quake - Crashed every time, log just before it crashes:
xml:
19:59:09.501 T:140735224840192   DEBUG: Failed to locate add-on for "Keyboard"
19:59:09.501 T:140735224840192   DEBUG: Failed to locate add-on for "Mouse"
19:59:09.501 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Settings port "1" (libretro port 0) to controller "game.controller.default" (libretro device ID 1)
19:59:09.501 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Libretro input bindings:
19:59:09.501 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): ------------------------------------------------------------
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_LEFT, Description: D-Pad Left
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_UP, Description: D-Pad Up
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_DOWN, Description: D-Pad Down
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_RIGHT, Description: D-Pad Right
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_B, Description: Jump
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_A, Description: Cycle Weapon
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_X, Description: Freelook
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_Y, Description: Fire
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_L, Description: Strafe Left
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_R, Description: Strafe Right
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_L2, Description: Look Up
19:59:09.502 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_R2, Description: Look Down
19:59:09.503 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_L3, Description: Move Down
19:59:09.503 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_R3, Description: Swim Up
19:59:09.503 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_SELECT, Description: Toggle Run Mode
19:59:09.503 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): Port: 0, Device: RETRO_DEVICE_JOYPAD, Feature: RETRO_DEVICE_ID_JOYPAD_START, Description: Menu
19:59:09.503 T:140735224840192   DEBUG: AddOnLog: Quake 1 (TyrQuake): ---------------------------------------------------------

Wonderswan / Wonderswan Color - Worked Great

SG-1000 - Worked great (genesis plus GX)

SG-1000 - Error message from Kodi (Internal Error) when launching with BlueMSX
xml:
20:02:14.495 T:140735224840192   ERROR: AddOnLog: MSX/SVI/ColecoVision/SG-1000 (blueMSX): [libretro]: Invalid device, setting type to RETRO_DEVICE_JOYPAD ...
20:02:14.495 T:140735224840192    INFO: GAME: ------------------------------------
20:02:14.495 T:140735224840192    INFO: GAME: Loaded DLL for game.libretro.bluemsx
20:02:14.495 T:140735224840192    INFO: GAME: Client: MSX/SVI/ColecoVision/SG-1000 (blueMSX) at version 1.0.0
20:02:14.495 T:140735224840192    INFO: GAME: Valid extensions: .cas .col .dsk .m3u .mx1 .mx2 .ri .rom .sc .sg
20:02:14.495 T:140735224840192    INFO: GAME: Supports VFS:                  no
20:02:14.495 T:140735224840192    INFO: GAME: Supports standalone execution: no
20:02:14.495 T:140735224840192    INFO: GAME: ------------------------------------
20:02:14.496 T:140735224840192   DEBUG: PERIPHERALS: Event poll handle registered
20:02:14.496 T:140735224840192    INFO: RetroPlayer: Opening: /Users/xxx/Library/Application Support/Kodi/userdata/addon_data/plugin.program.iarl/temp_iarl/007 James Bond (Japan) (v2.7) (Othello Multivision).sg
20:02:14.496 T:140735224840192   DEBUG: GameClient: Loading /Users/Xxx/Library/Application Support/Kodi/userdata/addon_data/plugin.program.iarl/temp_iarl/007 James Bond (Japan) (v2.7) (Othello Multivision).sg
20:02:14.682 T:140735224840192   ERROR: GAME - LoadGame() - addon 'game.libretro.bluemsx' returned an error: the command failed

Sega32X - Worked Great (picodrive)

SegaCD - Black screen and no errors if BIOS files were not in ..path_to_userdata/addon_data/game.libretro.picodrive/resources/system.  Worked great after the BIOS files were placed there.

VirtualBoy - Worked great

Sega Saturn (beetle saturn) - Did not work with default IARL settings, worked after changing the default to point to a cue file instead of an m3u file.  Retroplayer does not recognize m3u files as potential for playing.  Retroarch uses m3u files, particularly for multi disc systems, to launch games that contain bin/cue files.  IARL generates an m3u file for systems like these currently.  Maybe something to add at some point?
BIOS files were required in the folder ..path_to_userdata/addon_data/addon_data/game.libretro.beetle-saturn/resources/system

PS1 (medfaden psx) - Hangs application on launch, have to force exit
xml:
08:21:12.988 T:140735224840192   DEBUG: AddOnLog: Sony - PlayStation (Beetle PSX): CORE: ----------------------------------
08:21:12.988 T:140735224840192   DEBUG: AddOnLog: Sony - PlayStation (Beetle PSX): CORE: Library name:    Beetle PSX
08:21:12.988 T:140735224840192   DEBUG: AddOnLog: Sony - PlayStation (Beetle PSX): CORE: Library version: 0.9.44.1
08:21:12.988 T:140735224840192   DEBUG: AddOnLog: Sony - PlayStation (Beetle PSX): CORE: Extensions:      exe|cue|toc|ccd|m3u|pbp|chd
08:21:12.988 T:140735224840192   DEBUG: AddOnLog: Sony - PlayStation (Beetle PSX): CORE: Supports VFS:    false
08:21:12.988 T:140735224840192   DEBUG: AddOnLog: Sony - PlayStation (Beetle PSX): CORE: ----------------------------------
08:21:12.989 T:140735224840192   DEBUG: Calling TransferSettings for: Sony - PlayStation (Beetle PSX)
08:21:12.989 T:140735224840192   ERROR: AddOnLog: Sony - PlayStation (Beetle PSX): Kodi setting psx_dithering unknown to libretro!
08:21:12.989 T:140735224840192    INFO: AddOnLog: Sony - PlayStation (Beetle PSX): Invalid settings detected, generating new settings and language files
08:21:12.990 T:140735224840192    INFO: AddOnLog: Sony - PlayStation (Beetle PSX): Settings and language files have been placed in /Users/xxx/Library/Application Support/Kodi/userdata/addon_data/game.libretro.beetle-psx/generated/language/English
08:21:12.990 T:140735224840192   ERROR: AddOnLog: Sony - PlayStation (Beetle PSX): Kodi setting psx_enable_analog_toggle unknown to libretro!
08:21:12.990 T:140735224840192   ERROR: AddOnLog: Sony - PlayStation (Beetle PSX): Kodi setting psx_enable_multitap_port1 unknown to libretro!
08:21:12.990 T:140735224840192   ERROR: AddOnLog: Sony - PlayStation (Beetle PSX): Kodi setting psx_enable_multitap_port2 unknown to libretro!
08:21:12.990 T:140735224840192    INFO: Loading controller layout: /Users/xxx/Library/Application Support/Kodi/addons/game.controller.ps/resources/layout.xml
08:21:12.990 T:140735224840192   DEBUG: <motor> tag has no "label" attribute
08:21:12.991 T:140735224840192   DEBUG: Previous line repeats 1 times.
08:21:12.991 T:140735224840192   DEBUG: AddOnLog: Sony - PlayStation (Beetle PSX): Settings port "1" (libretro port 0) to controller "game.controller.ps" (libretro device ID 0)
08:21:12.991 T:140735224840192    INFO: AddOnLog: Sony - PlayStation (Beetle PSX): Controller 1: Unplugged

PS1 (PCSX rearmed) - Works both with and without BIOS files in ..path_to_userdata/addon_data/game.libretro.pcsx-rearmed/resources/system

ZX Spectrum (fuse) - Did not work with default IARL settings, had to update to unzip rom and then it worked (I can fix this in IARL).

MAME / Flavors of MAME - Couldnt test since it doesnt look like there are any available addon/cores currently.


RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-02-12

I've fixed a bunch of input bugs. I launched another round of builds, they'll be up tonight or tmrw.
(2018-02-10, 00:52)zachmorris Wrote: 1)  My controller was not recognized in this alpha build (OSX).  It is recognized in v17.6, but not this latest alpha.  Testing the controller on the same computer with both versions installed (using the same userdata folder):

Is peripheral.joystick present? Search a full log for "joystick". My initial round of builds omitted the add-on, but it should have been in the current posted ones.
(2018-02-10, 00:52)zachmorris Wrote: 3)  Context menus aren't working anymore (at least in my addon) - not sure if Kodi changed something for how context menu's are handled?

They work for me, both on IARL platforms and individual games. Can you try again on the builds I post tonight?
(2018-02-10, 19:04)zachmorris Wrote: The in game menu:  Clicking reset option with the mouse or pressing enter when reset is highlighted not seem to do anything

This should be fixed in the newest builds.
(2018-02-10, 19:04)zachmorris Wrote: In an addon in Kodi:  Clicking on the '..' to exit top directory does not work the first time.  Have to click it twice now.  Maybe this is different functionality in the new Kodi version?

I reproduced this once but now it seems to be working. I'll look into this tmrw. You could post a log snippet of this failure if you want.
(2018-02-10, 19:04)zachmorris Wrote: MAME / Flavors of MAME - Couldnt test since it doesnt look like there are any available addon/cores currently.

MAKE cores take too long to compile. I'll do some special builds once things are working better including these cores.  

Soon these core-specific errors will be lost in the thread. I want to start using Github Issues for this, and sync the wiki page with open/closed issues so we can track which cores are most reliable. Can you open issues at https://github.com/kodi-game? No rush, I want to get the main bugs fixed first before I put much time into core-specific problems.


RE: RetroPlayer Test Builds (updated for Leia) - Abbaskip - 2018-02-12

(2018-02-08, 09:07)garbear Wrote: PR is up: PR:13499

I'll post builds tmrw, starting with OSX, and then Android once I fix game add-ons. A PR in early December broke game add-ons on Windows, so Windows users are stuck on the 2017-12-04 build unfortunately.
 Is there any future for the Windows builds? Or are we stuck on this version for the forseeable future?


RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-02-12

New builds are up. Input regressions have been fixed. The OpenGL renderer is getting faster, but this is only enabled for Linux and GBM now. More platforms (including Android and OSX) to follow in the future.
(2018-02-12, 07:13)Abbaskip Wrote:
(2018-02-08, 09:07)garbear Wrote: PR is up: PR:13499

I'll post builds tmrw, starting with OSX, and then Android once I fix game add-ons. A PR in early December broke game add-ons on Windows, so Windows users are stuck on the 2017-12-04 build unfortunately.
 Is there any future for the Windows builds? Or are we stuck on this version for the forseeable future?  
  
It's not bright. I've only been able crash cores 100% of the time in always different locations. This will definitely need the attention of a windows dev.


RE: RetroPlayer Test Builds (updated for Leia) - zachmorris - 2018-02-13

My controller works with the new build, thanks. It looks like it was originally missing peripheral.joystick.

Context menus still dont work, and I'm guessing this is a Kodi thing vs. a Retroplayer thing. The context menus display, but nothing happens when they're selected.
I've asked about this in a seperate thread here, but it looks like when my addon runs a command via context menu such as:
python:
'XBMC.RunPlugin(plugin://plugin.program.iarl/update_xml/path_to_file.xml?tag_value=blah)'
It will execute plugin://plugin.program.iarl/update_xml/path_to_file.xml but then drop the argument 'blah' for some reason.  Running the same code in 17.6 doesn't have any issues.

The double click '..' parent directory is still present as well, and I'm guessing this is again a Kodi thing rather than a Retroplayer thing. The first time I select '..', I get:
xml:

HandleKey: return (0xf00d) pressed, action is Select
20:15:49.680 T:140735305183232 DEBUG: CGUIMediaWindow::GetDirectory (plugin://plugin.program.iarl/)
20:15:49.680 T:140735305183232 DEBUG: ParentPath = [plugin://]
20:15:49.682 T:123145304526848 DEBUG: CAddonDatabase::SetLastUsed[plugin.program.iarl] took 2 ms
20:15:49.689 T:140735305183232 DEBUG: Loading items: 97, directory: plugin://plugin.program.iarl/ sort method: 0, ascending: false
And the second time I select it I get:
xml:

HandleKey: return (0xf00d) pressed, action is Select
20:16:18.331 T:140735305183232 DEBUG: CGUIMediaWindow::GetDirectory (plugin://)
20:16:18.331 T:140735305183232 DEBUG: ParentPath =
20:16:18.331 T:123145309892608 DEBUG: CAddonDatabase::SetLastUsed took 0 ms
20:16:18.332 T:123145305600000 ERROR: Unable to find plugin
20:16:18.333 T:140735305183232 ERROR: GetDirectory - Error getting plugin://
20:16:18.333 T:140735305183232 ERROR: CGUIMediaWindow::GetDirectory(plugin://) failed
20:16:18.333 T:140735305183232 DEBUG: CGUIMediaWindow::GetDirectory ()
20:16:18.333 T:140735305183232 DEBUG: ParentPath =

I'll start opening issue's on github for Retroplayer stuff.


RE: RetroPlayer Test Builds (updated for Leia) - xodi - 2018-02-13

For Android, the XBOX ONE S wireless controller does not work at all. There is no any response for any button pressing, even left/right. I remembered it works fine in Krypton and I played some games with it in the IARL addon. I use the controller as the remote replacement for Android TV, it works fine, I'm curious why even the left/right button doesn't work.


RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-02-14

(2018-02-13, 23:39)xodi Wrote: For Android, the XBOX ONE S wireless controller does not work at all. There is no any response for any button pressing, even left/right. I remembered it works fine in Krypton and I played some games with it in the IARL addon. I use the controller as the remote replacement for Android TV, it works fine, I'm curious why even the left/right button doesn't work.
  
Can you try mapping the controller? https://kodi.wiki/view/HOW-TO:Configure_controllers

Can you upload a full debug log including startup and pushing some buttons?


RE: RetroPlayer Test Builds (updated for Leia) - xodi - 2018-02-14

(2018-02-14, 00:41)garbear Wrote:
(2018-02-13, 23:39)xodi Wrote: For Android, the XBOX ONE S wireless controller does not work at all. There is no any response for any button pressing, even left/right. I remembered it works fine in Krypton and I played some games with it in the IARL addon. I use the controller as the remote replacement for Android TV, it works fine, I'm curious why even the left/right button doesn't work.
  
Can you try mapping the controller? https://kodi.wiki/view/HOW-TO:Configure_controllers

Can you upload a full debug log including startup and pushing some buttons? 
After configuring the controller, it works. For the main stream game controller, why don't make this working out of box?
I have a difficult to get any log. Since Windows 10 RS3, the adb always crashes when I run it. I tried several versions of adb.exe, including the latest one from platform sdk, all of them crash. Without adb, I don't know how to get the log.


RE: RetroPlayer Test Builds (updated for Leia) - xodi - 2018-02-14

The button layout of Kodi controller profile is just as the XBOX controller, but the button seems not working as the XBOX controller. I configured the 'A/B/X/Y' buttons and also map the 'A' button as "Start", the 'B' button as "Back", but they don't work as expected. For example, in the Movie library, I pressed 'A', it supposed to play the movie, but nothing happened, and pressed 'B' also didn't navigate back, but pressed 'X' button did pop up a context menu.


RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-02-14

(2018-02-14, 02:18)xodi Wrote: After configuring the controller, it works. For the main stream game controller, why don't make this working out of box?

Working out of the box is the goal. I've put a lot of work into an expansive architecture for controller autoconfiguration. Only a few more pieces are needed until we have close to 100% controller coverage for all emulators. Without those pieces, however, manual configuration is required.

Can you follow the instructions here to share the button map you just created? https://kodi.wiki/view/HOW-TO:Share_button_maps

If adb isn't working, you might be able to use Kodi's File Manager to extract the button map.

I'll include the buttonmap in our builds so that you won't have to reconfigure whenever you reinstall Kodi. Otherwise, by our v18 release in a few months I hope to have 100% autoconfiguration working.


RE: RetroPlayer Test Builds (updated for Leia) - xodi - 2018-02-14

(2018-02-14, 02:35)garbear Wrote:
(2018-02-14, 02:18)xodi Wrote: After configuring the controller, it works. For the main stream game controller, why don't make this working out of box?

Working out of the box is the goal. I've put a lot of work into an expansive architecture for controller autoconfiguration. Only a few more pieces are needed until we have close to 100% controller coverage for all emulators. Without those pieces, however, manual configuration is required.

Can you follow the instructions here to share the button map you just created? https://kodi.wiki/view/HOW-TO:Share_button_maps

If adb isn't working, you might be able to use Kodi's File Manager to extract the button map.

I'll include the buttonmap in our builds so that you won't have to reconfigure whenever you reinstall Kodi. Otherwise, by our v18 release in a few months I hope to have 100% autoconfiguration working.     
I really appreciate your years of great work on this!

I don't know how to copy the file, but I can see its content with the Kodi File Manager. The file name is Xbox_Wireless_Controller_v045E_p02FD_11b_1h_6a.xml, the content is:

<?xml version="1.0" ?>
<buttonmap>
    <device name="Xbox Wireless Controller" provider="android" vid="045E" pid="02FD" buttoncount="11" hatcount="1" axiscount="6">
        <controller id="game.controller.default">
            <feature name="back" button="1" />
            <feature name="down" hat="h0down" />
            <feature name="guide" button="6" />
            <feature name="left" hat="h0left" />
            <feature name="leftbumper" button="7" />
            <feature name="leftstick">
                <up axis="-1" />
                <down axis="+1" />
                <right axis="+0" />
                <left axis="-0" />
            </feature>
            <feature name="lefttrigger" axis="+5" />
            <feature name="right" hat="h0right" />
            <feature name="rightbumper" button="8" />
            <feature name="rightstick">
                <up axis="-3" />
                <down axis="+3" />
                <right axis="+2" />
                <left axis="-2" />
            </feature>
            <feature name="righttrigger" axis="+4" />
            <feature name="start" button="0" />
            <feature name="up" hat="h0up" />
            <feature name="x" button="2" />
            <feature name="y" button="3" />
        </controller>
    </device>
</buttonmap>


RE: RetroPlayer Test Builds (updated for Leia) - garbear - 2018-02-16

New builds posted! Bunch of input fixes with zachmorris's feedback.

(2018-02-14, 05:19)xodi Wrote: I don't know how to copy the file, but I can see its content with the Kodi File Manager. The file name is Xbox_Wireless_Controller_v045E_p02FD_11b_1h_6a.xml, the content is:
  
I've created a pull request for your button map: https://github.com/xbmc/peripheral.joystick/pull/139

I'll get this in tomorrow's nightly so that Xbox One S controllers will work out-of-the-box.