To explain:
The "No VSTOL control" problem MAY occur when Tacpack is active; Tacpack then somehow interferes with the interface modules I use (IPC dll + FSUIPC) to command SimConnect from my VSTOL XML gauge.
The same problem sometimes happens with other addons that use my simular "VSTOL" solution, like in the Bounty sailing ship.
- On FSX-Accel and FSX-Steam: never a problem.
- On P3D: only occasionally, and then even only on some user PC's (most P3D users have no problem). No explanation why ...
IF someone with P3D and Tacpack has this problem, disabling TacPack (so TacPack isn't automatically loaded when P3D starts, to be set in TacPack itself) appears to be the remedy (for the 4 users I know of).
I hope user FREDDO will confirm this works for him too.
I don't have a clue why this sometimes happens, and I don't think I ever will, because I have to bring some parties together to solve this (Tacpack, IPCmodule, FSUIPC, and ???) while I can't even reproduce it myself.
So trying to debug this, especially since most P3D/Tacpack users have NO problem, is virtually impossible.
But, as said, the remedy is simple and maybe I have a solution in the future.
Rob