Sign in to follow this  
Flyboy

Partial Fuselage texture & skin loss in external views

Recommended Posts

Fianlly got of the ground in PMDG Tutorial 1.5.

Changed to chase view and this is happening....

Partial loss of the aircraft's fuselage skin and texture color on wings changed...

Never happened before and have been using it the original tutorial.....

Does give me an idea for a translucent plane though.....

 

http://fsfiles.org/flightsimshotsv2/image/700

 

Any thoughts?

highmem=1 is enabled.....

and it is steam.

 

Thanks

Will

Share this post


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

Any thoughts?

highmem=1 is enabled.....

and it is steam.

 

Full names - first and last - in all posts.

 

Looks like either the HIGHMEMFIX=1 (sorry to repeat it, but you wrote "highmem=1" in your post, which won't do it) issue, or you're running out of memory due to high settings in the sim. Additionally, it could be an issue if you loaded the 777 more than once in the same sim session (changing liveries, etc.).

Share this post


Link to post
Share on other sites

Kyle listed the most likely issues; in rare cases it could be a video driver issue but in that case there are many other tells that something is wrong.

Share this post


Link to post
Share on other sites

Double checked the HIGHMEMFIX=1 and didn't have it.

Changed the config and all was well until 20 mins out of kiad.

This is the current state of the aircraft....

 

Well.... OZ is down as is ORBX website so i cant post the image...

Essential, all is well and beautiful except the Tail, Stabilizers and Turbine housings are black.

 

Thanks for any help...

Will Charles

  • Upvote 1

Share this post


Link to post
Share on other sites

Get a copy of Process Explorer as recommended in the Introduction, it would be handy right now in looking at how much system and GPU memory is being committed by P3D.

 

Try updating your vidia driver, but I don't see the connection to Orbx. You know of course that the HIGHMEMFIX statement goes only the [GRAPHICS] section, just trying to rule out assumptions.

Share this post


Link to post
Share on other sites

Just a final report...

Seems to solve itself but need to wait it out.

I did add the highmem statement in there...

 

Thanks again....

Will Chalres

Merry Christmas & Happy New Year!

Share this post


Link to post
Share on other sites

You shouldn't need the HIGHMEMFIX=1 entry if using FSX Steam Edition. My understanding is that Dovetail have now encorporated this fix when they recompiled it. The fix is only for FSX SP2/Acceleration.

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