vstuart

It's great to have such recognition from PMDG and is this a fantastic reward for all of us involved with the 744 team at BAV over the years. Thanks to you and your team, and a very happy 2015!

They are correct in terms of IATA equipment codes, which are all three-character designators. But yes, not so useful for ATC, mostly used in airline systems.

Hello Richard, Have you tried running (as admin) the Flight1 Registry Fix tool? The issue sounds similar to previously reported ND problems, which have often been fixed with this.

According to the relevant manual, there is no deceleration level computation for the RTO setting and full hydraulic system pressure is applied. The max available pressure for both MAX AUTO and RTO is 3000 psi, but the deceleration is set at 11 ft/s^2 for MAX AUTO. HTH

Run FSX as administrator.

It's often necessary to enter your position twice in the FMC after selecting the IRS mode selectors to NAV. Try that.

Right-click the knob(s) to increase the associated value.

Good call Paul! I've been experiencing what seems to be the same issue you've described on my new rig, and I'm also using the frame limiter in Inspector. Will report back if this sorts out the problem.

Fuel scavenged from the centre wing tank and pumped into main tank 2 could result in main tank 2 having more fuel than main tank 3, especially if APU usage was brief. To avoid the > X FEED CONFIG advisory message appearing after going tank-to-engine, you could perform fuel balancing: close cross-feed valves 1 & 4; select the override pumps off on tank 2/3, whichever has less fuel, and wait the fuel in the other tank to reduce to the same amount; switch the remaining override pumps off.

Here you go,http://www.texturasb...are&down_id=618Have a nice day,Vince

I've tried the original spotlight.bmp and halo.bmp to no avail. As I understand it, it's the .mdl file itself that defines the position of the taxi/landing light ground illumination. So either REX or A2A has corrupted the .mdl, which I think is impossible, or one of those programs has installed an fx file interfering with the normal operation of ground illumination.

Hi Dan,The default aircraft that appears is that microlight. However, I always choose the C172, go to my gate of choice and then power everything down (electrics, avionics, lights etc). Once it's settled, I select the PMDG 747-400 from the menu.Another thing I notice when first going to top-down or spot camera is a black square around the nose gear that appears momentarily. There's also this halo around the nose of the aircraft in top-down view that grows larger as you zoom out, even when no lights are swtiched on.Strange...

Yes - this only seems to affect the colour and "throw" of the beam, not the position.

Hello guys,This is a seemingly perennial question asked here, but after searching the board I can't find a solution. The screenshot below shows the minor irritation I'm having with the taxi light ground illumination:I've turned on the runway turnoffs to illustrate the problem clearly.I'm not running the DX10 preview. I am running both REX2 and A2A 3D lights. The problem occurs with and without the modified [Lights] section in the aircraft.cfg. I've replaced the original FSX spotlight.bmp as well as trying some other spotlights from REX, none of which have solved the problem. I've checked that the .mdl file's modification date, and it's 2/11/2007.Is this just a known issue with the 747-400X? I have to say that my attention was only drawn to it only after installing the A2A lights, so I can't be sure if the problem was caused by REX or if it existed initially.One last thing, I've noticed that to the right of the taxi lights is a faint halo that grows larger as you zoom out:Hopefully somebody has managed to resolve this,Vincent Stuart

Maybe I've misunderstood your query ("autopilot altitude"?), but to increase the altitude selection on the MCP just right-click the alt knob to rotate it clockwise.Vince

Qas,While you're at it, you could also look into the 747 RR and PW soundpacks from the same developers.Not too sure how they live up to the soundpacks that used to be in the AVSIM library, but here's a couple of preview videos: Vince

Thanks for your help,Did you type the wind into the scratchpad, and click on LSK 1R on the RTE DATA page?I just tried what you said, and got an "INVALID ENTRY" message. Is this because you can only do this once the wind is displayed on the ND (i.e. not during preflight FMC setup).EDIT: I hadn't completed the PERF INIT before attempting to enter winds. All is well now. Cheers Dan! In this respect, the PMDG manual is a little ambiguous as it suggests that there is a separate page to enter wind information for the respective waypoints.Vincent Stuart

Thank you sir for going out of your way to help, much appreciated. I reckon you're correct about the "W>" caption thing, will be interesting to find out how to do this...Vincent Stuart

Perhaps I didn't fully describe my problem.I have no trouble accessing the RTE DATA page, and clicking NEXT PAGE/PREV PAGE. I believe that when the manual says "The entire remaining portion of the flight plan can be paged through using the NEXT PAGE/PREV PAGE keys on the FMC/MCDU keypad", it means that's how you cycle through the waypoints - not how you get to the winds section. I'm wondering how to enter the wind information (if this is possible) for each waypoint, as clicking on any of those LSKs in the above picture you attached doesn't do anything. The FMS manual states: "The WINDS page is accessed using the W> prompt for each associated fix in the RTE DATA pages."Vincent Stuart

Blimey, that was a fast reply. Thanks!I don't quite understand what you mean by "increment the RTE DATA page". I assume you mean "NEXT PAGE"? If so, that didn't help.Thanks for your time,Vincent Stuart

Hi,I'm having trouble accessing the Winds Page in the 747X FMC. From reading the AOM, I gather that you access it via the RTE DATA page by clicking the LSK next to the carat. When I click on the key, nothing happens. Is there actually a Winds page modelled?Vincent Stuart

Thanks for the pointer Larry. Tried the app but didn't improve things (the visual result was the same as using CCC to force AA). I think I've exhausted all options and I bought an nVidia card yesterday. I asked the guy in the thread I linked to if he had managed to sort out the problem (which was noticed months ago), and he also had to buy an nVidia card. Seems there are a few dodgy 4870s about...

Thanks for the suggestion Larry - I'll give it a shot but I wouldn't want to compromise visual quality further for what should seemingly be a standard task for a mid/high-end graphics card such as the HD 4870. I'm guessing the problem isn't isolated to liveries: take a look at the white apron lines surrounding the PMDG 747 in the screenshots for example. I do get a hell of a lot of shimmering as well.Seems I'm not the only one with this issue, as it has been discussed in another forum without conclusion: http://www.flightsimworld.com/forums/index...t&p=2065555VinceP.S. Just noticed the rule about screenshot size, sorry about that.

Thank you TechguyMaxC for the prompt reply and advice. I was under the impression that neither ATI nor nVidia cards use true supersampling anymore, but I went ahead and enabled the hybrid SSAA in CCC (adaptive anti-aliasing set to quality). The following screenshot was taken under the same settings as in the OP, but with the hybrid SSAA enabled. Note that the AI liveries are fine, but that the PMDG's (which happens to be a 32-bit livery) isn't. The terminal building also looks in good shape. In fact, to my eyes, enabling hybrid SSAA has had no effect at all.To reiterate, I've tried the various settings, and have tried using ATI Tray Tools. I think this issue was raised a while ago in another forum, but wasn't resolved IIRC.Vince

The attachment above appears to have been corrupted, so here is the screenshot posted again: