ark

Make sure you have the latest version of the binding app, ver 1.6 (shows in lower right corner). There must be 1000s of Lear owners using this binding script successfully, really strange you are having this problem. When you contacted the developer what did he say? Al

Make sure the app hasn't just minimized to the task bar. That's what happens in my case. Al

My understanding is the departure airport history is not saved if the sim is in Developer mode. So if you do have Developer mode on, try turning if off, then exit and restart the sim to see if that makes a difference with departure airport history. Al

Yes, StarHawk! I knew that, don't know why I used Skyhawk (age problem maybe 😕), but I fixed it above). Al

Here are the StarHawk pictures from ValinHawk. He and his wife built the StarHawk.

FSW actually got to fly the Starhawk with Valin -- he loved it. Al

BTW, I assume there is no need for a Community2020 folder (which would be for addons that only work in FS2020) because the premise is that FS2024 will successfully run all FS2020 addons, although I have to wonder how well that holds true in practice . Al

@Tuskin38, Thanks for the clarifying info directly above. It makes good sense to me that the Community2024 folder would be for addons that only work with FS2024, and that the single shared FS2020/2024 Community folder would be for all other addons. Al

I have both FS2020 and FS2024 and a separate Community folder for each. I have been putting FS2020 addons that are compatible with FS2024 into the "regular" FS2024 Community folder and all seems to be working fine. I did not realize until now that there was a separate Community2024 folder in FS2024, and so it is currently empty. Will putting FS2020 addons that are compatible with FS2024 into the "regular" FS2024 Community folder lead to problems somehow? I don't mind keeping two copies of addons that work in both sims. Thanks, Al

Some FSW Legacy info here: https://www.avsim.com/forums/topic/690182-flysimware-–-lancair-legacy/

Although the FS2020 version of the Lear35A works in FS2024 Free Flight, my understanding is you can't have the FS2020 and FS2024 native versions of the Lear35A in the same Community folder at the same time. Al

No such plans at this time. Al

GREYSPIDER, you may be confusing the Pitch Hold and Pitch Trim functions. Pitch Hold adjusts the aircraft pitch (nose up/down position) when the AP is in Pitch Hold. The AP is in pitch hold when ENG is on (AP on) and no other vertical mode (such as IAS, VS or ALTHLD) is on. It is activated by moving the barrel up or down WITHOUT also holding in the hat switch that is on the end of the barrel. The bindings INCREASE/DECREASE AP PITCH HOLD REFERENCE work for Pitch Hold. Pitch Trim works when the AP is off. Pitch Trim works by moving the barrel up and down while also holding in the hat switch on the end of the barrel (which is difficult to do with the mouse). And note that STEER LOCK much be off for pitch trim to work. The bindings ELEVATOR TRIM UP/DOWN work for Pitch Trim. Moving the pitch trim should also turn off the AP if it is on, so whatever keys/buttons you use for pitch trim should also be assigned to turn off the AP. Al

If the FS2020 Learjet35A does everything a user wants, I certainly understand not wanting to purchase the FS2024 Native Learjet35A version. However, IMO I don't think it is accurate to refer to the FS2024 native Learjet35A as an "upgrade" in the usual sense of the word. Many FS2020 aircraft have been upgraded (or ported) to work in FS2024 Free Flight, including the FS2020 Learjet35A. In contrast however, the native FS2024 Learjet35A is a newly coded aircraft that strives to take maximum advantage of the new FS2024 SDK. Here is a partial attribute list for the native Learjet from the FSW Discord: 1. Expansion packs (Cargo and Medevac) included (no separate add-ons needed). 2. Two brand-new variants/mods: Long range Tip Tanks and a Ventral Fin (this models a real life mod provided by a company called AVCON), that provides a total of 6 presets or variants total. 3. Major livery expansion: 8 passenger + 8 cargo + 4 medevac = 20 liveries. (This was specifically requested for Xbox.) 4. MSFS 2024 SDK work is dramatically heavier: building these features took multiple times longer than the typical “effects + preflight” update that many aircraft are doing. What’s in this package is on a completely different level. 5. New failures system with 3 modes: realistic MTBF (with an acceleration slider), Scheduled (you can set a time range of up to 300 minutes for a random failure), and Speed (so you can properly practice scenarios like an engine failure at V1 during takeoff). 6. New model and control-surface fidelity: the sim now understands the aircraft as more than “fuselage + wings” — it recognizes short tanks vs. long tanks and the ventral fin, so the aircraft flies and behaves like the real configurations. 7. New Boris engine sounds (and yes, for those who noticed, they were recently added to the MSFS 2020 version as well). 8. New integrated tablet as part of the default sim tablet — no “two-tablet mess” (since the default can’t be disabled). Includes real-world charts and more. 9. 179 working circuit breakers, plus a full electrical overhaul, tied directly into both the failure system and the career wear-and-tear system. 10. Three careers added for each preset, with wear and tear fully implemented. 11. Windshield bloom effects and rain effects across the entire aircraft. 12. Improved icing visuals on the nacelles and nose, including melting behavior (Asobo still doesn’t provide this natively, it was implemented as a workaround). 13. Three-level interactive checklist, including a camera “eye” button that moves your view to the correct area for each step. 14. New pneumatic system with temperature control, plus live valve operation feedback on the tablet, including the emergency pressurization system. 15. New ground equipment architecture: the Fuel Truck and GPU are no longer built into the aircraft — they are loaded as true SimObjects, just like standard sim vehicles. 16. Proper ground behavior for ground equipment: because these are real SimObjects, they always know where the ground is and stay planted. Changing payload no longer causes floating or drifting wheels, something commonly seen in other aircraft products. And there’s a lot more. The primary beta testers for the native Learjet 35A are two retired real life pilots with many 1000s of hours in the Learjet 35. One was a chief pilot, and the other a Learjet flight instructor for Flight Safety International. That said, whether the type of features provided by the native Learjet35A are "worth it" is clearly personal to each user. To each their own. Al

