'Direct Input' from a belkin n52te to Innerspace

I'm new to using innerspace, and I've only just got it set up and working with my 3 characters in Everquets 1.

As I am just now I have all my commands for my 2 boxs setup as a 2 button press on my n52te to avoid any accidental commands going to my mains window. However the n52te can output 'Direct Input's, and I was wondering if anyone knew to setup Innerspace to accept those as my send/hotkeys?

1. Set up each of the buttons as a Direct Input button -- each direction on the D-Pad should count as well, assuming the n52te works essentially the same way as the n52.
2. Save this link: http://lavishsoft.com/downloads/mods/buttontest.iss to the Scripts folder in your Inner Space installation.
3. If you have not launched Inner Space with the n52te plugged in, do so now, and then exit Inner Space (so the file for the next step is saved with the n52te info)
4. In notepad (or text editor of choice), open the file InputDevices.XML in your Inner Space folder
5. Right click the running IS icon in the system tray and select Console
6. In the Uplink window, there should now be a window that says Console. It might be behind another window (e.g. the Patcher window). Click on the Console window and type in
   Code:

   ---

   run buttontest

   ---

7. Push each button on your n52te. Each button that gets pressed should say some output in the Console window, like Button=Button 1, Position=TRUE. The "Button 1" corresponds to the settings that appear in the part of InputDevices.XML that applies to your n52te. For each one, replace "Button 1" (or whatever it says) in InputDevices.XML with a different name. Make it concise and as obvious as possible, and it must not start with "Button" or conflict with other key names (so you can't use 1, 2, 3, 4, etc). So for example, you could use N1 for the button labeled 1 on the n52 itself.
8. Exit Inner Space, and THEN save InputDevices.XML -- or Inner Space will overwrite it.
9. If you launch Inner Space again, and run the buttontest script again, and hit the buttons again, it should now output the names you specified for the buttons. You can then restart ISBoxer, and it will have these buttons available for hotkeys!
10. When you're done, paste the filled in InputDevices.XML section for the n52te here so that the next person can just copy/paste and not have to run the script, as long as they use the same order of DirectInput buttons you configured (maybe specify the order of your DI buttons as well) :)

Thank you very much that was incredibly helpful, and exactly what i was looking for and didn't know how to search for. :D


This is a copy/paste of what i think is the appropriate section of InputDevices.XML, if not i'll have another bash at posting the right bit.




Thanks again.

Quote:

---

<Set Name="BEEF-FEED Virtual Hid Device (31-input)">

<Set Name="Buttons">

<Setting Name="44">n52te DI 1</Setting>

<Setting Name="45">n52te DI 2</Setting>

<Setting Name="46">n52te DI 3</Setting>

<Setting Name="47">n52te DI 4</Setting>

<Setting Name="48">n52te DI 5</Setting>

<Setting Name="49">n52te DI 6</Setting>

<Setting Name="50">n52te DI 7</Setting>

<Setting Name="51">n52te DI 8</Setting>

<Setting Name="52">n52te DI 9</Setting>

<Setting Name="53">n52te DI 10</Setting>

<Setting Name="54">n52te DI 11</Setting>

<Setting Name="55">n52te DI 12</Setting>

<Setting Name="56">n52te DI 13</Setting>

<Setting Name="57">n52te DI 14</Setting>

<Setting Name="58">n52te DI 15</Setting>

<Setting Name="59">n52te DI 16</Setting>

<Setting Name="60">n52te DI 17</Setting>

<Setting Name="61">n52te DI 18</Setting>

<Setting Name="62">n52te DI 19</Setting>

<Setting Name="63">n52te DI 20</Setting>

<Setting Name="64">n52te DI 21</Setting>

<Setting Name="65">n52te DI 22</Setting>

<Setting Name="66">n52te DI 23</Setting>

<Setting Name="67">n52te DI 24</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="Directional Pads">

<Setting Name="24">Hat Switch</Setting>

</Set>

---

Looks right to me, but that's interesting that they don't use a real vendor ID or product ID, let alone device name ("Virtual Hid Device"?! wtf Belkin) for it. And by interesting I mean really bad.