MobiFlight is a great piece of software, no doubt about it. In a way, finding it made me wonder whether or not I might have a chance at building my own A320 cockpit. At that time, I read a lot about all those specialised interface boards, and complicated hardware/software setups that I really felt like MobiFlight is a godsend.
Despite my initial success and enthusiasm I quickly became weary of the lags between changing autopilot values and seeing a response on the MAX7219 7-segment display driver. Now, this is not a problem of MobiFlight itself! The issue was that X-plane doesn’t do FSUIPC/XPUIPC offsets so you need to map the datarefs to those offsets first, and only then you can link that offset to MobiFlight.
So I started looking for another solution. And I found it…
Yep, I’m talking about SimVim. Incredible piece of software that works with Arduino (I’m using the MEGA2560 board), comes with great online documentation, visual configurator, and absolutely amazing support by its creators. And most importantly, it is insanely fast (it’s an X-plane plugin, not an externally running app).
How does it work?
It took me a while but I eventually figured out how to use it all to do what I need it to do.
- download and install the SimVim plugin from the creator’s Patreon page
- go to the SimVim Configurator
- enjoy experimenting 🙂
Now, I’m not going to try and explain how it all works, their website covers it all in plain and simple English.
What I will do though is I’ll share what I stick into the data.cfg file (supplied with the SimVim plugin), how I create my own custom datarefs for the FlightFactor A320 Ultimate plane, and how I link that all together. I’ll also post a video to demonstrate the results.
In my next post, I’ll show off a little how I managed to convince the SimVim display managed/selected mode of the plane’s speed, which is also applicable to heading, and –partially– to altitude displays, too.
Until next time!