metzgergva

Thank you, will do that! BTW Excellent tutorial video. I'm just learning to fly her!

Hi, since a flight into KDEN I have this 60 ft missmatch between the ALT bug and the indicated altitude. On the tarmac the aircraft was indicating 60 ft above the ground with baro set correctly. Is this a simulated baro sensor or indicator error?

Hello, At one point of you approach, typically when established on final, you need to change current set ALT to missed approach ALT. When I fly an ILS approach and the G/S is captured I just can turn the ALT up to the desired value and the T7 stays on G/S captured. Flying a RNAV approach I would need to do that change after the last WPT with a vertical restriction. Now what I experience is that when I change to the higher ALT quickly, the T7 stays on VNAV and continues, but when I just change over slowly it may initiate a VNAV capture. Is that the real behavior you need to pay attention to?

I just have tested it and it is still 59 sec (P3D V2.4)

Thanks a lot!

Hello, As the title says, I have next to the right EGT display graphic a message which reads *FMS in white. I could not find an explanation in the handbook as it is difficult to search for that term. Anyone knows what it means?

So, who is right now? Richard or Kimberly?

Hi, just would like to get confirmation that the anouncment text: Active Sky Next Service Pack 3 has been officially released for both FSX and Prepar3D versions means that this SP3 works also for P3D V2.4?

Sorry Martin, but I think it is relevant to speed and aircraft weight. The default settings are definately way off. Just check the the stall speed at MTOW. While clean it it stalls correct at the end of the white arc, it does not stall at all at the end of the green arc with the flaps down as it should. That is a clear indication of too much lift gain from the flaps. Yes, the PC-12 does arrive at the runway pitch down with Vs x 1.3 but then you pull power and reduce speed so that at Vs x 1.15 you set her down with the nose wheel up. A simple cure is just as people said above!

There are different recomendations on how to fly the plane and some are based on actual use, which often takes more care of an old engine and flying empty for demonstration flights. I suggest to use the settings that I laid out in the flying guide which you can download here: http://forum.sibwings.com/viewtopic.php?f=29&t=1132 There you find recomendations based on flying scenic flights with a full load of curious passengers :rolleyes:

Unfortunately this is also related to the way some of the designers at ORBX do assign surfaces. That causes a very high friction. There is no way to set the friction per aircraft in FSX. FSX calculates that by itself depending on weight, wheel diameter and definde surface. But i'm in the process to add bit more thrust on low RMP which should help. We also rework the cooling effect of the cowling flaps. It is all very much work balancing the various parameters. Just keep the cowling fully open on ground and play with power and brakes to steer her. There is a general improvement for the friction problem in FSX which you may google or find in Pete Dawson's forum here: http://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/

Guys, I will be reworking the ground behaviour. With rudder pedals, soft braking and full rudder and some power I got the results that were explained to me from the pilot I worked with. Problem is that FSX never just brakes on one wheel, just puts more on one or the other side, ner 100%. So I try to find a better balance between steering from brakes and support from rudder by propwash. Until then you may modify the aircraft.cfg and link the tailwheel to the rudder. Replace: point.0 = 1, -25.85, 0.00, -2.48, 1300, 0, 1.0, 180.0, 0.2, 2.0, 0.9, 0.0, 0.0, 0 by point.0 = 1, -25.85, 0.00, -2.48, 1300, 0, 1.0, 50.0, 0.2, 2.0, 0.9, 0.0, 0.0, 0

Will, I followed your recomendation and it REALLY solved the issue! Thak you very much!

I know that tool but had no reason to use it as new installs do find the proper path to FSX. Could you elaborate why that tool would fix the problem? Can you confirm that it does not exist on your computer with the same add-ons installed?

Changing HDG to TRK does not change this. There is no wind at that situation. It has nothing to do with location as it happens in Anchorage too. So it looks to me as an error in the calculation of the runway display. As said, switching to the B737 and the problem does not exist anymore. And both planes use the same NAV database. Anyone an other idea?