Sign in to follow this  
RPRIEVER

Skeletons in the (PMDG) closet

Recommended Posts

Greetings all,

 

I recently installed FSX onto my new computer, specifically into the SSD. When I installed the PMDG aircraft (737's and 777), I am getting a skeleton plane, both from the outside and from cockpit view. I tried reinstalling the plane thru the OPS center, but that didn't do any good. Any ideas on how to correct this? 

 

Also, I tried copying and pasting my FSX.cfg file, but the forum doesn't allow my to paste it. Forgive my ignorance, but what I am I doing wrong?

 

Many thanks,

Ron

 

 

 

 

 

 

 

 

 

 

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

add HIGHMEMFIX=1 into your fsx.cfg under the [GRAPHICS] section ..and all the skeletons in your closet will disappear :)

Share this post


Link to post
Share on other sites

Already done. I should have mentioned this earlier, and it is the #1 answer to this issue. However, the problem remains......

Share this post


Link to post
Share on other sites

Ron, u are one in a million, u can see what actually is under the skin of PMDG planes !!

Seriously, issue ticket and surely Ryan will help u.

Share this post


Link to post
Share on other sites

Actually, if you're using the EZDok add-on, the skeleton issue can arise.  I think you have to re-run the EZDok CONFIGURATION MANAGER utility. This is caused if you add a new aircraft to your FSX setup and fail to re-run the Configuration Utility.  You must run it after each new aircraft install.

 

There is a folder in your programs list called EZCA (If I remember right) and one of the programs within that folder is the configuration manager.  Be sure FSX is NOT running when you run the configuration manager!!

 

Worst case, some users report having to uninstall and then reinstall EZDok, but that's quite a PITA.  If you have to go there, be sure you export your camera views for each aircraft, or you may lose them.  Export them to your desktop.  After reinstall, import them back into EZDok.

Share this post


Link to post
Share on other sites

Robert,

 

The EZDOK solution has come up before, however I don't currently have it installed. I was waiting to be sure the PMDG acft were running normally before re-installing EZDoc. I've submitted a ticket with PMDG, just awaiting their response.

Share this post


Link to post
Share on other sites

Robert,

 

The EZDOK solution has come up before, however I don't currently have it installed. I was waiting to be sure the PMDG acft were running normally before re-installing EZDoc. I've submitted a ticket with PMDG, just awaiting their response.

I used to get missing fan blades when I loaded up a 777 repaint not done by PMDG, but I resolved it by loading the default "PMDG" version of that paint then changing aircraft. Also the HIGHMEMFIX worked for me when I had the skeleton issue...hope your issue gets resolved 

Share this post


Link to post
Share on other sites

Ron,

 

Despite your PC making mine look pretty weak, the only thing that would cure my skeleton plane (737) was to make repaints at  lower resolution..I.E 2048, or 1024, rather than the 4096 that all paints/ repaints are.

 

When i posted this news, it kinda went unnoticed or was brushed off...

 

If you cant cure the problem any other way then give it a try....you wont notice any diffrence in looks of the repaint quality at a a lower resolution - at normall veiwing distances...and even then if you were to zoom in the diffrence in quality Vs performance isnt werth worrying about.

Share this post


Link to post
Share on other sites

 

 


I used to get missing fan blades when I loaded up a 777 repaint not done by PMDG, but I resolved it by loading the default "PMDG" version of that paint then changing aircraft.

 

Imran,

 

That might have happened because the texture.cfg file inside the texture folder of the non-PMDG repaint was written incorrectly.  The texture.cfg file is supposed to point to shared files in other texture folders.  Take a look at the texture.cfg file in a livery that is working correctly and see if there are differences.  Unfortunately I don't think that's the OP's problem.

 

Mike

Share this post


Link to post
Share on other sites

Imran,

 

