TL;DR My current setup enables me to develop AirManager scripts on a remote machine using one AM license and without remote desktop
For whoever may be interested... If you scan the pictures on
https://fsarduino.com (specifically what my cellar looks like) it may be easier to visualize my setup.
I'm building a cockpit in my cellar, and I use AirManager as the primary software to integrate the hardware with FlightSimulator 2020. I have one license of AirManager.
My current setup is:
1) One main machine, which I typically use to run FlighSimulator (and work on as my daytime job, if I'm working from my cellar that is). It's a pretty high end machine and performant enough for FS2020 and my daytime development work
2) One supporting machine, which runs AirManager, Little Navmap, SimToolkit Pro and some other software. This machine has a touch screen as a main screen (which I use to deal with littlenavmap while flying) and a secondary screen, which shows my instruments. In front of my instrument screen there is a panel with some rotary encoders and buttons to configure the instruments via AirManager.
Since my supporting machine is not setup for keyboard usage really (it has a small shelve to hold the keyboard and mouse, but it's all not convenient to develop with that), I want to use my main machine for developing the AM-scripts. I can't use my main machine directly, because I only have one license (which is linked to the supporting machine), I can't use remote desktop (because AM won't load the instruments because of the graphics driver) and I can't use a demo version of AM on my main machine (because the demo version doesn't allow me to edit the scripts).
I don't need any graphics for my instruments; I just want to work on the physical buttons and integration. AM won't do remote desktop for me so, what I ended up with is:
1) Setup VSCode on both machines
2) Install the Live Share extension on vscode
3) Start a Live Share session on the supporting machine
4) Connect to that on the main machine
5) Develop the scripts on the main machine (in the shared session)
6) Start the instruments for debugging using the touch screen
This works fine for me. I'd rather have a remote desktop session to the supporting machine, but this is second best. So, my feature request stands: "Can AM please support remote desktop, at least for script development", but until then, I'll use the above set up.
You never know, there might be someone else to look for something like this.