(2016-01-04, 01:51)Steveb Wrote: The snes9x and snes9x-next cores seem to be missing the ../resources/buttonmap.xml.
I just copied the resources folder from the beetle-bsnes core to the snes9x and snes9x-next cores and they seem to working ok now.

(2016-01-04, 02:16)cfetzer Wrote: Ups, I missed those files when making the two cores compatible again with recent RetroPlayer versions.
Created PRs for it so that it gets fixed with the next build: https://github.com/kodi-game/game.libretro.snes9x/pull/4 and https://github.com/kodi-game/game.libretro.snes9x-next/pull/3

(2016-01-05, 02:26)Heat Wrote: -snes9x and snes9x next do not recognize input, default configuration is seen.

(2016-01-05, 02:26)Heat Wrote: -Trying to start Super Mario World on a zip file with snes9x makes kodi crash. Trying some other zipped games didn't make kodi immediately crash, but if I stopped the game it crashes. Games that didn't even start were: Super Mario World (.smc), Donkey Kong Country (.sfc), Goof Troop (.sfc). Snes9x next didn't have this problem.

(2016-01-05, 02:42)garbear Wrote: Can you open an issue at game.libretro.snes9x issues? Debug logs are helpful. This will give us a good place to consolidate per-core issues.

(2016-01-02, 21:40)charlie0440 Wrote:

(2016-01-02, 18:56)a1rwulf Wrote: @charlie0440 I can reproduce the issue with the analog stick now.
Unfortunately I can't fix it easily and will have to start from scratch on my linux machine.

Glad you found the issue. Shame its not an easy fix. Will be greatly appreciated if you manage to fix it. n64 is my favourite platform for retroplayer

(2016-01-08, 03:13)Shinoby92 Wrote: why isn't there any android build?

(2016-01-08, 07:55)zachmorris Wrote: A few bugs I believe I've ran across with the latest build as far as input goes:
1) PS Controllers dont map the L1/L2/R1/R2 buttons as expected. They're included in the configure input page, but when I launch a game and hit say the Cross button it registers. The log shows:
game.controller.ps feature [ cross ] released
but when I press L1/R1/L2/R2 they don't register and I get something like:
game.controller.default feature [ righttrigger ] released

(2016-01-08, 07:55)zachmorris Wrote: 2) I think SNES left and right bumper are swapped. I ran across a homebrew suite of roms for controller testing and what the 'game' is registering as left and right are opposite of what Kodi maps.
I hit the left bumper, Kodi registers:
game.controller.snes feature [ leftbumper ] released
but the right bumper shows toggled in game.

(2016-01-08, 07:55)zachmorris Wrote: 3) Not really sure if this is a bug or not. I'm using a PS3 controller and mapped the default/Kodi controller along with NES. I'm playing a mashing games type game for NES which only has two buttons and accidentally hit triangle (not mapped for the NES controller), the default controller mapping fires and my screen view mode is changed inadvertently. Is it possible to inhibit the other non-mapped buttons from triggering when its currently being used in a different core (except maybe the GUIDE button that brings you back to Kodi)

(2016-01-06, 12:32)a1rwulf Wrote: OK, I found the root cause - not sure where's the right place for the fix, have to talk to garbear.

Our buttonmaps for analog axis look like this: https://github.com/kodi-game/peripheral.joystick/blob/master/peripheral.joystick/resources/buttonmaps/xml/linux/Xbox_360_Wireless_Receiver_15b_8a.xml#L59

If you change the analogs to look like below, the analog stick will work in n64:

Code:

<feature name="analogstick">
                <up axis="-1" />
                <down axis="+1" />
                <right axis="+0" />
                <left axis="-0" />
            </feature>

Hope this helps for now.

(2016-01-06, 20:27)a1rwulf Wrote: Regarding your OE builds:
Be careful, the platform lib of kodi was renamed and I've been changing stuff in game.libretro and peripheral.joystick.
That means if you bump peripheral.joystick for example you'll also have to bump all other libs - just to save you some time.

(2016-01-08, 07:55)zachmorris Wrote: A few bugs I believe I've ran across with the latest build as far as input goes:
1) PS Controllers dont map the L1/L2/R1/R2 buttons as expected. They're included in the configure input page, but when I launch a game and hit say the Cross button it registers. The log shows:
game.controller.ps feature [ cross ] released
but when I press L1/R1/L2/R2 they don't register and I get something like:
game.controller.default feature [ righttrigger ] released

(2016-01-08, 07:55)zachmorris Wrote: 2) I think SNES left and right bumper are swapped. I ran across a homebrew suite of roms for controller testing and what the 'game' is registering as left and right are opposite of what Kodi maps.
I hit the left bumper, Kodi registers:
game.controller.snes feature [ leftbumper ] released
but the right bumper shows toggled in game.

(2016-01-08, 07:55)zachmorris Wrote: 3) Not really sure if this is a bug or not. I'm using a PS3 controller and mapped the default/Kodi controller along with NES. I'm playing a mashing games type game for NES which only has two buttons and accidentally hit triangle (not mapped for the NES controller), the default controller mapping fires and my screen view mode is changed inadvertently. Is it possible to inhibit the other non-mapped buttons from triggering when its currently being used in a different core (except maybe the GUIDE button that brings you back to Kodi)

(2016-01-08, 21:27)garbear Wrote: I did this all by hand. As you can see above, there's a long chain of input, so somewhere along this chain I must have swapped a left and a right. Tracing this down is the same process as the PS controller issue.