I’m using a MIDI device as a virtual joystick (via vJoy and midi2vjoy) and I can’t figure out how to make the absolute position of the rotary dials to correspend to a setting on the autopilot (or any other in-game rotary dial)? Is there a way where I can make that happen, any known config files to explore?
The virtual joystick works fine and I’ve mapped the rotary dials to Z, X rotation, Y rotation and Z rotation and Flight Simulator detects them just fine, I just can’t find a function to map these to.
I dont think we have that stuff exposed yet via SDK or refs. Ill be digging deep this weekend with a bunch of hardware I have and seeing what I can/cannot get to work.
Workaround: I mapped each “click” of the dial to a joystick button so now it “works”: if previous value was less than current → press “joystick button 2”, if more press “button 1”. It’s very hacky but, oh well, that’ll have to do for now. Only I can’t rotate it too quickly or it doesn’t work, so kinda pointless
I’m not a simpit builder, beyond HOTAS, a couple of MFD etc. but I was wondering how you guys coped with the fact that the rotary dial commands in the control setup seem to be very coarse? For example, the keystrokes for rotating the Heading bug goes in steps of 10 degrees, or Autopilot Altitude knob on some aircraft steps in 1000ft increments. Conversely, the virtual knobs in game can be left clicked to get fine adjustment, or scrolled with the mousewheel to get coarse adjustments.
I mapped mine via FSUIPC7. I even got the Go-Flight AP to work through FSUIPC7. Now, I am waiting for the upcoming Sim Connect fix, so the FPS don’t drop tot he floor.
How do I configure FSUIPC7 correctly? On my plane of choice, the TBM930, the Autopilot wont register any change, but if I set it to, say, trim on FSUIPC7 it works ok. I can set it to the heading bug too, but one click of the dial makes the bug do craaaazy things. Do I need to do math in Python or just click something I don’t know?
I “think” it works for me? I assigned the Go-Flight A/P rotaries to the appropriate functions. I can’t remember if I had any issues, however. I am not using FSUIPC at the moment. I am waiting for the sim-connect fix.
Here is the thread link for FSUIPC7. You might find some info there, or ask your question that the forum.
I am the developer of midikey2key, which is a universal software to transform MIDI events into anything else.
After the FS patch was released now, I am developing a direct Midi-to-FS interface (get and set FS values). So besides setting values or reading the altitude it will be able to read the status of a toggle and send a MIDI command to Your MidiPad which has LEDs behind its buttons and set a LEd color.
So far MidiKey2Key is capable of translating Midi event into keypresses and manipulate MS FS.
Endless encoders are a problem, because there is no standard how to represent these messages into events.
MidiKey2Key can already translate controller inputs (pots or faders that have a value scale 0-127) into sending 2 different keyboard events (+ and- key).
Some things are already working and are already useful for Flightsimulator and others are in development.
MidiKey2Key is free and there is a discord channel and a support forum (german/english). Get it on midikey2key.de
Within the next days I will make a demo video showing what You can Do already with it and FligthSimulator.
Your program sounds interesting. Thank you for offering it to us. I use FSUIPC for most of my control settings. However, their are times when it doesn’t work. Perhaps, MidiKey2Key will work in these situations. I look forward to seeing your demo vid.
I look forward to this. I have a Faderfox UC4 and I’d like to use it for MSFS! I will need to figure out how to better configure the rotary encoders and sliders. The rotary encoders can also behave a pots and display values, which is nice!
Do you think MSFS parses keyboard inputs at the same rate as joysticks?
Yes, but only in research.
Now I know, how to do it and what to do.
A320 is not possible in the moment, because it uses so far unknown offsets, which Microsoft/Asobo need to publish or Pete Dawson find ou the hard way…
There are thousands of possible parameters to control. I could implement all of them, but it will take a long time. May I start with the most common values.
But:
AS mentioned this will be part of the pro-version of Mifikey2Key, which will be sold for a fair price.
Even if the Flightsim-implementation would be built-in, to release the program all the licensing stuff and online-shop requiremenst needs to be programmed.
I am half way through this, but it will need some time.
We could talk about beta-testing if You deserve the functionality very badly.
But first of all, it must be built-in with an extended UI and the possibility to store the new setups.
I will provide informations of the progress in the midikey2Key forum as well as discussing Your wishes about that.
I’m using your software with TouchOSC to create an MSFS controller. As you say, keystrokes are easy, but I’m having difficulty with the rotary encoders!
I am using Bome’s MIDI Translator Pro demo, but I would be interested in your Pro Version.
Samething is happening to me…even if i use fsuipc…alt and hdg will increase by 1000 and by 10 instead of 100 and 1…
But the hick is that it does that about 95% of the time…in the rare occasion, it is ok ?
With the same aircraft…i use the c208 a lot…
I am puzzled…
