I’m sorry to hear about your problems with the device. I work for Loupedeck and from the company’s behalf I can say that we have plans to enable plugin support for MS2020 SDK. So I can assure you the Loupedeck devices’ compatibility with MS2020 will improve.
For now, the workaround is to use FSUIPC with @CaliBx’s MSFS Deck which in my tests has worked really well.
Perhaps he can post a step by step instructions as I’m not able to share links to this thread.
Thank you for your reply, I’m quite impressed by the way you respond to this type of issue. I will most definitely give the unit another try, following these guidelines.
You guys are awesome! It’s working like a dream. I only had an issue in that the .dll wasn’t placed into the proper directory so the plugin wasn’t installing properly. I found this in the installation logs and moved the .dll. After that it went smoothly.
Yep, you can use Axis And Ohs alongside it using the MIDI plugin to create as many volume, slider, fader etc. virtual controls you could want and allocate to dial pages.
A&O’s can then see them to allocate against.
Seems like you need to delete the old installation before upgrading, so delete the folder %userprofile%\AppData\Local\Loupedeck\Plugins\MSFSPlugin
Then you can double click the new .lplug4
Excellent. Any chance of bringing in the G1000 FMS upper and lower knobs and map zoom?
I 've added them via Axis & Ohs reading MIDI inputs but native would be easier.
Yes, if you have the full version. I have it configured to generate MIDI commands and then Spad.next can map them to whatever you want. I believe the Spad.next developers are working on integrating Loupedeck, but I don’t know about the timeframe.
I will wait to remove FSUIPC before including G1000 support because FSUIPC doesn’t handle all the inputs. Using SimConnect without middleware will be more easy.