- 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.
- Save this link: http://lavishsoft.com/downloads/mods/buttontest.iss to the Scripts folder in your Inner Space installation.
- 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)
- In notepad (or text editor of choice), open the file InputDevices.XML in your Inner Space folder
- Right click the running IS icon in the system tray and select Console
- 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- 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.
- Exit Inner Space, and THEN save InputDevices.XML -- or Inner Space will overwrite it.
- 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!
- 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)
Connect With Us