However I'm running into some initial setup issues mostly revolving around the problem that I can't have the sticks plugged in before I run VKB Device Config. If the sticks are plugged in before running DevConfig it will quickly hang when I try to use the program. It LOOKS like it is going to work ... displaying the 2 sticks (1 left, 1 normal) in the top of the program and doing the "get/init device" on the sticks, but as soon as I try to click anywhere the software stops responding and eventually gets the dreaded "Application Not Responding" Windows dialog.
...
Summary of questions:
- Generally: Anyone seen this issue before and know what I need to do?
- Is the joysticks being on FW 1.96D but the software showing NJoy 1.96C any kind of problem?
- Do I need to find a way to just rip old devices out of my registry and try again?
- Should I just go back to Joystick Gremlin if I was comfortable enough with it? (prefer not to)
...
Details:
I've tried running as Administrator, that's not helping. I have swapped from directly connecting to my motherboard USB2 or connecting via a powered hub, same behavior. Most times if I only connect the sticks after running DevConfig it will work as expected (but not always, sometimes it stops responding and I have to redo the procedure again).
Doing the "connect sticks after starting program" still has issues with going not responsive. I -was- able to update firmware (sticks were 1.96.7 when I got them if I remember correctly, and are 1.96D now). However even though DevConfig shows the sticks at 1.96.D, the DevConfig title bar shows it as "NJoy firmware 1.96.C". Do I need to do another firmware upgrade? Note: I had the problem with app going unresponsive before the firmware updates as well.
I've tried rebooting a number of times with various changes to get things working and just not having any luck. One of the times I tried to load the app after a fresh boot I had an error pop up something along the lines of "module not found" or something similar.
I thought "maybe I'll just use Wizzo for now" but it seems like Wizzo doesn't do remapping and only sees 1 stick at a time. I've used Joystick Gremlin (with a set of TM 16000 FCS sticks) in the past but was recommended to stick with DevConf for these sticks for getting support.
I've had a number of controller type devices over the years. Off the top of my head: Steam Controller, PS4 via Bluetooth, Xbox 360 controller, dual Thrustmaster TM16000s. However none of those have been connected recently. I also have an EDTracker Wireless but the dongle hasn't been plugged in during this and I make a point of closing the EDTracker (and OpenTrack) software after each boot for now while trying to figure out my problem. I also made a point of uninstalling all Thrustmaster and Joystick Gremlin/vJoy software before even plugging the VKB sticks in.
...
System:
OS: Windows 10 Pro v. 1809 (updated last night)
Motherboard: MSI Z68A-GD80 B3
CPU: I7-3770K
RAM: 32GB DDR3
(yeah, it's an old PC, waiting on Zen 2 stuff ... I do have most recent motherboard drivers and am not having other system issues)
...
VKB Support Request Info
Retyping some of the above in the more concise format:
1 - Device model and version
Gunfighter mk2 Kosomsima dual (left and standard)
2 - Controller Firmware version
1.96D
3 - Number and type of springs used
Both are standard spring config (#20 springs)
4 - Тype of cams used
Right stick is stock config (2x #10 cams)
Left stick has #30 cam on Y, #10 (standard) on X
5 - If VKB original software is used, please always mention its version
VKB Device Config v0.90.19 (NJoy firmware v1.96.C)