![]() ![]() At least the “Lights” variables are (still) declared as “read-only” in the SDK documentation… There it also seemed that setting some light variable actually toggled “the last successfully set” (which includes “operations with the mouse in the cockpit”) element. LIGHT PANEL ON).Īnd I tried with both LIGHT NAV and LIGHT NAV ON variables. However I was in fact trying to set other light variables (e.g. the SimVarTokens.simvars set) all of a sudden I was “able” to toggle the “Strobe Light” switch (in the “Extra” aircraft). Otherwise it could simply mean that FS 2020 - despite claiming otherwise in the SDK documentation - simply does not support yet the TAILHOOK POSITION and CANOPY OPEN variables.Īgain, I’m interested whether others were successfully reading (and setting) those variables with other aircrafts, or whether anyone can confirm the same observations (with the same T-45 model or with other aircrafts even).Īll simulation events considered legacy? SimConnectĭoh! I take it back: just after reloading SimWatcher and only loading (and trying to set) the LIGHT NAV value it did not work anymore.Īfter fiddling around with other “LIGHT” related variables (and also loading e.g. I have yet to find a proper contact address )). for the Spitfire? Because that would probably also imply that the T-45 Goshawk implementation simply does not properly set those variables (yet) (-> I have also a pending question with IndiaFo圎cho about this, but yeah, on their facebook announcement post. So are you implying that you do get values > 0.0 for the CANOPY OPEN variable (e.g. I am not sure whether I understand your answer (or whether you understood my actual question )): the tailhook and the canopy of the T-45 Goshawk (by IndiaFo圎cho - who also provided the MB339 earlier) do work within Flight Simulator: that is, the tailhook properly is lowered and raised (visually), and so is the canopy (open, close) when I operate the corresponding handles in the cockpit, with the mouse.īut the problem I have is that this is seemingly not reflected by the corresponding simulation variable states, namely the variables TAILHOOK POSITION and CANOPY OPEN: according to the MSFS SDK documentation (linked above) they should work, but I always get values 0.0 back - also with the provided SDK example app “SimvarWatcher”, regardless of whether I set the metrics (unit) to “percent over 100”, “percent”, “number” or even “degrees”. I guess so?īut the canopies of the Spitfire, the MB339, the G.91 and the P.139 all work through the virtual cockpit (*) I just read that the F-15 does have a tailhook as well, for emergency landings on land - but not sure whether the F-15 in FS2020 has a functional tailhook. Not sure whether other airplanes with a tailhook exist in FS2020 (*) but maybe someone has had luck with opening canopies? I also tried with the example SimWatcher app, with different metrics (percent, percent over 100, number, even degrees… the values remain at 0.0). Quite possibly that airplane is not setting those variables properly (yet), or they simply don‘t work at all yet in FS2020. ![]() ![]() It should, but with the T-45 Goshawk that I just purchased today in the MS Marketplace (which has a tailhook and a canopy that can be opened) I am always getting values 0.0, regardless of whether the tailhook has been lowered or whether the canopy is open. Can anyone confirm whether reading and writing the simulation variables TAILHOOK POSITION and CANOPY OPEN actually works? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |