Gierasimov

Does it for other maps? 
I never seen BDA for anything destroyed on the map unless I used triggers for such specific mission objectives. On the other hand coming from the two decades of ED sims I never tried without the trigger in DCS 

It won't ... it is part of the core experience with such objects. Even if it is on ED 'to-do' list, most likely after (long after) Marianas WWII project. Resources busy with Afghanistan (for years to come) and Iraq (even more years)... 🙂 and nobody wants to assign somebody to fix those two cranes ...

This is fixed @GazAce

In my testing it is looking like the latest update fixed the issue! Thank you @NineLine

Remove pylons is one of the options in ME armament window.
null

also in the jet in mission in re-arm menu

Right, then it is not unit related but the scenery object. Make sure to test this in Caucasus terrain, record short track and post as a bug in the relevant forum section. This is not MIssion Editor bug, so likely nobody will look at it. If it is OK in Caucasus, but not at Nellis, then post the bug report with the track on the NTTR section of the forum. However, understand, that if it happens only for the NTTR terrain, most likely it will never be corrected, given that it is a very minor bug and NTTR is long past the mainstream support.

Hi. Your report here could have been missed as this is NOT the case of AI aircraft bug, so you posted in the wrong section
Issue reported: 
https://forum.dcs.world/topic/353858-296-single-player-logbook-landing-is-not-counted-in-statistics-or-displayed/#comment-5489388

Hi there @Bugfish welcome to the forum. Wrong section, so please have a look at Game Crash - ED Forums (dcs.world) maybe some info for you there already 🙂
Try this first:
 
 

Air-To-Air Missile Development. We plan to migrate the R-27 (AA-10) family and R-73  (AA-11) missiles to a new component structure and flight dynamics. This will be coupled with a new proximity fuse model that accounts for Doppler closing speed, modified seekers, and a more realistic interaction model between the missile and the supporting radar. This will be done within the larger MiG-29 project framework. Other missile types will also be developed in the same way.

9.12A never had it, and ED already presented the 3D model of the module itself in the 2024 & beyond video. 
It's not simply 3D object that needs to be added, remember that one of the systems simulated is the fuel system. 
As much as I would love to have it as I enjoy AAR it is not going to happen.

Up to the mission maker to decide what weapons are available. Even for MP crowd it's going to be nice. 
Completely agree with CrazyGMan.

You would need multiple laser designations for multiple bombs to hit different targets. I had it once with the script that mimics JTAC. So each bomb was set with different code and scripted JTAC was lasing two targets with two laser beams, so when I dropped two at the same time, they went for two distinct target. 
In your situation I assume you were self lasing or DCS JTAC lasing on 1688 a single target / unit, hence no matter how many bombs you drop, they all to the same target based on the configured laser code. 
GBU-10 / 12 glide towards the reflected laser energy constantly, so need some sort of lasing all the way to the shack. 

So, to keep things more realistic, I want to fly Hokum as Russian AF and have Russian FAC. I don't need JTAC at all.
I can still do it all with triggers, custom voiceovers, and radio commands to achieve what I want, it just takes time to do it all. That's it.

@iQyThradz3137i
This is what I did:
In Livery description.lua you need to remove lines that start with "F18C_BORT_NUMBER_ and replace them with the new format:
    {"f18c1_number_nose_right", 0 ,"F18C_1_DIFF_323L",false};
    {"f18c1_number_nose_right", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true};
    {"f18c1_number_nose_right", DECAL ,"empty",false};
    
    {"f18c1_number_nose_left", 0 ,"F18C_1_DIFF_323L",false};
    {"f18c1_number_nose_left", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true};
    {"f18c1_number_nose_left", DECAL ,"empty",false};    
    {"f18c2_kil_right", 0 ,"F18C_2_DIFF_323L",false};
    {"f18c2_kil_right", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true};
    {"f18c2_kil_right", DECAL ,"empty",true};
    
    {"f18c2_kil_left", 0 ,"F18C_2_DIFF_323L",false};
    {"f18c2_kil_left", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true};
    {"f18c2_kil_left", DECAL ,"empty",true};
    
    {"f18c1_number_F", 0 ,"F18C_1_DIFF_323L",false};
    {"f18c1_number_F", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true};
    {"f18c1_number_F", DECAL ,"empty",true};    
    {"f18c2_number_X", 0 ,"F18C_2_DIFF_323L",false};
    {"f18c2_number_X", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true};
    {"f18c2_number_X", DECAL ,"empty",true};    
Then, at the end of file you need to include the custom arguments:
custom_args = 
{
 
[27] = 1, -- Tail      change of type of board number (0.0 -default USA, 0.1- )
[1000] = 1, -- Flaps
[1001] = 1, -- Nose
[1002] = 1, -- Kuwait Squadron 
[1003] = 1, -- Australian Squadron 
[1004] = 1, -- Finland Squadron
[1005] = 1, -- Switzerland Squadron
[1006] = 1, -- Blue Angels Jet Team
}
If you want to show bort numbers, the line would be similar to this:
{"f18c1_number_nose_right", DECAL ,"F18C_bort_number_PL",false};
and then custom args must be changed from 1 to 0.0
for example:
[1000] = 0.0, -- Flaps
[1001] = 0.0, -- Nose
 

Hi GazAce, 
This is the effect of the new way how bort numbers are created via description.lua. 
I can send you amended files to replace, need to test on Aussie pack first.

Thank you @SUNTSAG
Values worked for me when throttles moved to ground IDLE. Adjusted and now the trigger activates when throttles are in OFF position!
This is the best community ever! Thanks guys!
null