Cydrych

It is due to the dynamic bort texture. ED's dynamic bort texture is offset a few pixels from the surface so you end up with a shadow of the whole rectangle texture and not just the numbers. The bort textures also also have fixed roughness and metallic values which causes problems too. You can see the texture outline on any livery using dynamic borts. The only way around it is not using the dynamic bort or trying to blend it as best you can with the surrounding area but it will still be noticeable at some angles.

Thank you to those who serve.

Thank you to those who serve.

Nice work.

You will need both these in the description.Lua. The first is for the pilot in the plane and the other is for the pilot out of the plane. They use the same texture and texture file name but one is "details" and the other "getails". I'm not sure if ED made a typo or if it was intentional. Also is that my desert flight suit? {"pilot_F16_hmd_details", DIFFUSE , "pilot_f16_helmet_details", false}; {"pilot_F16_hmd_details", NORMAL_MAP , "pilot_f16_helmet_details_normal", false}; {"pilot_F16_hmd_details", SPECULAR , "pilot_f16_helmet_details_roughmet", false}; {"pilot_F16_hmd_getails", DIFFUSE , "pilot_f16_helmet_details", false}; {"pilot_F16_hmd_getails", NORMAL_MAP , "pilot_f16_helmet_details_normal", false}; {"pilot_F16_hmd_getails", SPECULAR , "pilot_f16_helmet_details_roughmet", false};

Check that the line for the HMD texture in the description.lua is set to false. If it is true it will pull the default texture.

Download link added to first post.

Could bee. Maybee. Might bee on user files soon. Anyway here is a Thursday teaser.

They went all out on the tigermeet liveries this year. Pure works of art. Recreating them in DCS is 100s of hours of work unless someone has access to the raw art files. It won't be me but there are some really complex liveries on user files so someone might be crazy enough to take them on.

Skin is now on user files.

buzz buzz

If you have camo texture there are 2 possibilities. 1. The 370 gal tank textures are not in the plane's livery folder but the description.lua code is correct. 2. The lines for the 370 gal tank textures in the description.lua are incorrect and the tank textures are in the plane's livery folder. #2 is more likely because a few years ago ED changed the 370 gal tank texture file names. These are the default lines in the description.lua for the 370 gal tanks. If you want to use ED's default textures change "false" to "true" and if the livery has custom tank textures leave it false. -- F16_bl50_Fuel_Tank_370Gal {"F_16_Tank_370", 0, "Fuel_Tank_370Gal_diff", false}; {"F_16_Tank_370", 1, "Fuel_Tank_370Gal_NM", false}; {"F_16_Tank_370", ROUGHNESS_METALLIC, "Fuel_Tank_370Gal_diff_RoughMet", false};

Thanks for the compliment.

Speaking from my own point of view model viewer is already kind of janky and if we are forced to use anything less capable than what model viewer is now I probably will be done making liveries. Skinning is time consuming and tedious so making it more difficult just to make it harder to pirate textures and models, yeah, I just can't be bothered with it. I also don't want to have to load the whole game either. I'm already pushing the RAM limit with GIMP and MV open because I'm usually working in multiple files at the same time to match textures up on different parts of the plane. So if it has to be hooked into the DCS files for account verification and decryption then release "model viewer 2.0" as a free module you download into the DCS root directory and have it launch from the DCS launcher as a standalone app after you sign in.