[zeuss-axis]

I'm looking for an alternative solution to REMOTEXBMC for using an Xbox1 Remote with XBMC for Windows. Any suggestions?

I currently have the Xbox Remote Dongle hardwired into a USB header, and everything seems to work fine, but if I edit button functions via keymap.xml, I run into issues: it doesn't recognize my changes.

If I change keyboard parameters in keymap.xml, they change as expected. However, any change to remote parameters = no results. To prove it isn't just my fat fingers to blame, I copied "Up" from <up>Up</up> to <down>Up</down>, the result of which should be obvious. Nope. Down still moves the cursor down. On the contrary, this same change in the <keyboard> section produced the expected results.

Ideas?

[WinterMuteAu]

Have you tried IR Suite ? http://forum.xbmc.org/showpost.php?p=199762&postcount=3 for some more details

[MarcelX]

There is a keymap.xml in de xbmc\system folder which seems to override the settings in the keymap.xml in the userdata folder. I renamed keymap.xml in the systems folder and now it behaves as expected. Although this might not be the preferred solution.

[kraqh3d]

It's supposed to be the other way around. The system/keymap.xml is the default. It's read in first. Then userdata/keymap.xml is read it and it's mapping overrides the default ones. Open a trac ticket with the details about what's not working. Be sure to attach a copy of your userdata/keymap.xml file. I assume you made your up/down switch to the global section?

[animemike]

I'm looking for an alternative solution to REMOTEXBMC for using an Xbox1 Remote with XBMC for Windows. Any suggestions?

I currently have the Xbox Remote Dongle hardwired into a USB header, and everything seems to work fine, but if I edit button functions via keymap.xml, I run into issues: it doesn't recognize my changes.

If I change keyboard parameters in keymap.xml, they change as expected. However, any change to remote parameters = no results. To prove it isn't just my fat fingers to blame, I copied "Up" from <up>Up</up> to <down>Up</down>, the result of which should be obvious. Nope. Down still moves the cursor down. On the contrary, this same change in the <keyboard> section produced the expected results.

Ideas?

hey mate did you use a tut on how to hardwire the Dongle as a USB or was it realy easy thinking of doing the same "if its easy that is "

[kraqh3d]

its relatively easy... the xbox1's proprietary connector is basically usb in a non-standard package. search google or xbox-scene.com.

[zeuss-axis]

Yeah, it's really not hard at all. There's a thousand diagrams around that show which wires correspond to which USB wires, and if you have an extra USB header cable laying around, most boards use the Gigabyte standard pin layout. Provided that you have (or are willing to make) a window on the front of your PC to mount the IR eye into, the result is a much cleaner solution than the dongle-based solution...

[zeuss-axis]

It's supposed to be the other way around. The system/keymap.xml is the default. It's read in first. Then userdata/keymap.xml is read it and it's mapping overrides the default ones. Open a trac ticket with the details about what's not working. Be sure to attach a copy of your userdata/keymap.xml file. I assume you made your up/down switch to the global section?

Yes, I only changed things in the <global> <keyboard> and <remote> sections.

To ensure I do it all correctly, can you point me in the direction of the FAQ on posting a traq ticket?

[zeuss-axis]

Have you tried IR Suite ? http://forum.xbmc.org/showpost.php?p=199762&postcount=3 for some more details

Okay, so I installed IRSuite, loaded the debug app and verified that my IR Codes are getting through, and replaced the IRSSMAP.xml file in the /system directory with the one available on the SVN...and nothing works in XBMC 14676.

...rebooted...and nothing.

Next step?

[animemike]

just done it all it works as in windows find it woot

now just to get XBMC to work with it

cheers mate

[kraqh3d]

http://trac.xbmc.org/

try to login. i think all the user registrations are duplicated there. if you cant login, then register again. once you're logged in, you'll see a "new ticket" option at the menu bar across the top.

what do you mean you replaced the IRSSmap.xml with the one in SVN? they should be the same. and you need to set up a new map based off whatever device name your remote is called. here's the transcript from my X10 lola remote in the IRSS debug client:

Connect
Received Message: "RegisterClient, Response, Success"
Received Message: "ActiveReceivers, Response"
Windows Messages: X10
Received Message: "ActiveBlasters, Response"

Received Message: "RemoteEvent, Notify"
X10 (X10CMD_ENTER)

In this case, the name of my device is X10 and the button I pressed is called X10CMD_ENTER.

You'll see in SVN I included an X10-Lola-IRSSmap.xml file. Take a look at that. PM me and I can help you set up a new mapping if that's what's required. The default IRSSmap.xml file only has a mapping for device "Microsoft MCE".

[animemike]

hehe i cant get it to work in XBMC too works on windows meida player 9 when using XBCDRC

Cheers