How to remove bort number on liveries?

[BlueAngel]

Is there a way to remove all bort numbers on tail, nose and top? Really annoying on some liveries as it's also poorly implemented with no alpha channel, just a lazy number set with painted background.

[ST0RM]

In the skin description file, you can change "FALSE" to "TRUE" on the decals you dont want to show.

[BlueAngel]

In the skin description file, you can change "FALSE" to "TRUE" on the decals you dont want to show.

 

Sorry, but I don't think that's how that's syntax works. I think that's an instruction to search the current folder and if the texture isn't there it will place a "missing texture" placeholder.

[lee1hy]

insert blank bort_number image and false

[CucoNegron6924]

So, is the bort number the thing I see now on the tail of the F-16C after the last update. Is so, how can I remove it, it looks bad. Is this addition to the liveries supposed to be there?

 

Cuco Negron

San Juan, PR

[magmasta]

insert blank bort_number image and false

 

Can you explain this better? I’m a bit confused on how to remove the bort number.

[fishermanivan]

How about for liveries that don't have any bort entries, like the Norwegian liveries... I copied it from the US Aggressor livery and then it didn't show up at all..

[Badhorsie53]

Hope this helps! Ive noticed this on quite a few skins where bort numbers overlay:(

 

edit description file and add these entries.

 

--F16_bl50_NOUSE_1_DECAL

{"F16_bl50_NOUSE_1_DECAL", 0, "f16_bl50_main_1", false};

{"F16_bl50_NOUSE_1_DECAL", 1, "f16_bl50_main_1_normal", true};

{"F16_bl50_NOUSE_1_DECAL", ROUGHNESS_METALLIC, "f16_bl50_main_1_roughmet", false};

{"F16_bl50_NOUSE_1_DECAL", DECAL, "empty", true};

--F16_bl50_NOUSE_1_BORT_NUMBER_001

{"F16_bl50_NOUSE_1_BORT_NUMBER_001", 0, "f16_bl50_main_1", false};

{"F16_bl50_NOUSE_1_BORT_NUMBER_001", 1, "f16_bl50_main_1_normal", true};

{"F16_bl50_NOUSE_1_BORT_NUMBER_001", ROUGHNESS_METALLIC, "f16_bl50_main_1_roughmet", false};

{"F16_bl50_NOUSE_1_BORT_NUMBER_001", DECAL, "empty", true};

--F16_bl50_NOUSE_1_BORT_NUMBER_010

{"F16_bl50_NOUSE_1_BORT_NUMBER_010", 0, "f16_bl50_main_1", false};

{"F16_bl50_NOUSE_1_BORT_NUMBER_010", 1, "f16_bl50_main_1_normal", true};

{"F16_bl50_NOUSE_1_BORT_NUMBER_010", ROUGHNESS_METALLIC, "f16_bl50_main_1_roughmet", false};

{"F16_bl50_NOUSE_1_BORT_NUMBER_010", DECAL, "empty", true};

--F16_bl50_NOUSE_1_BORT_NUMBER_100

{"F16_bl50_NOUSE_1_BORT_NUMBER_100", 0, "f16_bl50_main_1", false};

{"F16_bl50_NOUSE_1_BORT_NUMBER_100", 1, "f16_bl50_main_1_normal", true};

{"F16_bl50_NOUSE_1_BORT_NUMBER_100", ROUGHNESS_METALLIC, "f16_bl50_main_1_roughmet", false};

{"F16_bl50_NOUSE_1_BORT_NUMBER_100", DECAL, "empty", true};

 

 

 

 

--F16_bl50_NOUSE_2_BORT_NUMBER_001

{"F16_bl50_NOUSE_2_BORT_NUMBER_001", 0, "f16_bl50_main_2", false};

{"F16_bl50_NOUSE_2_BORT_NUMBER_001", 1, "f16_bl50_main_2_normal", true};

{"F16_bl50_NOUSE_2_BORT_NUMBER_001", ROUGHNESS_METALLIC, "f16_bl50_main_2_roughmet", false};

{"F16_bl50_NOUSE_2_BORT_NUMBER_001", DECAL, "empty", true};

--F16_bl50_NOUSE_2_BORT_NUMBER_010

{"F16_bl50_NOUSE_2_BORT_NUMBER_010", 0, "f16_bl50_main_2", false};

{"F16_bl50_NOUSE_2_BORT_NUMBER_010", 1, "f16_bl50_main_2_normal", true};

{"F16_bl50_NOUSE_2_BORT_NUMBER_010", ROUGHNESS_METALLIC, "f16_bl50_main_2_roughmet", false};

{"F16_bl50_NOUSE_2_BORT_NUMBER_010", DECAL, "empty", true};

--F16_bl50_NOUSE_2_BORT_NUMBER_100

{"F16_bl50_NOUSE_2_BORT_NUMBER_100", 0, "f16_bl50_main_2", false};

{"F16_bl50_NOUSE_2_BORT_NUMBER_100", 1, "f16_bl50_main_2_normal", true};

{"F16_bl50_NOUSE_2_BORT_NUMBER_100", ROUGHNESS_METALLIC, "f16_bl50_main_2_roughmet", false};

{"F16_bl50_NOUSE_2_BORT_NUMBER_100", DECAL, "empty", true};

 

 

 

 

 

---F16_bl50_FIN_DECAL

{"F16_bl50_FIN_DECAL", 0, "f16_bl50_kil", false};

{"F16_bl50_FIN_DECAL", 1, "f16_bl50_kil_normal", true};

{"F16_bl50_FIN_DECAL", ROUGHNESS_METALLIC, "f16_bl50_kil_roughmet", false};

{"F16_bl50_FIN_DECAL", DECAL, "empty", true};

 

--F16_bl50_FIN_BORT_NUMBER_001

{"F16_bl50_FIN_BORT_NUMBER_001", 0, "f16_bl50_kil", false};

{"F16_bl50_FIN_BORT_NUMBER_001", 1, "f16_bl50_kil_normal", true};

{"F16_bl50_FIN_BORT_NUMBER_001", ROUGHNESS_METALLIC, "f16_bl50_kil_roughmet", false};

{"F16_bl50_FIN_BORT_NUMBER_001", DECAL, "empty", true};

 

--F16_bl50_FIN_BORT_NUMBER_010

{"F16_bl50_FIN_BORT_NUMBER_010", 0, "f16_bl50_kil", false};

{"F16_bl50_FIN_BORT_NUMBER_010", 1, "f16_bl50_kil_normal", true};

{"F16_bl50_FIN_BORT_NUMBER_010", ROUGHNESS_METALLIC, "f16_bl50_kil_roughmet", false};

{"F16_bl50_FIN_BORT_NUMBER_010", DECAL, "empty", true};

 

--F16_bl50_FIN_BORT_NUMBER_100

{"F16_bl50_FIN_BORT_NUMBER_100", 0, "f16_bl50_kil", false};

{"F16_bl50_FIN_BORT_NUMBER_100", 1, "f16_bl50_kil_normal", true};

{"F16_bl50_FIN_BORT_NUMBER_100", ROUGHNESS_METALLIC, "f16_bl50_kil_roughmet", false};

{"F16_bl50_FIN_BORT_NUMBER_100", DECAL, "empty", true};

[magmasta]

Hope this helps! Ive noticed this on quite a few skins where bort numbers overlay:(

 

edit description file and add these entries.

 

Thanks. That helps a lot

[popov]

Still can't get rid of this only digit '0' in the front... any solution ideas ? For the rest on the livery I managed to get it to work ok.

 

[Shahdoh]

Bort numbers are many times in the description lua 1 digit at a time, so it may be that you missed an entry, or need to find what it is for that particular one and add it in.

 

 

 

Edit:

Some things to keep in mind concerning the description.lua entries, lets break down what each section does:

 

{"su27_tex01", 0 ,"Su27_tex01_for",true};

 

"su27_tex01", is the link to the actual part that is getting painted - this MUST match with the info in the .EDM file

 

0 , this section is for the value for the type of layer or texture this is going to be (2=Spec / 0=Dif / Decal / etc) there are others but do not know the specifics

 

"Su27_tex01_for", is for the name of the texture that will be used on this part. If the next value is true, this MUST be in the texture.zip file for the aircraft (usually the default name). If next value is false, you can name the texture file anything you please and it should be in the same folder as this description.lua

 

true tells DCS whether the texture file is in the default location (in that aircraft's texture\Su-27.zip file) or (false) = its in another location, usually the same folder the description.lua is in.

Edited May 3, 2020 by Shahdoh

[dannyq8]

Have a look here

 

https://forums.eagle.ru/showthread.php?t=266835&page=3

 

In particular this post

 

https://forums.eagle.ru/showpost.php?p=4267441&postcount=22

[Top Jockey]

Need your help guys.

 

How can I remove not only the bort numbers, but more hard - the gray rectangles which keep getting there (the ones in red arrows), even after editing the .lua file...

 

Thank you.

[Burnie]

Yep, I'm trying to find the answer to this too

[Top Jockey]

So, can anyone who uses add-on liveries on the F-16 share some light here ?

[BarTzi]

So, can anyone who uses add-on liveries on the F-16 share some light here ?

 

Post your lua file so we can have a look and tell you what to change. If you are not the maker of that livery, check the user files section incase the creator updated it already. If you didn't read it by now - here's the official explanation on how to change it: https://forums.eagle.ru/showpost.php?p=4341890&postcount=72

Edited June 1, 2020 by BarTzi

[Top Jockey]

Post your lua file so we can have a look and tell you what to change. If you are not the maker of that livery, check the user files section incase the creator updated it already. If you didn't read it by now - here's the official explanation on how to change it: https://forums.eagle.ru/showpost.php?p=4341890&postcount=72

 

Thank you.

Although it happens in every add-on livery I have for the F-16.

 

Here it goes one of them - the NSAWC Desert camo, image at post #13.

description.lua

[Top Jockey]

Anyone ?

[TWISTER312]

SOLUTION

 

The solution was given elsewhere on this forum :

 

 

kim raver height

[Top Jockey]

The solution was given elsewhere on this forum :

 

 

kim raver height

 

Sorry, everything keeps showing exactly as in the image at the post #13 - both the numbers and the gray rectangles...

[TWISTER312]

Perhaps you added it in the wrong place?

It should be placed here :

 

 

[Top Jockey]

Perhaps you added it in the wrong place?

It should be placed here :

 

 

 

Well... now that I look at the folder hierarchy closelly, let me ask :

 

Shoulg those changes be done at the "descriptiom.lua" of the respective add-on livery, or at the one in the "default" F-16 folder ?

[Top Jockey]

No joy.

 

I'll post the two .lua files I've changed according your recomendations.

Their respective folders are:

 

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\F-16C\Liveries\F-16C_50\default

 

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\F-16C\Liveries\F-16C_50\F-16A NSAWC Desert

description1.lua

description2.lua

[BarTzi]

No joy.

 

I'll post the two .lua files I've changed according your recomendations.

Their respective folders are:

 

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\F-16C\Liveries\F-16C_50\default

 

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\F-16C\Liveries\F-16C_50\F-16A NSAWC Desert

 

All of the changes should be applied only to the description.lua of the livery in question.

 

I attached the description file to my post. It's really just a simple copy-paste of the arguments to the end of the file.

 

It would be easier to contact the original creator and have him update the files.

description.lua

[Top Jockey]

All of the changes should be applied only to the description.lua of the livery in question.

 

I attached the description file to my post. It's really just a simple copy-paste of the arguments to the end of the file.

 

It would be easier to contact the original creator and have him update the files.

 

Thank you BarTzi - numbers and gray rectangles gone from the NSAWC livery !

(Also tried with the Portuguese Air Force livery, and it works 5 stars now.)

 

My previous error, I was placing all the "strings" before the "name" tag, and not after it - as it should be.

 

Many thanks and @Twister312 also. :thumbup: