GACSavannah

Did you run the MSFS plugin?

>I have MSFS set to the output that I use, which is LG TV via Nvidia High Definition Audio. When the issue occurs, it resets to system's default device. As I see it you have two options. Either set the TV up to not turn off after sitting idle, so that the connection is never lost, or you can set the TV as your default output, so that when it disconnects and switches to the default, it is right back to the TV.

I had an issue yesterday where certain elements of my controls were not working, such as thrust reverse through my Thrustmaster Boeing and Airbus throttles. I rebooted but have not had time to go back and see if the issue is still there or not

>Loose lugnuts? There are no lugnuts. The wheel assembly is held on by a single large nut, that secures to the end of the axle at the center of the wheel. The nut is torqued and then secured with a metal snap ring to prevent it from backing off. It is actually not all that uncommon for one to come off. The typical cause is failure to properly torque the nut and install the snap ring, or occasionally failure of the axle itself, where the end of the axle is cracked usually between the threads and simply snaps off, taking the nut with it. With the nut gone, the wheel assembly will slide right off with no problems.

That is not a military flight. N66W is a civilian aircraft. They were probably doing a photo mapping flight, to update Google Maps or Bing Maps or some other customer, or possibly performing a LIDAR scan.

I am with you on this one. I refuse to even attempt to access anything Discord any more. I wonder if all of these developers that insist on using it realize how much they isolate a big portion of their customer base by insisting on Discord only support. :0(

I have done the same, also with no apparent ill result. I hope that everyone else is enjoying the plane as much as I am. I was an AP Mechanic on the Lears for Clay Lacy in Van Nuys Ca back in the late 1980's, and this has brought back so many memories 🙂

I have been getting that on and off for most of this past week

UPDATED Update Instructions: Yesterday I responded to Mac44's request on how to update the Lear 35A. As a result of the (FALSE Positive) Defender warnings, they have changed the process at least for now. Rather than identify the differences, I will start over here with new instructions on updating the file. Please note that I have NO association with the developer, I was simply attempting to answer a fellow users question yesterday, and feel I should update that previous answer with the current correct information... Updated update directions: You want to go into your Flysimware account, and select "Order History and Downloads". On the right side of the purchase click the Details/Downloads link. When the Order Details page opens scroll down to "Order Details", where you will see ">> Download Information", and below that you will see "Start Download", Download Info", "Contact Page", and "Learjet 35A MSFS". To the right of the "Learjet 35A MSFS" you will see a note specifying the current file level. Right now it says "Current product Version V1.1.8 / JAN-31-2024" If this is newer than your current version, re-download the file by clicking the teal colored link in the product window just below. The zip file will contain a folder named "flysimware-learjet-35a". This is the complete Learjet 35A product. If you had previously installed an earlier version, go into your Community folder and manually delete the earlier version. After deleting any prior versions, paste the "flysimware-learjet-35a" folder in your Community folder. That's all there is to it. This manual method replaces the previous automated installer.

You want to go into your Flysimware account, and select "Order History and Downloads". On the right side of the purchase click the Details/Downloads link. When the Order Details page opens scroll down to "Order Details", where you will see ">> Download Information", and below that you will see "Start Download", Download Info", "Contact Page", and "Learjet 35A MSFS". To the right of the "Learjet 35A MSFS" you will see a note specifying the current file level. Right now it says "Current product Version V1.1.7/JAN-30-2024" If this is newer than your current version, re-download the file by clicking the teal colored link just below. The zip file contains an executable file. The executable will automatically remove the prior version and install the current version for you. The zip will also contain a copy of the current changelog so that you can see what is changed with the current version. CAUTION!!! I was actually doing these steps as I wrote them to make sure I told you correctly. As I opened the version 1.1.7 zip I received a Thread Defender virus warning for a hidden TROJAN in the file. I have never had a problem with any of their other files, so I do not suspect any harm is intended from them. It may have simply been a false positive, but I deleted the file to be safe....

Loving the Lear 35 so far. Thank you for the continuing stream of updates. Is there a default program setting that aligns with the Nose Wheel Steering activation button that can be assigned to a controller button through the standard program controllers settings and options menu?

I am seeing snow in the Pacific North West

>This plane has been very clearly identified as an "Early Release" edition No worries, I was simply pointing out that there was an issue, in case it was simply an unintended fault of the last update. I believe I posted previously that it was apparent that the reason for the issue was a change in the texture applications, and even commented that the change was a good one.

OK, I figured out the issue. They have added new textures for the right wing with the latest update, presumably to allow non mirrored textures on the wings, which is good. But now every livery that has already been made will need to be updated. They have also added dedicated texture for the top left of the nose (Avionics access panels) presumably for the same reason.

> Are you using just a default Flysimware livery? Good question. It was with every livery that I had loaded into the Community Folder. Both default paint jobs seem to be okay. Any community folder livery replaces the right wing with the right wing from the default N86BL livery, plus the top left of the nose is a seemingly random grey and black texture, regardless of which livery I select, including all three Airframe/Avionics options. I am going to run a test and load a third party repaint into the default folder, and update the Aircraft.cfg manually to reflect the addition, and see if it displays properly. I will report back once I have the result...