K,this is a new one for me…I’ve tried a couple of flights now with both the TBM and Longitude and keep running into the same problem. Somewhere along the way on my flights, the PFD will just freeze up and stop updating. The speed, altitude and horizon display just stop working. The center MFD map screen continues to update…At first I didn’t notice it, until I start getting “stall” warnings…Switching to the external view, shows me the true airspeed with those instruments displayed there working…but inside everything was froze up…
I just had this same problem. It happened on Arrival whilst prepping for Approach. I disabled AP and used the backup gauges to maintain control of the aircraft. I cycled the Garmin using the hotkey (PgUp) – but that didn’t help. Thankfully, it came unstuck as I hit my approach - just in time to hit the glide slope.
I have had the same problem multiple times. It is extremely annoying. I haven\t been able to figure out what triggers this problem. It happens so often that I’m going to stop using this program until it’s resolved.
It happens when starting the approach phase of you r flight plan. The only thing that works for me is deleting a previous waypoint in the flight plan.
Thank you for the suggestion, I’ll give it a try.
Glad its not just me. Same problem on approach. What seems to have cleared it for me was cycling the PFD through FMS -> LOC1, etc. Then things started to work again. Or maybe they just started working again.
As I was starting the approach phase of a flight today, the PFD froze again. I tried deleting the previous fix and the PFD started working again. Thank You!
I have the same problem, PFD freezes sometimes when going from arrival to approach procedure in the TMB.
My hunch is this is JS issue. The screen is not completely dead, typical JS behavior.
Edit: Would be nice if we can use Chrome to debug HTML UI’s…
1 Like
If you can provide the flight plan (with SID,STAR, APPROACH, any Transition waypoints) that failed maybe other pilots could test the same situation.
It’s another known bug already published that was added in the last patch. Hopefully it will be fixed in tomorrow’s update Parch 4 release, but don’t bank on it considering ASOBO consider getting rid of the ‘press any key to start’ page as high priority!!
Where was the bug published ?
I would like to have a look at it.
It’s been fixed with yesterday’s patch 4. Have a look at the patch notes.
I read about the update when I installed it yesterday.
My post here was:
Where was the bug published ?
I would like to have a look at it.
I had this problem too yesterday. I use the honeycomb yoke. I resolved the issue by switching my batteries off and on again (I would guess it’s the same as switching on/off batteries in cockpit). Had to do it 2 times to get the displays to update again. This was in the longitude.
I was running the newest patch 1.9.5.0
Just happened to me too, on the latest patch 1.9.5.0. Ruined my flight, hope this gets fixed.
Yes it happens quite often 1.9.5., just yesterday when entering the transition NAPSA into Munich and Vatsim ATC told me to descend FL100. The back up works but it sucks as you trouble shoot just during the ATC intensive phase of a flight. I have to try the delete waypooint trick.