Bruce_D

You are using the wrong folder. The correct is \USER NAME\Saved Games\DCS\Liveries\F-16C_50\

Hi, Sorry for the delay, I was preparing launch :) I will try my best to explain the step by step. 1) I will use the polish air force skin as an example: https://www.digitalcombatsimulator.c...files/3306489/ Open the folder “Polish Air Force” located in \USER NAME\Saved Games\DCS\Liveries\F-16C_50\Polish Air Force 2) Use “Notepad++” to open the file named “description.lua” (if you don’t have ‘Notepad++’ you can Google it and download or use the Windows Notepad, but I recommend ‘Notepad++’). The file will look like this: 3) On the same place as the picture below you are going to add the following code: --F16_bl50_NOUSE_1_DECAL {"F16_bl50_NOUSE_1_DECAL", DIFFUSE, "f16_bl50_main_1", false}; {"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", DIFFUSE, "f16_bl50_main_1", false}; {"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", DIFFUSE, "f16_bl50_main_1", false}; {"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", DIFFUSE, "f16_bl50_main_1", false}; {"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", DIFFUSE, "f16_bl50_main_2", 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", DIFFUSE, "f16_bl50_main_2", 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", DIFFUSE, "f16_bl50_main_2", false}; {"F16_bl50_NOUSE_2_BORT_NUMBER_100", DECAL, "empty", true}; --F16_bl50_FIN_DECAL {"F16_bl50_FIN_DECAL", DIFFUSE, "f16_bl50_kil", false}; {"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", DIFFUSE, "f16_bl50_kil", false}; {"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", DIFFUSE, "f16_bl50_kil", false}; {"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", DIFFUSE, "f16_bl50_kil", false}; {"F16_bl50_FIN_BORT_NUMBER_100", ROUGHNESS_METALLIC, "f16_bl50_kil_roughmet", false}; {"F16_bl50_FIN_BORT_NUMBER_100", DECAL, "empty", true}; 4) Done! Just save the file and play! Important notes: 1) For other skins you may have to change a few other parameters that weren’t necessary for this particular skin. So I suggest you to study my code and compare with what Akatsuki publish (he published a complete code for more elaborated skins) to change different skins: https://forums.eagle.ru/showpost.php?p=4252394&postcount=4 2) It is optional, but I have added the following code at the end of the “description.lua” file: countries = {"POL"} With this code the skin will only appear for the Polish F-16 and not for all F-16 from other nations on mission editor. Hope I could help.

Don't worry, give me a few minutes so I will prepare an explanation on how to do it. One of this skin I have and fixed it. I will use it as an example.

Could you send me a screenshot showing the error? Did you create this skin?

I've just edited the Description.lua file. add the following code to the descripition.lua: --F16_bl50_FIN_DECAL {"F16_bl50_FIN_DECAL", DIFFUSE, "--NAME OF THE KIL.dll OF YOUR'S SKIN --", false}; {"F16_bl50_FIN_DECAL", DECAL, "empty", true}; {"F16_bl50_FIN_DECAL", ROUGHNESS_METALLIC, "--NAME OF THE KIL_ROUGHMET.dll OF YOUR'S SKIN --", false}; --F16_bl50_FIN_BORT_NUMBER_001 {"F16_bl50_FIN_BORT_NUMBER_001", DIFFUSE, "--NAME OF THE KIL.dll OF YOUR'S SKIN --", false}; {"F16_bl50_FIN_BORT_NUMBER_001", ROUGHNESS_METALLIC, "--NAME OF THE KIL_ROUGHMET.dll OF YOUR'S SKIN --", false}; {"F16_bl50_FIN_BORT_NUMBER_001", DECAL, "empty", true}; --F16_bl50_FIN_BORT_NUMBER_010 {"F16_bl50_FIN_BORT_NUMBER_010", DIFFUSE, "--NAME OF THE KIL.dll OF YOUR'S SKIN --", false}; {"F16_bl50_FIN_BORT_NUMBER_010", ROUGHNESS_METALLIC, "--NAME OF THE KIL_ROUGHMET.dll OF YOUR'S SKIN --", false}; {"F16_bl50_FIN_BORT_NUMBER_010", DECAL, "empty", true}; --F16_bl50_FIN_BORT_NUMBER_100 {"F16_bl50_FIN_BORT_NUMBER_100", DIFFUSE, "--NAME OF THE KIL.dll OF YOUR'S SKIN --", false}; {"F16_bl50_FIN_BORT_NUMBER_100", ROUGHNESS_METALLIC, "--NAME OF THE KIL_ROUGHMET.dll OF YOUR'S SKIN --", false}; {"F16_bl50_FIN_BORT_NUMBER_100", DECAL, "empty", true};

