Ok, so I have owned the PMDG 737 for about a month now, and everything was great until about a week ago, when suddenly it wasn't. A lot.

There are two major reasons for this:

 

1) My panel states have stopped saving when I save in fsx (using the ; key type save). This is a major problem as I load my flight and suddenly I am in an aircraft with no FMC flight plan, no autopilot and an IRS which is crying softly to itself. The aircraft initialises, and the engines are on etc., but the FMC is unprogrammed and the pressurisation panel is reset to 10,000ft. Thus, I have a lot of useless saves that are about 25 minutes into the flight.

 

2) The FMC has suddenly decided to not accept some waypoints. For example, whilst inputting flights from Cardiff to Malaga Arpt, Cardiff to Ibiza, and Manchester to Malaga (using the default FSX flight planner) I will encounter at least one or maybe two waypoints that the FMC refuses to recognise, even when I try to input them without using airways.

 

Also, at the same time, I have lost most of the exterior model of the airplane. I have two very pretty wings, some magic floating doors, a big white box with PMDG written on it at the front, and the rest is invisible. Now, I don't claim to be an aircraft expert - but I don't think that's right :P

 

I am running FS2 Crew (the PMDG 737 version), Rex Essential, EZdok Camera, and UTX europe, and both fsx and the 737 are patched appropriately. I did notice that all of this trouble started around the time when UTX was installed, but re-installing it didn't seem to help, nor did re-installing the ngx or FS2 Crew. I have also cleared out and re-installed my livery textures. I also recently modded my .cfg file using a website recommended on these forums (by a lot of people) - would that do all of this?

 

Any help is greatly appreciated :)

 

Stephen Cole

Stephen,

 

I run REX, UTX and the EZDock camera. I don't have FS2Crew. I know the external issues (white PMDG cockpit box) can show up depending on how you're interacting with EZDock and normal view selections. You might try temporarily using the "global disable" in the EZDock section under "Addons" and see if that cures your external view issue. I get that sometimes when I go to a view that's not configured in the EZDock view selection interface.

 

I don't get to fly as much as I would like as I spend a lot of my FSX time painting. Can't help you with the FMC and other issues. Haven't had those issues on my end.

 

Steve

Open a ticket with PMDG support. They will help you out.

The white box issue can be sent away by running EZCA config. EZCA needs to add an entry in the aircraft.cfg file to handle changing from VC to external and back correctly. It is possible that an aircraft update deleted this entry.

 

@2: FSX default planner uses 6 years old waypoint database. The PMDG uses one year old database, and that only if you had not had it updated. These waypoints were most likely simply discontinued. Try using rfinder.asalink.com/free for planning.

And in the future, try and make the title of your topic a bit more user friendly, the title "major problems" doesn't reveal any information what so ever. You could have tried "holes in exterior model" or "FMC doesn't recognize waypoints". It makes it easier for people experiencing the same problem to look it up here. Cheers.

Besides what denotes a major and minor problem...jusy wondering!

Thanks for all your help - the problems appear to be solved now. The strange invisible plane problem was indeed due to EZdok camera. The waypoint 'problem' was due to the FSX map being old (time to invest in some flight planning software methinks). As for the lack of panel state saving, I restored my .cfg file to the original and that seems to have solved it.

 

Oh and as for denoting a major and minor problem - two of those problems were stopping me from using the plane at all. Oh, and plus more people will read an article titled major problems (just to go "ooooh, that's bad"), than one titled "minor niggle" or "slight perplexity" :P

 

Thanks again :)

 

Stephen Cole

And in the future, try and make the title of your topic a bit more user friendly, the title "major problems" doesn't reveal any information what so ever. You could have tried "holes in exterior model" or "FMC doesn't recognize waypoints". It makes it easier for people experiencing the same problem to look it up here. Cheers.

 

I feel that was harsh. He did have a few issues there. How was he meant to get them all in the title. Unnecessary in my opinion, Staff or not.

Stephen

 

On your comment about investing in flight planning I use the following it here. Just input your depature and destination locations (ICAO codes) and your planned flight level. Then make sure you select the matching FMC database cycle. The default is 1108 unless you have updated AIRAC. It will even do NATs if you are into flying across the pond.

 

This works fine for me. I copy and paste the results into a Word doc and then print them out to complete my flight docs along with fuel plan, SIDS, STARS and approach plates.

 

Enjoy.

The waypoint 'problem' was due to the FSX map being old (time to invest in some flight planning software methinks).

 

Thanks again :)

 

Stephen Cole

 

This link might help the FSX nav database issue: http://precisionfsn.com/freew.html

I feel that was harsh. He did have a few issues there. How was he meant to get them all in the title. Unnecessary in my opinion, Staff or not.

I am a reporter for avsim news, that is why I have a "staff" banner, I do not have any special forum authority. I am saying this strictly as a forum user. I apologize to Steven if it sounded harsh, but it is more helpful for the people browsing the forums in the future to have titles of topics that actually relate to the problem. Offcourse you can't put 4 problems in 1 title, but you can put some, or open two topics for unrelated problems.