You want Shift+C (or a key or button of your choice) assigned to both of the Asobo bindings called QUICK PREFLIGHT and TAKE CONTROL OF CHARACTER.

An interesting point (at least to me 🤔) is that when using approach mode with an LNAV+V approach, if when reaching the MDA you don't see the runway, you don't want to initiate the missed approach procedure until reaching the published LNAV MAP. It is not uncommon for the advisory GP to intersect the MDA well before the MAP, but as with any approach, initiating the missed approach "early" can be bad for your health. So this begs the question, if you don't have any ground contact during your approach, how will you know you have reached the MAP? Unless there is a convenient VOR, NDB, etc to help identify the MAP, you would need to time the approach from the FAF to the MAP even if flying an approach with advisory GP information.

I was told by a retired Learjet pilot, who also was a Learjet instructor for Flight Safety International, and works with the FAA in the design of instrument approaches, that there are differing opinions on the use of the APPR button with an LNAV + V approach. His opinion is you can use the APPR button with an LNAV+V approach. He said in part: LNAV+V is a GPS derived lateral path using GPS, and SBAS if available. However, it uses Baro-VNAV for vertical guidance. That vertical guidance is advisory, in part because the Technical Standard Order (TSO) for Baro-VNAV guidance does not require a level of performance to prevent false and/or misleading information from being presented to the pilot. That's because when using Baro-VNAV, the pilot is supposed to be referencing the barometric altimeter for minimum altitudes. LNAV 's obstacle clearance surface (OCS) is a level surface, providing 250' of obstacle clearance in the final approach segment (in contrast, the OCS for a typical 3.00 degree GP slopes at 34:1). No one cares how you get down to the MDA or any intervening stepdown altitudes. You simply have to not go below these altitudes. You can use VNAV, use VS, or basic PIT mode. With LNAV+V, you can use APP mode. In the Lear 35 with the GTNXi, that means NAV and GS. You have to keep in mind that approaching the MDA or a stepdown altitude, the autopilot will ignore the altitude preselected set altitude and not level off. If you flying Constant Descent Final Approach, which you should be doing with modern aircraft, you do not level at MDA anyway. You set a derived decision altitude, which is typically no lower than MDA+50'. I like to use MDA + 10% of the final segment vertical speed. When you get to your derived DA, if the runway is not insight, you execute a missed approach just like an ILS or RNAV to LPV or LNAV/VNAV. All approaches are flown the same this way, and APP mode is used in all of these approaches. Treat all approaches the same, fly them the same, and you won't have any problems. Being doing it this way for 25 years, in the Collins, Universal, and Garmin systems and a variety of jets. The key take-away for me on this is you can use Approach Mode on a LNAV+V approach, but you are still responsible for not busting any of the stepdown altitudes or the MDA as indicated on your altimeter.

I often log into Discord from a different location, I just enter the info they ask for. So I don't understand why if you provide the info they ask for it doesn't work. My last ideas would be to suggest you contact SimMarket and see if they can help since that is where you bought the product, or maybe Flysimware through the Contact form on the Flysimware website. Al

Seems strange, here's another Discord link you can try. https://discord.gg/SGe8XaGJ Al

I I have no experience with SimMarket. I have read that there is no installer like that from Flysimware, but rather there is a Simmarket APP that you run to get their products installed. You install that APP and run it from your desktop. In the settings you setup the 2020 and/or the 2024 community folder location. For more help, suggest you go to the Flysimware Discord sit and post in the pc-support-chat channel under Product Support. Lots of Lear35 users there and I'm sure some SimMarket customers. https://discord.gg/23r7jnCA Al

From where did you buy the Lear35? If directly from Flysimware, just unzip the medevac download and run the installer that is inside. It should install the medevac into your Community folder. If your Community folder is not in the typical location, you will have to point the installer to the correct location. The installer will also ask if you have a Steam or MS sim install. Note that to use the Medevac version of the Lear the basic passenger version has to be installed as well. The Medevac version uses files installed with the Lear's passenger version.

As a start, make sure each version (passenger, medevac, cargo) of the Lear that you have, and the PMS50, are ALL updated to the latest versions, and you are using default Flysimware liveries. Al

Is the new sound set for the TBM850 part of the 0.1.4 update or does the updated sounds have to be downloaded and installed separately? Thanks, Al

Ah, somehow I didn't realize that was the main issue. Hopefully all is now working with the aircraft magneto start switch. Al

I experimented a bit and found that while holding down the left mouse button I can use the mouse wheel to move the magneto switch to the start position and it will stay there until I release the left mouse button. Works in both Legacy and Lock mouse modes, at least in the Piper Dakota. With the C152 and C172, just holding the left mouse button down worked in both mouse modes, so it seems to be developer dependent to some degree. BTW, I use FS2024/SU3. Al