Hi. Thanks a lot for your interest.
Encoders should work with any device (with virtual bus over USB and FW 2.17.9+), but LEDs need a definition file to be accessible. If you have not changed anything about the LED numbering after running autoconfig (i.e. adjusted external devices by hand), all it takes is to run the definer and enter the base device and modules in there. Default button, LED and encoder indices should work unless you remapped your buttons in VKBDevCfg or added shifts/mols to the encoders.
When you are done, there should be a file ending in .joystick.json in your output folder. Copy that to your mobiflight joysticks folder and things should work. The controller should now be selectable as an output device.
Currently I am not including a config for 1 SEM, 1 THQ and 1 FSM, since pretty much all combos sold by VKB have multiple THQs. Since it is a fairly badic GA combo though, I might include it in a later commit if the MobiFlight guys ask for revisions.
Edit: no need to build from source, there should be a github release on each project with prebuilt binaries. But some antiviruses may panic if tools from a private developer start doing low-level hardware access after being downloaded from the interwebz.
Encoder capabilities
Moderator: AdminGroup
Re: Encoder capabilities
Hi again and thanks for taking the time.
Still no luck I'm afraid. I removed all the source code builds and just went with your pre-built binary (10.2.2.2-VKB-5) as suggested. I recreated my joystick.json file and copied it into the Joysticks folder of the pre-built version. I turned on logging and can see my joystick.json file "VKBSim NXT SEM THQ FSM.GA" was detected (albeit with two warnings, not sure if that's relevant).
The only place I can see a reference to Output Device is on the "Display" tab in the Output Config Wizard screen. In the "Choose" dropdown it says "Output Device", but then the "Module" dropdown and the "Use type of" dropdown are both empty.
And that's it, there is no reference to this new joystick.json config anywhere. Am I even looking in the right places I wonder?
Still no luck I'm afraid. I removed all the source code builds and just went with your pre-built binary (10.2.2.2-VKB-5) as suggested. I recreated my joystick.json file and copied it into the Joysticks folder of the pre-built version. I turned on logging and can see my joystick.json file "VKBSim NXT SEM THQ FSM.GA" was detected (albeit with two warnings, not sure if that's relevant).
The only place I can see a reference to Output Device is on the "Display" tab in the Output Config Wizard screen. In the "Choose" dropdown it says "Output Device", but then the "Module" dropdown and the "Use type of" dropdown are both empty.
And that's it, there is no reference to this new joystick.json config anywhere. Am I even looking in the right places I wonder?
Code: Select all
07/03/2024 07:11:25(322): Checking for RELEASE update...
07/03/2024 07:11:26(983): Found a new version: 10.3.0.0 RELEASE.
07/03/2024 07:11:30(332): Loaded joystick definition for Alpha Flight Controls
07/03/2024 07:11:30(342): Loaded joystick definition for Bravo Throttle Quadrant
07/03/2024 07:11:30(343): Loaded joystick definition for Octavi
07/03/2024 07:11:30(344): Loaded joystick definition for Saitek Aviator Stick
07/03/2024 07:11:30(346): Loaded joystick definition for S-TECS MODERN THROTTLE MAX STEM
07/03/2024 07:11:30(347): Loaded joystick definition for S-TECS MODERN THROTTLE MAX STEM FSM.GA
07/03/2024 07:11:30(348): Loaded joystick definition for T.A320 Pilot
07/03/2024 07:11:30(349): Loaded joystick definition for VKBSim NXT FSM.GA
07/03/2024 07:11:30(351): Loaded joystick definition for VKBSim NXT SEM THQ FSM.GA
07/03/2024 07:11:30(353): Loaded joystick definition for VKBsim Gladiator EVO R
07/03/2024 07:11:30(354): Loaded joystick definition for VKBSim NXT SEM THQ
07/03/2024 07:11:30(355): Loaded joystick definition for WINWING FCU
07/03/2024 07:11:30(385): Loaded midiBoard definition for APC Key 25
07/03/2024 07:11:30(386): Loaded midiBoard definition for Intech Studio: AC
07/03/2024 07:11:30(387): Loaded midiBoard definition for MPD218
07/03/2024 07:11:30(388): Loaded midiBoard definition for MPK mini play
07/03/2024 07:11:30(389): Loaded midiBoard definition for nanoKONTROL2 1 SLIDER/KNOB
07/03/2024 07:11:30(390): Loaded midiBoard definition for X-TOUCH MINI
07/03/2024 07:11:30(600): Adding attached joystick device: CH Products IP Desktop Controller Buttons: 12 Axis: 3.
07/03/2024 07:11:30(636): Adding attached joystick device: VKBSim NXT SEM THQ FSM.GA Buttons: 128 Axis: 8.
07/03/2024 07:11:30(726): VKBSim NXT SEM THQ FSM.GA => Button 13 => PRESS => No config found.
07/03/2024 07:11:30(726): VKBSim NXT SEM THQ FSM.GA => Button 24 => PRESS => No config found.
07/03/2024 07:11:35(919): Finish looking up connected modules. No modules found.
Re: Encoder capabilities
Ooooh, I have success!
Inside the joystick.json file I removed the leading space in the InstanceName, restarted MobiFlight Connector and now the VKBSim joystick is showing correctly in Module dropdown in Output Device.
Thanks again...
John
Inside the joystick.json file I removed the leading space in the InstanceName, restarted MobiFlight Connector and now the VKBSim joystick is showing correctly in Module dropdown in Output Device.
Thanks again...
John
Re: Encoder capabilities
In that case I must have, at some point in all my experimentation, added that leading space. I don't remember doing so but I tried so many things...
All working as expected and without any issues so far.
All working as expected and without any issues so far.
Return to “General discussions”
Who is online
Users browsing this forum: No registered users and 4 guests