Jump to content
Sign in to follow this  
ZEROpH

Ai Plane's Textures Are "white"

Recommended Posts

I recently added a Lufthansa repaint of the default 747 into FSX using the SDK Traffic Compiler. The plane showed up fine, with textures. After moving about the airport, I went back to the Lufthansa 747 and the textures went to the default "White" scheme that came with FSX. Also, later on, I hear a call to ground from Pacifica ### Heavy, when I looked, that plane was also in the default "White" scheme. (Also, by "White", I mean the textures with the game, not referring to the directX 10 issue). I was wondering if anyone has heard of this, if there is a fix, or an issue with the aircraft.cfg, or if I remove that plane from the route, will I get the Pacifica textures back? It seems to happen when it wants too, strange..-CJ

Share this post


Link to post
Share on other sites

OK, let me ge this straight. Did you add this texture to your list of 747s, or did you replace a texture in your list of 747s? If you've never done this before, things can turn out funny. Always make a backup of any folder you alter. If you replaced a texture properly, then that plane will now be in the default ai flight plans list. If you added a texture, then indeed you need write a FP. There are much, much easier(and better) tools to use than those found in the SDK. A little more info, please.Bob


Bob

i5, 16 GB ram, GTX 960, FS on SSD, Windows 10 64 bit, home built works anyway.

Share this post


Link to post
Share on other sites

Bob,I added the texture into its own texture.* folder, and then added the airplane into the aircraft.cfg. After that I created the flight plan using the SDK, which I have become fairly familiar with. The plane shows in the game with the Lufthansa textures at first, but after a few minutes of me hanging out at the airport, the Lufthansa textures turn to the default white scheme, all other 747's present at that time also turn to white. I've only had this problem with repaints for the default aircraft. I'm thinking it may have something to do with the fallback in the texture.cfg (which seems to be correct) or something to do with the Fresnel_Ramp.dds that came with the downloaded texture (which I am unable to open using DXTbmp). Thanks for the response!-CJ

Share this post


Link to post
Share on other sites

The SDK comes with an image tool that will open your Fresnel_Ramp.dds.Bob


Bob

i5, 16 GB ram, GTX 960, FS on SSD, Windows 10 64 bit, home built works anyway.

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  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...