(2016-01-19, 00:11)flipside101 Wrote:

(2016-01-18, 22:59)garbear Wrote:

(2016-01-18, 20:06)lrusak Wrote: I currently have the same issue on my RPi2. I'll ask garbear what he needs to look into it.

Debug logs please.

(2016-01-18, 01:41)longelf Wrote: The only issue I had was when playing a game, then pressing the Guide button to pause the game and switch back to Kodi, I couldn't navigate in Kodi any longer until I had quit the game entirely. To do that, I had to use the Tab key on the keyboard to regain functionality for the keyboard cursor keys. Once I had selected the Stop icon and pressed Enter, I could control Kodi again.

I'll look into this.

(2016-01-18, 16:33)longelf Wrote: Got ahead of myself slightly there, it seems the volume controls aren't working as expected in Yatse. Mute works fine, the volume up and down keys do bring up the volume slider on screen, but do not actually adjust the volume at all.

This should be fixed in the next round of builds.

(2016-01-18, 17:53)Mettbrot Wrote: I just tried OpenELEC-Generic.x86_64-6.0-retroplayer-20160118045753-r21784-gda8c8a0.tar and had a few freezes with it: http://sprunge.us/QAAD and http://sprunge.us/aOLM

It looks like those freezes are in Mupen64. N64 support is still highly experimental. Can you try different plugins in Mupen64's add-on settings?

(2016-01-18, 17:53)Mettbrot Wrote: Also the input configuration is quite bumpy: When I want to start setting up the N64 controller layout I press "Enter" on the keyboard it always skips the A button (as if I pressed enter twice). Same goes for "X" on the PS3 controller.
When I managed to set it up somewhat properly and I start a game in mupen64plus I cannot use the set controls since kodi reacts to them as if I was in video mode or something.

I can't reproduce this since the erratic behavior went away. Is it still an issue? Can you post a debug log?

(2016-01-18, 19:41)flipside101 Wrote: Hi What version of windows are you running, im on 10 and I've been trying for a while .windows sees it and all tests show the controller working but I can't get it to be seen in KODI

Can you post a debug log?

@garbear log file from my windows 10 install - http://xbmclogs.com/pcznrqo8u

I'm Still getting DPAD erratic button issues using the XB 360 wireless controller on the OE build. i will upload logs as soon as im able to access teh box

(2016-01-21, 08:04)doug Wrote: Started a bit of testing and found an easy bug to fix. When entering Games->Files, the context menu to play a file was not available. I had to add the following to my keyboard.xml:

Code:

<MyGames>
    <keyboard>
      <m>ContextMenu</m>
    </keyboard>
  </MyGames>

I don't see that section in the default keyboard.xml.

(2016-01-21, 08:04)doug Wrote: I started a few of my MAME games and many played okay. I'm still figuring out how to map my Ouya game controller but have the basics down. I am currently unable to quit a game using my controller or remote. I am using the webserver remote to stop the emulator for now. Thanks for that joystick fix!

(2016-01-21, 08:04)doug Wrote: I'll test over the coming week and post logs for any issues I get. Great job on integrating this!

(2016-01-21, 02:07)GOOCHY Wrote:

(2016-01-19, 00:11)flipside101 Wrote:

(2016-01-18, 22:59)garbear Wrote: Debug logs please.


I'll look into this.


This should be fixed in the next round of builds.


It looks like those freezes are in Mupen64. N64 support is still highly experimental. Can you try different plugins in Mupen64's add-on settings?


I can't reproduce this since the erratic behavior went away. Is it still an issue? Can you post a debug log?


Can you post a debug log?

@garbear log file from my windows 10 install - http://xbmclogs.com/pcznrqo8u

I'm Still getting DPAD erratic button issues using the XB 360 wireless controller on the OE build. i will upload logs as soon as im able to access teh box

I got the newest OE build installed and have this same issue as well. I can map all buttons with an XBOX 360 wireless controller but when I go to input the directional pad buttons I press "Up" and it immediately skips over "Down", I press "Right" and it immediately skips over "Left". Other buttons seem to input just fine. I thought it might be because one of my XBOX 360 controllers might have a D-pad that is acting wonky but it does this for both of my controllers.

Edit: Appears to have the same behavior with a DS4 controller paired via Bluetooth to my Kodi box (Chromebox). Connected via USB seems to work without issue.

(2016-01-21, 09:29)garbear Wrote: good find! shall I make this change or do you want to PR it?
...

We need a way to have a game add-on use the entire controller, but still deliver input to Kodi. Maybe allow button combos in joystick.xml? I think we have support for long presses, what about holding guide for 1s? and what about the majority of controllers that are lacking buttons?

(2016-01-21, 18:35)grumpygamer Wrote: @garbear

first post -> added Picodrive
I checked the "emulator matrix" it says "In progress". Do we have to consider that "matrix" a little bit outdated or is Picodrive in a non working/bugged form and will be updated later?

(2016-01-22, 20:54)OurJermain Wrote: My tv remote is not working with the latest rp2 build. One before that was working fine.