Looks like you are off to a great start. Already have a Streamdeck otherwise I would be looking to pick up one of these as the encoders would always come in handy.
Itās not seen as a device in FS as you know so youāre limited to setting up a config on the Loupedeck as keyboard emulation.
However, Axis And Ohs can see MIDI input and the Loupedeck can output MIDI.
I have a number of volume channels set against the rotary encoders, Axis And Ohs then can map those to simulator events like +/- altitude, heading, trims etc.
The advantage being over other MIDI controllers is that you can have multiple different sets of six encoders to allocate to all the inputs you want across different pages like a Streamdeck.
If you are integrating through FSUIPC though then youāre doing the same with the addition of reading values back in which is great. Will give youāre solution a go since I can see youāre already accessing the same Iām using so makes it a more contained solution.
Have followed you git repo for future updates. Excellent!
Downloaded the zip and FSUIPC7, unzipped the first and installed the second.
First thing, the installation notes say to copy the two .dllās to the %USERPROFILE%\AppData\Local\Loupedeck\Plugins directory. I donāt have a /plugins directory but do have a /plugindata directory. Is this a typo and it should be the later or do I need to create a /plugins directory? Iāve tried both.
If I import the .lp4 file either in the ānewā Loupedeck UI or the previous one, it does so under a blank application unless you choose an existing application profile set up for MSFS2020.
Either way, when I start FS, FSUIPC loads as expected and the Loupedeck switches to your profile but all I get on the screen is N/A in every area.
EDIT: Aha! got it to work by putting the two .dllās in the main install directory where all the others are. Having an odd issue with the auto-profile switch now seeming to work backwards but thatās a Loupedeck thing
Only had a quick try but looks great so far with the AP encoder controls working. Let me know if you have any updates to try out! Excellent.
Your plugin looks great. Iām from Loupedeck and can support you with the SDK & plugin development. Let me know if I can help you, feel free to email me at aki.sysmalainen@loupedeck.com.
Just installed the latest and removed the dllsās from the application directory and just have them in the plugins directory now. Heh - works fine this time! so not sure what was up previously.
Also, I deleted the existing application profile set to MSFS2020 I had previously and to which Iād imported the .lp4 previously. Just imported it directly and, even though itās not showing as being related to FS2020 as such, it now gives me access to the plugins controls - I thought they were locked previously since I couldnāt get to them.
Anyway, great job, this way now I can also move things around and add other controls as I wish together with home page links back to my other profiles etc.
Good news for the installation !
Next release, I hope tomorow, will use the new plugin delivery system of the UI.
I need some more tests before releasing the version
Great. Can you just double click on the .lplug4 file for the package installer to do it automatically, rather than through a CMD line? It seems to have created the MSFSPlugins directory in the right place for me and dropped the .dll and .pdb files in there.
Yep, can confirm that works, creates the application with a default profile and gives it the icon. Importing the .lp4 add it as a second profile under the application. Because the profile is now separate from the plugin, I assume it makes upgrading customised profiles easier?.
One question, the AP and Lights folders are effectively locked - I canāt see any way to edit nor re-arrange their contents? Is a folder even a native Loupedeck āthingā or are these effectively workspace links? Either way, could their contents instead be made available outside of the folders so they can be used as required? e.g. could set up workspaces for different aircraft with different requirements.
For the moment the command line seems to be the only way to include plugin. There a plugin menu in the UI but it is grayed out. Maybe a future update of LoupeDeck ?
The folders are way to simplify the config putting only one input but the layout is defined in the plugin.
I will add separate input in the next release.
Ok I know why it didnāt work for me : last update of Loupedeck fail so I installed it in portable mode, so I donāt have the registry entries for installing plugins.
I will update the doc in the next release to simplify this, and retry to fix my installation.
Gentlemen, I purchased a Loupedeck Live with high hopes. I was finally able to make it work with FS2020, byt ran into the issues that others have mentioned: disappearing cursor, heading bug circling endlessly, little to no response to button presses, no response from encodersā¦ I packed it up and am ready to send it back, but I came across this thread. Now my interest is coming back, but Iām a bit overwhelmed with the amount of information Iām seeing here. Iām no newcomer to technology, at 66 I can tell you I actually coded on Hollerith cards and teletype consoles, lol.
What Iād love to see, before I return this seemingly wonderful device, is a roadmap to getting the results that you are seeing. How about it, guys? Just a simple step-by-step.
Thank you for putting in the time and effort and sharing it here. Iād like to contribute as well, if I can actually catch up with you and get this working ! Regards!
