Jason_Peters

I can't speak to the de-rate as that often requires quite a bit of calculation. However, the aircraft is quite powerful and it's pretty easy to get a big de-rate such as 40 degrees like Marc suggested. For the takeoff flap setting, a general rule with our aircraft anything above 700,000 lbs is typically a Flaps 20 takeoff, anything below that would be a Flaps 10. There are certain exceptions, Flaps 10 provides for a better initial climb and thus obstacle clearance, while Flaps 20 generally shortens the time the aircraft is physically on the runway...so in certain cases based on the available runway we may choose something non-standard.

I’ve flown cargo occasionally using the Atlas livery (USAF 747 operators do their sim training with Atlas) but prefer passenger flights. I’ve typically been simming the -8 as a replacement for the now retired UAL 400’s.

I really enjoy the 747-8, but I’ve found myself flying other aircraft as I often struggle with finding good destinations suitable for her long legs. I typically fly passenger flights with the United livery (UVA Member). I’m wondering if it’s cause I lack a good variety of scenery for overseas destinations? EGLL, PHNL, and OMDB are my only really good overseas sceneries. So, any suggestions? Where is everyone flying? Good sceneries to purchase? Help me spend more time in the -8!

Some things have likely changed for sure. However, much has remained the same too. In certain cases, low-tech is a better solution due to the unique mission of the aircraft. That super high-tech stuff tends to not react well in a post-nuclear environment... lol

Pffft... 1989... not even close to the oldest 747 still in service! I'm flying a few early 70's vintage 747's (E-4B) in the USAF. 2 were built in 73', 1 in 74', and the newest in 1975!

I wish someone would make a TBM at that level for P3Dv4... what a beauty. Systems simulation looks superb, from the videos I've seen of it.

Well, that'll securely replace every GA plane in my fleet... what a dream! Can't wait! Where do I throw my money? HA!

Kyle, you'll find it under "My Account".

Right you are! My fault for my inaccurate & speedy reading. Sorry Karl!

Sigh, They already beat this up pretty good. It's different than the 777. Happy reading!

Kyle, Any idea what the expected wait time is right now? I placed an order around 3:40pm (cst), and got lumped into the no-dowload link issues. Submitted a support ticket and have been waiting. Just curious, I know the PMDG staff is working it. Thanks! Before you ask: it's 3CA-23397090-0477. But I did get sucked into the 'Contact Us' link (Under 'My Account') a half hour prior to coming to my senses and submitting the actual ticket...

Meh, bottom line is the same. You want to enjoy the hobby in the latest and greatest sim environment, you pay for that. Both in the cost of the P3D software, and any add-on software. As the old saying goes... you pay to play.

The price increase reflects the current state of development for each product... FSX as a platform is stable, and will not be further updated. Thus, PMDG knows exactly where the development boundaries are. P3D on the other hand is still actively being developed and updated. PMDG consistently works to take advantage of those new developments, which means the product needs to be constantly updated. You want to work with the latest and greatest FS environment? You pay the latest and greatest price... it is what it is.

Well, it's unfortunate you feel that way. While I agree with some of your sentiment about the cost of PMDG's fine products, this is not the thread to debate that issue. That said, you may consider cutting them some slack. Technology can be a finicky thing, I'm quite sure these releases put a large strain on their server system and during that time a few transactions are sure to get messed up. They don't really have control over when the software decides to hiccup, cough, or barf... they just get to clean-up the mess. Unfortunately, we both got included in that group this time. RSR, and the rest of the group at PMDG will have both of us sorted in no-time I'm sure. I'm just as frustrated as you are, however a little patience goes a long way...

Another with no download link. I'm sure the server is overwhelmed... they'll figure it out, give them some time.

Dan, The wooden trestle over the road at the departure end of runway 30 is still there... in fact, when we depart runway 12 we aren't allowed to set takeoff power in the mighty E-4B until we cross the actual threshold... I think they fear we'll knock it over... LOL

Fun fact, in the 747 there is no specific 3 engine landing checklist. Instead the procedure is part of the Engine Failure and Shutdown checklist and is actually found under the Abnormal Procedures section of the manual, rather than Emergency Procedures. Our checklist in the E-4B, (747-200) even has a note reminding us to plan a "normal approach and landing with normal airspeeds".

A Bonanza would be cool. I'd personally like to see a light jet of some sort, like a citation. Or if I'm really dreaming maybe Carenado could be talked into this... PC-12 with G600 Retrofit Ha!

Looking good Bert! I sent you an e-mail for the autopilot updates. Hopefully we'll see some more aircraft support for this great package soon!

Thanks guys.. working on things now. Is there a way to retain my button/axis assignments from FSUIPC4 and get them over to v5? Also, after moving the Orbx stuff from v3 to v4 can v3 be uninstalled?... I see no reason to keep both installed otherwise..

Getting ready to get started on my install, working on downloading the many updates as we speak... What's the best method to move from v3 to v4? Should I completely un-install and start over? Can stuff be moved? As with many simmers, I can't say I'm excited about an un-install, re-install... ugh time consuming!

Thanks Bert! Okay folks, accomplishing the below will make your AP & YD engage and disengage logic work as Pilatus intended. You'll need to perform a basic edit, and be familiar with FSUIPC. To make the autopilot panel function as described: Backup the original file in case you wish to return to the previous config!! Edit the ASandYD.xml file located in the CustomPC12 folder Bert provided. Remove entirely the code pertaining to the yaw damper. Be sure to leave the section for the anti-skid fix!. Now to map the AP disconnect button: Using FSUIPC's button & switches menu, map your disconnect button. You may make it "profile specific" i.e. specific to the PC-12 if you desire, I did. -select the correct button on your yoke or joystick -Check the box "select for fs control" -The control sent when button pressed: "Autopilot off" parameter "0" -The control sent when button released: "Yaw Damper off" parameter "0" Works like a champ. The AP control panel works as described in the manual and the AP disconnect on the yoke turns off both the AP & YD.

For those who are using FSUIPC and want tthe AP & YD logic to work correctly I may have found a solution that works! Works great on my machine, just did a bunch of touch & go's turning the AP & YD off every which way I could think of! However, you'll need to edit the ASandYD.xml file located in the CustomPC12 folder Bert provided, and you'll also need FSUIPC to assign buttons. Since it requires editing the work Bert graciously provides, I'll withhold sharing specifics till I get the go-ahead or Bert can just add the instructions to the next version of his Mod package.

Bert, Understood, these are your mods and I really appreciate you sharing them with all of us. I keep saying I'm gonna learn to understand xml... the stuff is mostly unreadable to me. Thanks for the hint on the line to edit... I may give that a whirl if it continues to bug me. You did raise a valid point about the yaw damper staying on though. I remember it was common to a bunch of Carenado aircraft in the past for the yaw damper to remain on in the background even though it indicated off, frustrating indeed.

See my post above, that's only true if you use the autopilot disconnect button on the yoke. If you press the AP button on the panel, the YD should remain engaged. I do agree though, if it can't be made to work correctly, I'd rather be able to use the rudder after disconnecting the autopilot.