So recently I begin experimenting ifr capabilities of the sim but isn’t going well.

Whenever I select an approach on the g1000, one or both of my screens (pfd and mfd) seems to freeze and won’t come back online no matter if I turn avionics off or even the battery or alternators. I loose all the aircraft parameters and I’m forced to land with the backup gauges, which are only 3 on the bonanza for example.

Those of you who have successfully engaged and flown an approach would you mind detailing your steps? Are you using ATC and the default fight planner (world map)?

In most occasion the vfr map continued to work and the route is followed, even if erratically returning to the last FP fix. I’m using the latest versions for the modded g1000, g36 and da40 but this even happened on the default glass 172.

I know this is a serious community so I searched and read previous threads but couldn’t come to a conclusion.

Thanks in advance,

Thiago

Edited December 28, 20205 yr by tchiari

I had this happen to me last night on a flight from KLMT to KPDX. I'm using the G1000 mod and don't know if that's the issue or not. Just as you described, when messing with the approach the PDF froze on me. MFD still worked and my Logitech Multipanel still controlled the AP functions, but PFD wouldn't come back to life no matter what I did (turn avionics and even master off-on, etc.) Made for a very unpleasant approach and landing.

I've had the same thing happen with the 172 & 208 (happened last night actually).  I have Navigraph running on another computer, so I can still follow my flight plan using ATC.  The AP usually will continue to work.  It just seems to be the PFD that dies.  Having the three backup gauges does help (I have 6 Logitech FIPs, so can always keep my eye on those).  It's not always the easiest landing, but I usually come through it pretty well.  😉 

The best suggestion I can offer given the current state of the sim is to always have a backup so you can fly why headings and altitudes if needed.  

LittleNavMap is great.

Just to clarify, is this with the latest release (0.3.4)?   We've had a few reports of similar behavior in the TBM, it's possible it's happening in the G1000 too, since they share a bit of common code.

It was with 0.3.4 for me.

0.3.4 for me as well.