26 minutes ago, toddc said:

I have the same AP panel lights issue since I puchased the plane last week.  I have submitted two support emails and was referred to this thread.  Which CAB file are we talking about and also the default flight files?  I love the plane and the autopilot works fine, just no indications at all.  Makes no difference if i try cold and dark or ready to start profiles.  I am using P3D4.5 HF2.

One thing you can try is to make the F-35 your default flight. Load it on to a runway, make sure the engines are running and systems powered up, then save it as your default flight. Some have found (including me) that this helps to initiate some of the sim variables. In general it is always good to start with a default a/c before loading a complex one. PMDG also advises this. I have found that for me the F-35 works better than other default a/c in this role.

If the above doesn't help, please try a quick test. After loading the Lear and clicking on 'Ready to start' in the Hanger (Shift+1), press the annunciator light test button that is just to the right and above the standby attitude indicator. Do any of the annuciator lights above the AP lights come on, or any of the AP lights come on? If you could post a screen shot here of the lights that would be helpful.

Al

Edited April 22, 20206 yr by ark

Thanks for the reply!  WIll try the steps later today.  I will make a short video of the steps you have suggested.

11 minutes ago, toddc said:

Thanks for the reply!  WIll try the steps later today.  I will make a short video of the steps you have suggested.

The main thing I need to see is what lights come on (this includes the annunciator panel lights, the Reverser lights, the GPWS light to the left of the pilot's AoA gauge, and AP lights) when you press the annunciator light test button (note this is not the AP TST button). The light pattern may provide a clue to what the problem is.

Thx,

Al

Edited April 22, 20206 yr by ark

I've just seen this bug - (first flight) - after updating to 4.3 - again autopilot works fine - just no lights - when i push test, I hear a horn but no lights illuminate

does pushing TST disable R/P ENG ? (Im guessing it does)

(only one flight so far - will try and gather more info)

I selected "Ready to start" at the beginning of this flight

RealityXP GTN 750 enabled

 

 

 

Edited April 22, 20206 yr by julian46

2 hours ago, julian46 said:

I've just seen this bug - (first flight) - after updating to 4.3 - again autopilot works fine - just no lights - when i push test, I hear a horn but no lights illuminate

does pushing TST disable R/P ENG ? (Im guessing it does)

(only one flight so far - will try and gather more info)

I selected "Ready to start" at the beginning of this flight

RealityXP GTN 750 enabled

 

 

 

Please see my initial post to toddc above wrt using the F-35 as a default flight and if necessary the light test using the test button under the glare shield (again, note this is not the AP TST button). If there is still a problem after using the F-35 default flight, please post here a picture of the annunciator lights when the annunciator test button is pushed. Since neither myself or FSW can replicate this lights problem we need as much detailed information as possible from those experiencing the problem.

Al

Edited April 22, 20206 yr by ark

8 hours ago, ark said:

The main thing I need to see is what lights come on (this includes the annunciator panel lights, the Reverser lights, the GPWS light to the left of the pilot's AoA gauge, and AP lights) when you press the annunciator light test button (note this is not the AP TST button). The light pattern may provide a clue to what the problem is.

Thx,

Al

I did a test.  Below is a link to the video I made.  It is about seven minutes long.  In the video, you will see it start with the F35 and engines running.  You will then a switch to the Lear 35 (I am using the latest version as of yesterday).  From then on you will see me test during various phases (prestart, start, taxi, takeoff, autopilot engagement).

The link to the video is located at https://flymirageva.org/pdf/l35test.zip

If you need to see the full 18 minutes, let me know.

Edited April 23, 20206 yr by toddc

58 minutes ago, toddc said:

The link to the video is located at https://flymirageva.org/pdf/l35test.zip

Good video - thanks! It seems to me all is working now unless I missed something. I guess using the default F-35 as the default flight made the difference. This has helped a number of simmers.

Al

Edited April 23, 20206 yr by ark

F35 as default flight also worked for me - I've only seen the ap light bug a few times anyway - also on many startups the RXP GTN750 would not power on (even after picking ready to start state in Shift-1) - this seems to take care of that too - will report more results later

3 hours ago, julian46 said:

F35 as default flight also worked for me - I've only seen the ap light bug a few times anyway - also on many startups the RXP GTN750 would not power on (even after picking ready to start state in Shift-1) - this seems to take care of that too - will report more results later

Great to hear all seems to be working now.

I had not heard of the RXP GTN750 not powering on being being associated with the AP lights problem. I would be interested to know if the GTN 750 not turning on and the AP lights not working seem to 'go together' every time. If so, that would be a good clue to what the overall problem might be.

Al

I did another test this evening, starting off with the F35 and then shifting to the LJ35.  All went well.  However, I think a new issue has come up.  Both yesterday and today, when I park the aircraft and shut down the engines, none of the selections under aircraft options work.  I can't get the chocks to set, the GPU to set, nothing works.  When I try to put on the engine covers they start to blink as if a key is stuck somewhere.  It is only when I select "all systems off" in the Hangar that everything returns to normal.  I also double checked the AFCS lights afterwards and they still work.  Again, this has happened twice.  I will do a another test flight tomorrow night.

I had three flights today - two shutdowns on current leg - everything worked fine for me - no issues (did not select all off or ready to start - just used external gpu while getting ready for next flight after turning off engines and related fuel computers etc - could enable engine covers, set chocks, set windshield cover fine)

 

 

 

 

Edited April 24, 20206 yr by julian46

10 minutes ago, julian46 said:

I had three flights today - two shutdowns on current leg - everything worked fine for me - no issues (did not select all off or ready to start - just used external gpu while getting ready for next flight after turning off engines and related fuel computers etc - could enable engine covers, set chocks, set windshield cover fine)

 

 

 

 

Great, thanks for the feedback!

Al

9 hours ago, julian46 said:

I had three flights today - two shutdowns on current leg - everything worked fine for me - no issues (did not select all off or ready to start - just used external gpu while getting ready for next flight after turning off engines and related fuel computers etc - could enable engine covers, set chocks, set windshield cover fine)

 

 

 

 

Are you using the F35 as default first before flying?

Yes I am starting with the F35 - let it settle down then go to the Lear

Once you finished, did you do the all shut down before connecting the GPU?