Using N52te device input

Hi there.

First of all, fantastic piece of software.
I used to multibox 5 years back using Keyclone, but this just gives so much more possibility!!

Any way,

I have an ol' Belking Nostromo N52te (powered by Razer) and saw it is supported as an input device for ISBoxer. This is great news as I'm having trouble running out of keys.
The bad news is; I'm not having it working. This is what I did:

1) Plug it in, start Inner Space
2) Using n52te editor to configure the buttons 1 through 14 as DI buttons (1 through 14).
3) Close InnerSpace, start IS Boxer
4) File > Edit Input Devices
5) There's 5 entries related to the n52te, but from another forum post and the looks of the entries (number and naming of buttons), the "Virtual HID Device 31-input" was my choice
6) "M" -> New Key Set -> Add
7) Select all the buttons from the list and press ">>" to add to list, "Save".
8) Now I expected to be able to find something related to these buttons in the list of keys in the hotkey selector - no luck.
9) I tried restarting, re-doing, etc. in various ways without luck
10) I also ran the buttontest in Inner Space console which registered the buttons seemingly just fine

Please advice!!

Thanks.

[lax]

Missed step:
6.5) Select each "Button 01" to "Button __" and rename them to not be "Button 01", because any button labelled "Button __" will not be listed in the Hotkey selector. I suggest prefixing them with N52, e.g. N52-1, N52-2, etc.

Thanks, I did that now.

I don't know if there is an easier way to rename them all rather than having to rename them individually.

Anyhow, now I wanted to test it out so I mapped the button on the N52te "04" which registers in buttontest as button 3, which I named N52-4 in the key set, as a replacement to a mapped key which was otherwise working on Ctrl + S.
I can select it from the hotkey list just fine, but when I then launch Inner Space and my character set, the button does nothing. Ctrl + S is unbound just fine.

Spamming all the keys on the N52te had no result either.

What could it be??

[lax]

I mapped the button on the N52te "04" which registers in buttontest as button 3

If it still registers in buttontest as button 3, then your renaming didn't work properly and this is why your Hotkey didn't work. You should make sure to close Inner Space out before saving your edits, then afterward you can launch Inner Space again and run the buttontest again and make sure it shows the same thing you entered in ISBoxer.

That's awfully strange, because I did in fact remember to close Inner Space before pressing "Save".

Just now I tried once again, closing Inner Space, and renaming the keys on both "sides" (as in default key set and my specified key set) and I renamed keys (different names) for all three related devices (Virtual HID devices 31-input, Belkin n52te 573-input and n52te 573-input).

Relaunching Inner Space and running buttontest still shows "Button x" for each of the buttons I press on the N52te.

Been trying all sorts of things now.

What should happen when I click "Save" in Input Device Editor?
If I could check if a config file is being written correctly, maybe.

If you would want to take a look, we can also try and arrange some Team Viewer or other desktop sharing.

[lax]

Clicking save will replace the data in InputDevices.xml. The correct device you're looking for may actually be listed as "BEEF-FEED Virtual Hid Device (31-input)"; this is what the original drivers incorrectly had it as and may still be the same.

"BEEF-FEED Virtual Hid Device (31-input)" is what I see too.

Do I need to "activate" my key set some where??

<Set Name="BEEF-FEED Virtual Hid Device (31-input)">
<Set Name="Buttons">
<Setting Name="44">Button 0</Setting>
<Setting Name="45">Button 1</Setting>
<Setting Name="46">Button 2</Setting>
<Setting Name="47">Button 3</Setting>
<Setting Name="48">Button 4</Setting>
<Setting Name="49">Button 5</Setting>
<Setting Name="50">Button 6</Setting>
<Setting Name="51">Button 7</Setting>
<Setting Name="52">Button 8</Setting>
<Setting Name="53">Button 9</Setting>
<Setting Name="54">Button 10</Setting>
<Setting Name="55">Button 11</Setting>
<Setting Name="56">Button 12</Setting>
<Setting Name="57">Button 13</Setting>
<Setting Name="58">Button 14</Setting>
<Setting Name="59">Button 15</Setting>
<Setting Name="60">Button 16</Setting>
<Setting Name="61">Button 17</Setting>
<Setting Name="62">Button 18</Setting>
<Setting Name="63">Button 19</Setting>
<Setting Name="64">Button 20</Setting>
<Setting Name="65">Button 21</Setting>
<Setting Name="66">Button 22</Setting>
<Setting Name="67">Button 23</Setting>
</Set>
<Set Name="Axes">
<Setting Name="0">Z Rotation</Setting>
<Setting Name="4">Y Rotation</Setting>
<Setting Name="8">X Rotation</Setting>
<Setting Name="12">Z Axis</Setting>
<Setting Name="16">Y Axis</Setting>
<Setting Name="20">X Axis</Setting>
</Set>
<Set Name="Key Sets">
<Set Name="M">
<Set Name="Buttons">
<Setting Name="44">N52-1</Setting>
<Setting Name="45">N52-2</Setting>
<Setting Name="46">N52-3</Setting>
<Setting Name="47">N52-4</Setting>
<Setting Name="48">N52-5</Setting>
<Setting Name="49">N52-6</Setting>
<Setting Name="50">N52-7</Setting>
<Setting Name="51">N52-8</Setting>
<Setting Name="52">N52-9</Setting>
<Setting Name="53">N52-10</Setting>
<Setting Name="54">N52-11</Setting>
<Setting Name="55">N52-12</Setting>
<Setting Name="56">N52-13</Setting>
<Setting Name="57">N52-14</Setting>
<Setting Name="58">N52-15</Setting>
<Setting Name="59">N52-16</Setting>
<Setting Name="60">N52-17</Setting>
<Setting Name="61">N52-18</Setting>
<Setting Name="62">N52-19</Setting>
<Setting Name="63">N52-20</Setting>
<Setting Name="64">N52-21</Setting>
<Setting Name="65">N52-22</Setting>
<Setting Name="66">N52-23</Setting>
<Setting Name="67">N52-24</Setting>
</Set>
</Set>
</Set>
<Set Name="Directional Pads">
<Setting Name="24">Hat Switch</Setting>
</Set>
</Set>

[lax]

Okay that actually shows the problem

Since you have created them inside a custom Key Set, you would definitely have to use an Input Device Key Set Action as part of some Mapped Key in ISBoxer, in order to activate the different Key Set. By default it will be using "Button 0" through "Button 23" as listed in the file. You don't need to set up Key Sets unless you actually want to rename them on the fly, e.g. to support different modes by changing the button names.

I would suggest just removing your custom Key Set, and just change the Default Key Set. Select each one in the list box on the left, and change the Control Name box.

And there we had it! Thanks.

Gosh that turned out to be problematic!