XCLTM3

Thanks for the clarification Ryan.....much appreciated.

Thanks Dan.........I'll just continue onward and kill the alarm.

Thanks Trent! Interestingly enough, according to the T/O data in the CDU, we're supposed to set trim at 2.50 - and yet sometimes, this red flag comes up?

Hi Trent, just to clarify - do you mean these 3 buttons are functioning in the PMDG 777? To test, I have pushed any of the appropriate 3 glareshield buttons instead of the corresponding buttons/prompts in the CDU but it never responds, hence I must use the CDU. PS: the dispatchers at HO are heavily tied to the union.....LOL!

Occasionally, on spooling up for take off I'm receiving a red flag warning on the upper DU "Stabilizer Configuration". As far as I can tell, everything has been configured correctly including trim. I was not able to locate this problem here in the forum, or in the documentation. Appreciate any assistance. PS: this is in relation to my 777-200 which has all the relevant updates.

I was led to believe here in this forum that the 3 buttons on the glareshield ie: ACPT, CANC, RJCT are linked to the Datalink system (this was prior to SP1 being released). Since the release of SP1 and the few added functionalities with Datalink, is there any chance PMDG will update these 3 buttons to become functional? Therefore, we will have the choice to use the 3 buttons on the glareshield or the CDU buttons.

Tried that too (a few times), but didn't get any result. I will take a look at your recommendations for making a fresh NI profile - just to ensure I'm not missing a procedure. It truly is odd that I cannot get NI to carry the full load from FSX (by unticking the internal FSX AA switch). As a point, NI settings recommended by you, Nick Needham, Ryan Maziarz (PMDG) & Kostas - and still the jagged edges and other anomalies if I untick the internal FSX AA. Ergo, I now relent to using the internal FSX AA. As I pointed out earlier, it would seem that there are other users experiencing this anomaly and I can't quite deduce why there are some of us seeing this problem, and others who are not. Thanks for your assistance.

Good 1 Mark...... I was so intrigued with the thread title I just had to look.......LOL.

My FSX is in DX9 mode (refer to my post yesterday) and I need to check the "Anti-aliasing" box within FSX. I don't use DX10.

Noticed that some users reported different experiences with reference to the FSX DX9 "Anti-aliasing" button in Settings. Either, you could get NI to solely carry the settings and have the FSX switched or ticked to off position, or, some needed the Anti-aliasing button ticked. I can confirm that on my system, I must tick the "Anti-aliasing" button in FSX - without it, I can clearly see FSX is suffering jagged lines and a host of other issues. Strange thing indeed.

Thanks for the clarification Michael.

Hi Kyle, thx for chiming in here. I had previously read that section (Intro Manual) but it still does not explain (as far as I've read): 1. Why does the "FLT NUMBER UPLINK" message appear & 2. What steps to take to action the message prompt (particularly considering that I manually entered the flight number - see below) For example: Again today, during preflight I utilised the Route Request to choose a predetermined flight plan. Once the flight plan was loaded, I manually entered in the flight number. I went through all the other steps (ie Perf data uplink, ALTN Uplink, Weather uplink, DES FORECAST Uplink) and once everything was set, the "FLT NUMBER UPLINK" message displayed. The only way to get rid of the message is to press the CLR key on the CDU. I was thinking that perhaps there was a step / or steps to follow to access/load the uplink and have it enter the flight number automatically - same as the procedure to load ALTN Uplinks, etc. Appreciate some clarification on this.

I checked the FCOM V2 but no specific details on "how to use the datalink to update the Flight Number uplink?". I understand how to use the other features of the datalink such as the ALTN Update, Forecast update, etc. Tried manually inserting the FLT Number, but this does not remove the FLT NUMBER UPLINK message. Thanks in advance!

Anyone???

Just want to check in and see if anyone else has reported the same condition since installing SP1 for the 777-200LR. Each time I initially load the 777-200LR at any airport (default of 3rd party), my frames and smoothness suffer for a period of around 2-3 minutes. After that period of time elapses, everything goes back to normal in terms of frames and smoothness and no stuttering. This has only happened since installing SP1. This is a dedicated FSX machine, and I have not installed any other software or made any changes to FSX or the PC prior to, or since installing SP1. It seems to me that there is a process or series of processes occurring in FSX's background that are causing this drop and lack of smoothness during the initial 2-3 minute startup at the gate. I have been using the default PMDG startup -> ie: engines ON at the gate. PS: It's not a huge deal breaker, as I have adapted to the situation by just waiting out the 2-3 minutes until everything settles back (ie sit at gate) into normal again. SP1 otherwise has been absolutely phenomenal......utterly pleased with it.

Ponteeman, the time frame you suggested of every 15 mins or so may be something to do with your settings in ASN (if you have ASN)? If you have ASN, is it set to update every 15 mins? I would check that first. I have SP1 on the 200L/R with ASN and everything is working smoothly thus far - tested the WXR, company uplinks, etc etc.

Kyle! Stop using avatars of Michael Schumacher!!! LOL!

What we're missing is a dedicated painter like Chris Hicks who produced excellent dirty & clean paints/textures for the PMDG 737NGX.......if only someone with the expertise could do the same for our 777's! That way you could pick & choose which specific airline/aircraft was clean or dirty.

Thanks Felix for the clarification. Much appreciated!

In terms of navdata within the G1000 and as it pertains to Australian data....it's not good at all. Missing many crucial points, and, even if they're listed in the MFD, they don't show up in the actual database when scrolling through. So, if I wanted to manually add navdata (ie waypoints, VOR's, etc) - is this achievable with the Carenado TBM850 G1000?

It'd be the real deal........only PMDG.

There is absolutely nothing unusual about this at all. And if you have EZDOK (EZCA), it can be more difficult depending on your settings (but you can alter it and reduce it down if required). Mind you, I've spent a lot of hours in full motion sims (737 800 & 747 400) and it can be difficult at times using your own hands/fingers to manipulate various buttons and dials in the flight deck whilst there is some bumping and buffeting from winds (and even whilst you're taking off or taxiing depending on how smooth the ground is)

Can anyone with expertise (FSX & Windows os) verify that this is not a hoax? If I see some real data I'd be very interested.

I thought I'd put my two cents in here - I've had several take-offs (with ASN of course) during thunderstorms. And on climbing out after take-off, the wind shear alarm was sounding - the plane was bumping around in updrafts/downdrafts - and my climb speed (via auto throttle) was continually being hampered down to almost stall speed with a few stall warnings. To correct this I either: 1. dis-engaged auto throttle and controlled the thrust levers manually to ensure a safe climb out speed, or 2. increased the climb speed in the window by 10+ knots 3. Flew manually (no auto pilot) to maintain a low climb rate to ensure a safe speed was maintained throughout the wind buffeting I would conduct either of these until I was out of the "danger zone". Mind you, until ASN came along I never experienced this in FSX........I love it! Bring it on!

Thanks to all for the replies. I'm a little more enlightened now in relation to my questions.