Go to Tools in the top, then on the bottom to Test and in the middle to Axes. Click start calibration, move all the axes fully, maybe click on pov hats and then move them all the way as well. After having done this, end calibration.
Setting up responsiveness curves / s-curve and deadzone
If you want to have custom curves first thing is to identify the name of the axis you want to apply the curve to; could do this in the tester, let's say you want to apply same curve on pitch and roll, they're recognized as X and Y axes. Then go to Profile/Axes/ Logical Axes and find the number of those axes; for this example they are number 1 and 2. Now in Physical Axes panel check the Eq box for axes 1 and 2 - this means the curve will get applied on these axes. If you want to modify the deadzone you could do it in the Logical Axes panel, under DzLo; if the 2D option is active the deadzone will get applied for both axes.
Now go to Response Curve panel and click on the large white box when the first row is marked. In the new window draw your preferred curve, but be advised that what you see is just half of the curve with the lower deadzone in the lower left corner (the invisible lower half is mirrored). When done click OK so the window will close. Do the same after you select the second row
When done press the Set button in the Action tab.
This way the curves will get permanently applied to your joystick.
Setting up the curves in the configurator is more precise than setting them up in game.
There's also another option to get the curves on. Let's say you want the standard, unmodified curve for general flight and another curve for dogfighting. In this case you'll have to leave the Eq boxes empty (unmarked), fill up the curves as explained above and set up a button that will activate the modified curves:select the Poll option on the left side, press the button you want to be the curve modifier and click on the blinking button on the chart. Set up that button as Curves. Make it Alternate if you want the curves to stay active after releasing the button; you could revert to original curves by pressing the button again. You could leave the Alternate action box empty if you want the curves to stay active only as long as the button is pressed. Check the axes numbers below for the axes you want to apply the curves to (in this case 1 and 2). As usual, press Set button at the end.
This way the curves are only temporary applied to your joystick.
Suggest values something like this for - classic S curve:
10% - 60
20 - 80
30 - 95
40 - 110
50 - 128
60 - 135
70 - 150
80 - 165
90 - 145
100 - 128
Gives finer control for 1st 50% of deflection, then high response (when you need to turn/thrust fast) in 2nd 50%, tapering off to normal response at max deflection.
Numbers themselves can be adjusted - if you want super fine control in the 10-30% zone put lower numbers.
Basically all values of 128 would be a flat response curve where moving 10% deflection gets 10% turn response etc.
Anything under is under-response (finer control) and anything over is quick-response at that level of deflection.
Import the pictures into one of the SVG files in Inkscape. Rearrange and copy / paste the boxes (the NXT EVO guide is easiest to edit, it has groups)
Export as a PDF in Inkscape
Open the PDF Adobe Acrobat. Go to Tools -> Forms -> Create. Import from the open PDF. Once they are there you will need to make slight corrections. You can copy / paste fields, resize and rename them. Double click for properties. Certain properties you can edit if you select all the fields. Make sure the fields are multiline.
Use the Configurator
In one of the newer versions of VKB device config you can view the device as a template by selecting the device and clicking the eye to the right as described in http://forum.vkb-sim.pro/viewtopic.php?t=7550 - a bit lower in the post you can find how to load a template ini file into the diagram
They link to an njoy google drive space, but I downloaded mine from the official site https://www.vkbcontrollers.com/pages/downloads - I am not sure how to generate the ini file though.
USB Settings
For some reason the sticks don't show the vendor name in device manager, but they do in Devices and Printers, which is annoying. However the VendorID is 231d
using VKB software VKBDevCfg can I see and therefore change the current VID and PID setting?" - No
I ended up using third party software USBDeview to view all installed connected USB devices on my system http://www.nirsoft.net/utils/usb_devices_view.html. Its very detailed and easy to sort.
Using this USBDeview I was able to sort my devices by the column for the VID. Then looking at VID (the Vendor Identification Number 231d is VKB's number) and deleted old entries that had different old disconnected PID's to the current active connection recognized by DCS.
Vendor Name not showing up in Windows
Because the OEM name of Joystick's is "Blank",so the control files been generated by DCS like this above.First character is "Blank",cause Windows bug,I can't rename the files.
In system "Regedit",the VKB joystick's OEM full name is " VKBsim Gunfighter MCG Ultimate ",or this "(blank) VKBsim Gunfighter MCG Ultimate(blank)".This is the reason why DCS will generate the wrong control files.The solution is to manually modify the OEM name, delete the first blank and the last blank in the regedit.I hope VKB can fix this in firmware.I dont know why they add 2 blanks in the name?How dare u?I also posted a topic in VKB forum,but no one reply,hope they can pay attention to this bug.
Elite Dangerous Keybindings no longer working after firmware update
The binding files can be found in C:\Users\<username>\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings
It's always a good idea to copy the custom bindings files to another name and edit those. In my case, VKBRobin.
In BindingLoadingErrors.log you can see which device is not recognised / found.
The device is something like "231D3201" - 231D is the USB VendorID for VKB Sim products. 3201 is the device ID. You can find the device ID in Show_HID.exe, where it will be shown in the form "231D/2301".
In VKBRobin.4.0.binds AND VKBRobin.binds you can then search for both devices, to find out which ID has changed and then find and replace the uncrecognised device ID with the new one after the update
