FC3 Texture Bug with F-15C (screenshot intensive)

[Home Fries]

I discovered a bug with the F-15C texture mapping when a custom external fuel tank texture is used (like the new Adversary Super Flanker skin). Quite simply, if you use a custom PTB texture, then you will get corrupted mapping if you mix custom helmets or flightsuits with defaults.

 

To explain further, I ran four tests in the same mission (flight of 4 F-15Cs on the runway) using the default Adversary Super Flanker skin and a couple of personalized variants that have "pilot_F15_00_helmet" lines in the definition.lua. This example is shown with the same skin (personalized variants) so you can readily see the differences, but this bug is also present when completely different texture sets are selected.

 

 

First Test:

First test involved the player aircraft being the default Super Flanker skin (Skin A), -2 being a personalized Super Flanker skin with a custom aggressor helmet (Skin B), and -3 being another personalized Super Flanker skin with a "pilot_F15_00_helmet" line calling for the "pilot_f15_helmet" texture (Skin C). Note that Skin A does not have a "pilot_F15_00_helmet" line in its description.lua.

 

Skin A (default) looks normal:

 

Skin B (custom helmet) displays the default F-15 helmet texture and maps the custom helmet texture to the PTB. EDIT: Note the white rank insignia (USN LT); Skin B has a custom flightsuit texture as well.

 

Skin C (description.lua specifically calls default helmet) shows the same artifact:

Second Test:

The second test just changed the order. This time I led with Skin B, followed by Skin A, and then Skin C.

 

Skin B looks normal. You can see the custom helmet as well as the custom flightsuit and colored PTB.

 

Skin A maps the PTB texture to the helmet and uses the default texture for the PTB.

 

Skin C looks normal (because it specifically calls for the default helmet texture).

 

Third and Fourth Tests:

For the third test, I inserted the following line to Skin A's description.lua (just prior to the PTB line):

{"pilot_F15_00_helmet", 0 ,"pilot_f15_helmet",true};

I then repeated the order of the first two tests, and everything worked as it should.

 

Conclusion:

Right now there appears to be an issue when description.lua files with lines left out (allowing for default mapping) are mixed in the same mission with description.lua files that call for custom textures.

 

The first skin is always normal, but any skin that does not specifically call textures to the same material names will show corrupted textures on the following material name.

 

I have noticed this mostly with custom PTB textures, but this may happen with other combinations as well.

 

The work-around solution is to add lines for the flightsuit, helmet, and PTB to every description.lua, and specifically call the default texture if you don't want a custom texture (most instances).

 

 

Here are the description.lua files for each of the skins used in testing:

 

Skin A (default Super Flanker). Note that the helmet line I added is remmed out; enabling this line fixes the bug with that skin.

livery = {
   {"f15nose", 0 ,"f15_noseF",false};
   {"f15nose", 3 ,"f15_decolF",false};
   {"f15bottom", 0 ,"f15_bottomF",false};
   {"f15bottom", 3 ,"f15_decolF",false};
   {"f15centr", 0 ,"f15_centrF",false};
   {"f15wingl", 0 ,"f15_wrL",false};
   {"f15wingl", 3 ,"f15_decolF",false};
   {"f15wingr", 0 ,"f15_wrF",false};
   {"f15stab", 0 ,"f15_stabF",false};
   {"f15stab", 3 ,"f15_decolF",false};
   {"f15numbers", 0 ,"f15_numbers",true};
   {"pilot_F15_patch", 0 ,"pilot_F15_patch_65A_sqdn",true};
   {"pilot_F15_00_body", 0 ,"pilot_f15_00_a",true};
--    {"pilot_F15_00_helmet", 0 ,"pilot_f15_helmet",true};
   {"f15PTB", 0 ,"f15_PTBF",false};
}

Skin B (my personal skin with a custom flightsuit, markings, and helmet):

livery = {
   {"f15nose", 0 ,"f15_noseF_noname",true};
   {"f15nose", 3 ,"f15_decolF_drh",false};
   {"f15bottom", 0 ,"f15_bottomF",true};
   {"f15bottom", 3 ,"f15_decolF_drh",false};
   {"f15centr", 0 ,"f15_centrF",true};
   {"f15wingl", 0 ,"f15_wrL",true};
   {"f15wingl", 3 ,"f15_decolF_drh",false};
   {"f15wingr", 0 ,"f15_wrF",true};
   {"f15stab", 0 ,"f15_stabF",true};
   {"f15stab", 3 ,"f15_decolF_drh",false};
   {"f15numbers", 0 ,"f15_numbers",true};
   {"pilot_F15_patch", 0 ,"pilot_F15_patch_65A_sqdn_drh",true};
   {"pilot_F15_00_body", 0 ,"pilot_f15_drh_a",true};
   {"pilot_F15_00_helmet", 0 ,"pilot_usn_agrs_helmet",true};
   {"f15PTB", 0 ,"f15_PTBF",true};
}

Skin C (a personalized skin that specifically calls the default flightsuit and helmet):

livery = {
   {"f15nose", 0 ,"f15_noseF_noname",true};
   {"f15nose", 3 ,"f15_decolF_neph",false};
   {"f15bottom", 0 ,"f15_bottomF",true};
   {"f15bottom", 3 ,"f15_decolF_neph",false};
   {"f15centr", 0 ,"f15_centrF",true};
   {"f15wingl", 0 ,"f15_wrL",true};
   {"f15wingl", 3 ,"f15_decolF_neph",false};
   {"f15wingr", 0 ,"f15_wrF",true};
   {"f15stab", 0 ,"f15_stabF",true};
   {"f15stab", 3 ,"f15_decolF_neph",false};
   {"f15numbers", 0 ,"f15_numbers",true};
   {"pilot_F15_patch", 0 ,"pilot_F15_patch_65A_sqdn_neph",true};
   {"pilot_F15_00_body", 0 ,"pilot_f15_00_a",true};
   {"pilot_F15_00_helmet", 0 ,"pilot_f15_helmet",true};
   {"f15PTB", 0 ,"f15_PTBF",true};
}

Hope this helps.

Edited February 27, 2013 by Home Fries

[Witchking]

Great detective work. :) Glad you found the solution. :)

[333Lancer]

F-15 C texture issues

 

Thanks for that homefries I have a Question ? It seems this update has affected other f-15 skins as well have you noticed that . Example i selected the 125 th wing and shows the 493 skin on the plane. Not sure if you have the same issue.

[Home Fries]

Lancer,

 

I'm not aware of a 125th Wg default skin; the only 125th Wg skin I'm aware of is the Mod Eagle scheme by USAFMTL. If you don't have the proper skin that is called for, the game will default to one of the original skins.