jbee1a

Rick, You need to run the command prompt as an administrator. From the search menu type 'cmd' then right click the Command Prompt and run it as administrator. cd to the appropriate directory and run the setup program. I hope it works, the MD-11 is a great airliner. Jonathan Bee

Hi torfih, it's probably due to the scenery priority. In your Custom Scenery folder there's a file called scenery_packs.ini. The order of the entries is important. Basically, airports are at the top and meshes are at the bottom. X-plane checks for new scenery and will put new entries at the top of the scenery_packs.ini. You'll need to edit the file and put the w2xp entry near the bottom, above any meshes. There are explanations around , try this: http://www.x-plane.com/?article=changing-custom-scenery-load-order-in-x-plane-10. regards, jbee1a

In the scenery library move the MyTraffic scenery to just above the propeller objects scenery.

It was nicknamed the Frightening.

PFPX exports to AAX format.

thank's for the suggestions - I'll do some tests.

There's a 1 1/2 hour video on youtube - md80 klax/ksfo, so you can see what you're letting yourself in for. It's a great 'plane - egpws, weather radar, hot starts, flame outs , icing effects, functioning circuit breakers, pmdg navdata - if you prefer procedures over visuals you can't go wrong, but be prepared for a lot of reading. In its day it was ahead of anything pmdg had on offer (but not now). As mentioned above, they're looking for a 3D artist so we may get a VC refresh. Buy it! JB

After having problems with the VC in the PMDG 777, namely the eye point shifting by itself depending on latitude or other factors, I download the Opus demo to test the Live Camera Control and see if it was a solution to my problem. At a northern latitude I set up a few cameras based on the captains view point, i.e., forward view, MCP view and FMC view. It's great, it works. Move the plane to an airport close it the equator and the view point has moved further back, distorting my view point. I opened the LCC dialogue and reset my eye point, so far so good. However, the problem is I have to reset the eye point for each camera individually: with more than 10 camera positions this isn't practical. Is there any way to adjust the eye point for all cameras simultaneously and preserve the setting for the duration of the flight, even after switching to an outside view and back? That would be a workable solution for me. I've researched enough to know that the 'shifting eye point' is a core FSX (and P3D) bug, (not PMDG), but so far I've spent more time fiddling with the VC than studying the 'plane - I would like to fly it once in a while. Any suggestions would be appreciated.

PFPX exports AXE flight plans.

I had exactly the same issue. My views were set up at Manchester and worked the way I wanted. I positioned the plane for tutorial 1 and the eye-point moved backwards into the headrest. I've been researching this: it's a bug in the core FSX VC implementation that calculates the eye-point. Both EZCA and OpusFSX are victims of it. All aircraft with a VC are effected by it too, but the effect is more pronounced with 'long' aircraft like the 777 and varying latitudes. I've also noticed that the eye-point tends to 'drift' on its own accord on long flights. I appreciate that the 777 VC is a work of programming genius but, apart from having something attached to my head, I've haven't found a workable solution for this. Jonathan Bee

This is related to my post above. I set up my EZDOK view profile at Manchester (EGCC) at it works okay around the northern latitudes. If I try the same profile at Male (VRMM) the eye point is moved backwards (inside the headrest), therefore the click spots are 'blocked'. This happens in the NGX (and OpusFSX Live Camera) as well. It seems to be related to latitude but I don't know why that would move the eye-point. Does anyone have any ideas on a solution for this? Thanks. Jonathan Bee

The eye point was in the headrest. I moved the eye point forward and everything works now. Thanks for your help. Jonathan Bee

I have the same problem with Tutorial 1. With Aerosoft's VRMM, in the 777 I can pan and zoom around the cockpit okay but none of the click spots work. The NGX and MD-11 both work fine but the 777 doesn't. At all other add-on airports the 777 works normally. I don't use EZCA or TrackIR. Does anyone have any ideas what could be causing this? Jonathan Bee