<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DragonRise USB Driver Issue]]></title><description><![CDATA[<p dir="auto">The generic DragonRise based N64 controllers that you get off of ebay appear to have an issue with how their axes work. Currently they register Joystick movements in jstest in a really odd manner:</p>
<p dir="auto">DPAD-L: Axis -0<br />
DPAD-R: Axis +0<br />
DPAD-U: Axis -3<br />
DPAD-D: Axis +3</p>
<p dir="auto">Joystick-L: Axis -2 (Axis -0 Binary)<br />
Joystick-R: Axis +2 (Axis 0 Binary)<br />
Joystick-U: Axis -3 Binary<br />
Joystick-D: Axis +3 Binary</p>
<p dir="auto">As you can see,  the driver is currently interpreting Joystick X movement as both Axis 0 and 3, with 3 displaying the analog data, and 0 replicating the same input data but in binary form i.e. either fully press or no press. Unfortunately the Joystick Y movement is completely broken and only interprets binary Y movement and has no analog data at all. Reportedly this problem does not exist in Windows, although I am experiencing it on mac using both Joystick and Gamepad Tester and Controllers Lite (can't confirm the duplication, can confirm the input Axis being used), and haven;t been able to confirm.</p>
<p dir="auto">My question is- is this a driver issue, or is there something physically wrong with these controllers? I have two and both operate in a similar manner.</p>
]]></description><link>https://retropie.org.uk/forum/topic/5962/dragonrise-usb-driver-issue</link><generator>RSS for Node</generator><lastBuildDate>Tue, 11 Aug 2026 19:39:02 GMT</lastBuildDate><atom:link href="https://retropie.org.uk/forum/topic/5962.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 08 Dec 2016 09:16:00 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to DragonRise USB Driver Issue on Fri, 09 Dec 2016 10:59:43 GMT]]></title><description><![CDATA[<p dir="auto">The fix has now been applied:</p>
<p dir="auto"><a href="https://github.com/raspberrypi/linux/issues/1755" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/raspberrypi/linux/issues/1755</a></p>
]]></description><link>https://retropie.org.uk/forum/post/39510</link><guid isPermaLink="true">https://retropie.org.uk/forum/post/39510</guid><dc:creator><![CDATA[DancingPigeon]]></dc:creator><pubDate>Fri, 09 Dec 2016 10:59:43 GMT</pubDate></item><item><title><![CDATA[Reply to DragonRise USB Driver Issue on Thu, 08 Dec 2016 09:26:56 GMT]]></title><description><![CDATA[<p dir="auto">Also to note:</p>
<p dir="auto"><a href="https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/DragonRise_Inc.___Generic___USB__Joystick__.cfg" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/udev/DragonRise_Inc.___Generic___USB__Joystick__.cfg</a></p>
<p dir="auto">Note that the linux kernel driver for this controller was broken from<br />
kernel 4.4 until 4.9. With the broken driver the joystick axes<br />
numbers will be off. This can be fixed by reverting commit<br />
18339f59c3a6698ee17d32970c9e1e450b16e7c3 and rebuilding hid-dr.ko.</p>
<p dir="auto">I'm going to pull one apart tomorrow and see if I can see how the buttons are soldered. I haven't looked into which version of the linux kernel RetroPie currently uses- is it between 4.4 and 4.9?</p>
]]></description><link>https://retropie.org.uk/forum/post/39250</link><guid isPermaLink="true">https://retropie.org.uk/forum/post/39250</guid><dc:creator><![CDATA[DancingPigeon]]></dc:creator><pubDate>Thu, 08 Dec 2016 09:26:56 GMT</pubDate></item></channel></rss>