Great that the slider worked. Try positive curves. In my case, my throttle physically makes an arc so I have to compensate it.

In your case you can not use curves. Your stick has a great similarity with the real plane stick. Just for a comparison my stick has half the arc of yours and 1/3 of the precision. Thats why I need curves and you don't.

Hi, Here is a post where I asked the same question about slider: https://forums.eagle.ru/showthread.php?t=238778&page=6 The negative value was a tip that one guy gave me on the forum so I started to test. I compared the position of my throttle with the rpm of the plane. For example, on the f-14 I discovered that my best curve was -15 and the f18 is -14, which is very similar with the tip that I received. If you take a look on the movements of the throttle and the negative curve of the slider graphic you will see the similarity. I tested curves from -10 to -20 and compared the rpm movement. The curves on my rudder are because my rudder is on my stick, so I control it with my hand. Some times, during turns I saw that I was using involuntary the rudder, so I put a curve to prevent this undesired movement. Hope I could help.

Right

I have programmed the 3 rotarys of my joystick to press a button instead of use a axis. In one of then I use the radar elevation and works perfectly. Check your joystick's software to see this possibility. I know it is possible to do that with the saitek software.

I've tried Chuck's curves (he uses 15 for x and y), but the best for me was 25 x and y with a dead zone 4 For throttle (very important) I use slider with -14 . Chuck's manual does not give his throttle's curve on the manual. For rudder I use 25 with a dead zone of 4. After finding this curves for my joystick the AAR become easy. Waste a little beat of time to find the best curves for your joystick, you will fell the difference. My joystick is a X52 Pro

Hi, Because we have a toy joystick at home it's fisical movements are different from the game stick a throttle movement. To correct this problem we have to tune the axis of the joysticks. At leats 90% of the problems that I used to have with AAR was due to the fact that my joystick config was wrong. With a wrong tune even a small input on your joystick increases the plane AoA more than necessary to hit the basket. The same happens with throttle. Even a small imput increases dramatically the speed. This video shows the way to tune your joystick's axis: Remember to input a curve on your joystick and a slider on your throttle. Hope This can help

Check this tutorial at 18:05 minutes:

Hi, Did you tune the axis of your joystick correctly? That's the best advise that I can give you. After I manage the correct tune AAR become so easy. I spent 2 months without playing and had no problem to come back and do an AAR on the firts attempt. It's amazing the difference between a good and a terrible tune can do. Good luck

I've contact support and ED solved the problem, now it is working!

Tks! Problem solved!

Hi, I'm a Steam owner of BS1. I didn't find where I have to send a screen shot to upgrade my BS2 key. Can someone help me? Tks

Hi, It does not work for me because I have a steam version of BS1. I was playing with BS2 before the last update. Steam does not give me BS1 CD Key, so I cannot use the link and update the key. Does anybody has the same problem? Tks

Same

+3

Hi, For the situation described I use 'Search Then Engage' or 'Search Then Engage In Zone' on the "Advanced (Waypoint Actions)". Here an example, the F-14 will only attack when the enemy reaches 10nm distance from the F-14 waypoint. F-14 Engage Test.miz

Hi, I’ve improved again and correct an error. Now it works for the 4 wingmen: On the function 'Qfuel(Gfuelplane, numero)', 'Gfuelplane' is the group name, 'numero' is a number between 1 and 0 that represents the % of fuel for each unit of the group.

Thanks! It worked and the game didn’t crash.

Hi guys, I came back to this tread because I managed to create a function that checks when the runway is damage and you can use it during the entire mission. Function CheckBase: And here is an example on how to use it on a script: I’ve attached a mission for the Persian Gulf as an example. Runway attack test.miz

I’ve improved the function, so now if the group is destroyed the script will not give an error message.