That might have happened because the texture.cfg file inside the texture folder of the non-PMDG repaint was written incorrectly.  The texture.cfg file is supposed to point to shared files in other texture folders.  Take a look at the texture.cfg file in a livery that is working correctly and see if there are differences.  Unfortunately I don't think that's the OP's problem.

 

Mike

Hi Mike,It was a problem but now its sorted, thanks for the help.

Share this post


Link to post
Share on other sites

Could try updating .net Framework and/or update graphics drivers.

 

heres the link to raise a ticket

 

http://support.precisionmanuals.com/Main/Default.aspx

 

.NET framework is not used by our products or by FSX itself - it's the runtimes for the MS C# language, which is generally too slow to use in performance intensive applications like FSX. C++ runtimes and DirectX runtimes are all you need to use our products.

Share this post


Link to post
Share on other sites

Ron, is this stock FSX + PMDG or what by way of scenery have you added? Have you made any changes to your fsx.cfg (other than HIGHMEMFIX=1)?

 

Can you try a test with dll.xml renamed?

Share this post


Link to post
Share on other sites

Probably something you did not forget, but just to make sure:

 

Did you install the FSX Servicepacks?

Share this post


Link to post
Share on other sites

Hey all,

 

Just an fyi...I'm running the default PMDG planes (no add-on liveries), along with default scenery. I also have SP2 installed (I also installed SP1 prior to that) . I don't want to install the add-ons until I get this issue fixed.

 

In addition to the HIGHMEM fix, I also changed the max text load to 4096. That's all I've changed in the fsx.cfg file.

 

I sent a ticket to PMDG on Friday  Understandably, due to the holiday weekend I haven't received a response yet, hopefully will get one today or tomorrow.

 

Ron

Share this post


Link to post
Share on other sites

So how did a test with renamed dll.xml come out? Not hard to do. Also have you got DX9 or DX10?


Reason is I just fixed a system with exactly the same skeleton plane problem, an error in dll.xml. Unfortunately done over the phone and I never got to see dll.xml but reinstalled worked. With stock FSX and a PMDG there's very little load and so HIGHMEMFIX=1 is not a "cure" for skeleton planes but more like a cap to the sim load.

 

dll.xml is usually found in:

"C:\Users\<you>\AppData\Roaming\Microsoft\FSX"

Share this post


Link to post
Share on other sites

...so let's say I renamed my dll.xml to dll.xml.sav and run up FSX.

 

If the plane is still a skeleton, then we know nothing loaded from dll.xml can be blamed and it's likely to be a file or folder problem. I would set the Write and Modify permissions for the Users group on the FSX program files folder (allow subfolders), and then try reinstalling the plane. If the plane is drawn in fully with dll.xml renamed, then it's more complicated, we would need to look at what's in the file.

Share this post


Link to post
Share on other sites

if this has not been fixed, the others are right, make sure you run windows update and double check you have the latest drivers.i do see you have windows 8.1, but that should not cause what you are experiencing. if you have the latest drivers, do a complete uninstall of fsx, and i mean everything (per pmdg uninstall guide). then start fresh. Looking at your PC specs, your pc is fine, but with FSX, are you using any service packs or acceleration?

Share this post


Link to post
Share on other sites

I had this as well and I did get it fixed, Unfortunatley I can't rememebr exactly what it was.  Backup your FSX.cfg and let it rebuild another one.

This it what I did and then started putting back tweaks one by one till I found the culprit. Sorry I can't remeber the exact conflicting line.

Share this post


Link to post
Share on other sites

OK guys.....problem solved (I think).

 

I just got a response from the PMDG support team (Paul Gollnick, to be exact). He had mentioned several reports regarding the HIGHMEMFIX and issues with the SP2 (or, if you have it, the acceleration pack). The solution is to simply uninstall SP2 (or the accel pack), and then just reinstall it. Everything else can remain as is.  I just started FSX and the 777 pax version appeared normally. Haven't done any flying yet, will first take my time adding liveries, add-on scenery, etc.

 

Thanks to everyone for their input. And a special thanks to Paul G.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this