ark

I appreciate all the above responses! Couple of questions: 1. Does Live weather with the Active Preset mode make any use of MSFS live weather? Or is it mainly based on METARS and interpolation (smoothing) between them? 2. Do all three Active Preset options make use of the many variables you can set with the AS controls, or is that only for the Live weather option? I realize these questions have likely been answered somewhere in the 60+ pages of the various AS threads, but it is not always easy to find them. Thanks very much, Al

Thanks for the response and explanation. I guess I would say the correct technical term that describes how AS does what it does may not be the best term to convey to the average non-technical user what the result is. Al

I don't have Active Sky -- yet. In reading here and the previous thread (now locked) I see posts referring to three Active Sky modes, Preset mode, Active mode, and Passive mode. My understanding is Passive mode is when you are using live MSFS weather, and Active Sky is "only" providing air effects such as turbulence, wind drafts, etc. My sense is Active mode and Preset mode are really the same thing. Correct? My understanding here is this is when Active Sky provides live or historical weather, where you can adjust the transition times between locations with METAR reports, etc. You can also customize the weather with the myriad of "controls" that Active Sky provides. I think it is this ability to adjust all these controls is where the term Preset come from, but I personally find this confusing and misleading since MSFS also has options for types of Preset weather when live weather is not used (you can select rain, or overcast, or clear, etc) I think it would be better if Active Sky used a different term, something like Managed mode or Customized mode perhaps, because the Preset weather in MSFS is not like the Preset weather in Active Sky. To me, Preset weather implies unchanging (set) weather, which of course doesn't fit the Active Sky situation. Just my $0.02. Corrections to any misconceptions above welcomed. Al

No. Look in the Changelog file in the INFO folder which is part of the Lear's update download. Current Lear Early Access ver is 1.2.8. BTW, the Flysimware Discord is the best source for the latest information on Flysimware planes. I also try to keep this post up to date. Al

Below pic shows the MSW button (Control Wheel Master SWitch, MSW). Looks like I had a typo above, very sorry! The standard bindings that FSW has set up are: MANUV BUTTON (RHS YOKE) — MANUV BUTTON : {bound to} : SMOKE ON (ON PRESS) MANUV BUTTON : {bound to} : SMOKE OFF (ON RELEASE) STEER LOCK BUTTON 1 (center console white STEER LOCK button replacement) — STEER LOCK BUTTON : {bound to} : TOGGLE TAIL HOOK HANDLE STEER LOCK BUTTON 2 (RED BUTTON ON LHS OF YOKE) — STEER BUTTON : {bound to} : G LIMITER ON (ON PRESS) STEER BUTTON : {bound to} : G LIMITER OFF (ON RELEASE) Make sure you get the on press and on release correct. MSFS also doesn't set the 'on release' on first attempt so it takes two tries. Al

If you turn on tooltips and hover over the SFT button you will see the AP SFT function is INOP. However, you can turn the SFT light on and off with (L:MODE_SFT), but since it is operationally INOP, I don't see any good reason to do that. Al

Thanks for the report Ray. I really have enjoyed using the Fulcrum yoke, and I'm looking forward to reordering the TQ when it is available! Al

Chris, Great to hear things are moving in the right direction for all concerned! I am also ready to reorder the throttle quadrant when it becomes available. Al

Thanks.

Could be a Community folder conflict, for example, do you have any addon liveries in your Community folder? BTW, I see an updated version of the TDS GTN 750 was released about 5 hours ago. Al

If anyone using eye tracking happens to wear glasses I'd be interested to know how the eye glasses impact eye tracking. Thanks, Al

If you mean why is the aircraft cfg file encrypted, you would have to ask MS. It is certainly not a developer decision. Al

If you are having an issue with FSUIPC7 connecting to simconnect "automatically" and don't want to look at the log file, one approach would be to simply try some values. The default value for DetectToConnectDelayAuto is 60, which apparently is not working on your system if your are having a problem, so then try a value of 100. If 100 works either live with that or try a value of 80. If 100 doesn't work try 120 or 150, etc. It should not take very long to find a reasonable and reliable value. I think the max value is 400 or more. My understanding is the value you use is not critical as long as it works reliably. So if the value you use is actually 30 sec more than necessary, it just means you will have to wait 30 sec more than necessary for FSUIPC7 to connect, but connect it will. If necessary, use the same idea with the other parameters. I expect John will have some better ideas. Al

The thread Bobsk8 posted shows how to look at your FSUIPC log file and then enter and set a FSUIPC7.ini file parameter called DetectToConnectDelayAuto under the [General] section if FSUIPC7 is loaded automatically, or the parameter called DetectToConnectDelay under the [General] section if FSUIPC7 is loaded manually. The thread also contains a test FSUIPC7.exe version (7.4.11A) that you can download if needed that seems to work. You just paste the file as a replacement into the location where your current FSUIPC7.exe file is and restart the sim. Al

My mistake, sorry, wrong plane! 🙁 No, there is no default keyboard entry to launch/stow the EFB. If you have a registered (payware) version of FSUIPC7 I can send you a C414 controls lua script that will allow you to assign keys or buttons for 26 different C414 controls including the EFB. If interested PM me your email address. Al