FAQ  •  Register  •  Login

[Input Device] Razer Nostromo Native Support

Moderator: MiRai

<<

Mellesande

Posts: 14

Joined: Fri Jul 26, 2013 11:36 pm

Post Mon Jul 29, 2013 2:41 pm

[Input Device] Razer Nostromo Native Support

I've read everything pertinent I can find on this topic and now I'm seeking feedback.

The Razer version of the Nostromo does not have the Direct Input option like its Belkin predecessors. Nor does it have the ability to "Clear All" like the Logitech devices. However it does have a really stubborn owner and Joystick 1-24 for most of its keys. Out of curiosity I mapped every button that would let me to its Joystick # counterpart. This turned out to be Keys 1-16 and the 8 positions of the DPad.

Now when I run the button script I get Button 01 - Button 24 (just like the list in the Input Devices GUI) and when I run the Lavish.ButtonTester I now get the Button # at bit ## results described (which I never got if the keys were mapped to anything else on the keyboard).

Is ButtonTester supposed to return "Button # at _____" where # runs sequentially starting from 1 regardless of which key you pushed when? Is it really the bit number that matters and that's why one of the posts said to press the keys in an order that makes sense so that you can describe the order?

If so, does that mean I just figured out how to force my will ... I mean get Direct Input from my Razer Nostromo? (Assuming of course that Lax can use it?)

These are the numbered normal buttons 1-16 on a Nostromo. (They are printed as such on the device.)

Code:
Device "Unnamed Device" 1532-0111 v=0x101 p=0x1 u=0x4 (r=1,l=12,i=12)
- Button 1 at bit 72 -- 1532-0111 (r=1,l=12)
- Button 2 at bit 73 -- 1532-0111 (r=1,l=12)
- Button 3 at bit 74 -- 1532-0111 (r=1,l=12)
- Button 4 at bit 75 -- 1532-0111 (r=1,l=12)
- Button 5 at bit 76 -- 1532-0111 (r=1,l=12)
- Button 6 at bit 77 -- 1532-0111 (r=1,l=12)
- Button 7 at bit 78 -- 1532-0111 (r=1,l=12)
- Button 8 at bit 79 -- 1532-0111 (r=1,l=12)
- Button 9 at bit 80 -- 1532-0111 (r=1,l=12)
- Button 10 at bit 81 -- 1532-0111 (r=1,l=12)
- Button 11 at bit 82 -- 1532-0111 (r=1,l=12)
- Button 12 at bit 83 -- 1532-0111 (r=1,l=12)
- Button 13 at bit 84 -- 1532-0111 (r=1,l=12)
- Button 14 at bit 85 -- 1532-0111 (r=1,l=12)
- Button 15 at bit 86 -- 1532-0111 (r=1,l=12)
- Button 16 at bit 87 -- 1532-0111 (r=1,l=12)


The DPad was a bitch because mine is so mushy but I ultimately got the bit numbers for each position even if I couldn't really get the pretty printout. Everything else about it was just like the items above.

Code:
NW - 88
N - 89
NE - 90
W - 91
E - 92
SW - 93
S - 94
SE - 95


These directions are based on the layout of the DPad in the Nostromo Config software and coordinates with the only position printed with an identifier being North.

So am I on the right path to getting my way?
<<

lax

User avatar

Site Admin

Posts: 7301

Joined: Tue Nov 17, 2009 9:32 pm

Post Mon Jul 29, 2013 3:57 pm

Re: [Input Device] Razer Nostromo Native Support

The "Button 1 at bit __" is saying Button 1 because it was the first one recorded, regardless of its position on your device, yes (which is why the buttons need to be pressed in a useful order). The bit number tells me how to identify the button from the device's data. The rest ells me how to identify the device and the correct data to check the bits from.

I can use the information you have provided in order to build in native support for your Razer Nostromo. Coming soon. :)
<<

Mellesande

Posts: 14

Joined: Fri Jul 26, 2013 11:36 pm

Post Mon Jul 29, 2013 4:45 pm

Re: [Input Device] Razer Nostromo Native Support

My husband, being the systems analyst that he is, just quizzed the hell out of me on this leading to another discovery.

Those bit numbers belong to the Joystick # assignment and not to the actual button. If I assign every Physical button Joystick 1 in the Config software they all register bit 72 in your the ButtonTester. So while it would still appear you can provide the support in ISBoxer, the extra step of the Joystick assignments will have to be carefully done by the owner to get the expected results.

Please note that the mouse wheel click can also be assigned a Joystick number. That means there are actually 25 assignable items and 24 assignments. So if I'm understanding all this correctly and you use the DPad for movement (like I do) you could leave the DPad with its default movement assignments and assign the 16 buttons to Joystick numbers and have leftovers that you could give one to the mouse wheel. All you'd have to do then is make sure you remembered which button was which assignment and pick that number from the drop down. Could you also then go into the Input Devices GUI and rename the buttons to keep them straight? So if you did as I described above and gave Joystick 17 to the mouse wheel you could rename Button 17 to like NOS:MW for easier selection in a drop down?
<<

lax

User avatar

Site Admin

Posts: 7301

Joined: Tue Nov 17, 2009 9:32 pm

Post Fri Aug 09, 2013 11:23 am

Re: [Input Device] Razer Nostromo Native Support

My apologies for the late response here. Yes, you can rename the buttons in the editor to help keep them straight.

Inner Space build 5896 (now the development build of Inner Space) includes native support for the Razer Nostromo, in Joystick mode. Buttons are named Nostromo-1 through Nostromo-16 and Nostromo-NW N NE W E SW S SE, by default. The DPad is expected to be 17-24 as in your post.

To try out this build, right click IS and select Patcher, check "Download development (test) patches" and then close and restart Inner Space to let it patch up

Return to Multiboxing Hardware

Who is online

Users browsing this forum: No registered users and 0 guests