Flappie

An update is planned for legacy missiles affected with the "speed wall" issue, but it seems the Hawk missile needs it first since it's unable to hit a plane 10 000 m high.
Issue reported.

See my post here: 
This is a terrain issue, not an Mi-24P issue.

The issue was caused by a strange modification of the mission (the UH-60A is "uncontrolled" yet starts in the air). Devs issued a fix which prevents the combination of these two settings at once). It will be applied in the next DCS core update.

@Raffi75 The "zoom" feature of the Mi-24P module is not an actual zoom, it simply switches between two large pictures with different scales. Since there is only one picture, you see black when you try to display the second picture.

I can't open your .miz file because of mods.
AFAIK:
IR markers : TGPs are not supposed to show IR markers. There used to be a bug in DCS and it was fixed in December. However, you should be able to see IR makers when wearing NVGs. Lasers : One cannot visualize lasers, even through NVGs. Only aircraft systems "see" where a laser points at ("LST", Laser Spot Tracker), but they won't draw any "light ray".

It was reported earlier. 👍
https://forum.dcs.world/topic/368255-static-pad-single-gives-wrong-external-category-ship/
 

This issue has been fixed with today's update.

Texture issue fixed in today's update.

Texture issue fixed in today's update.

The next update should fix this issue. The date is not known yet.
 

Thank for the heads up. It looks like the error was spotted internally. A fix is on its way.

When "live" (non-static) enemy units are present in an airbase or FARP, they capture the base, which is what happens here:

No idea why SP lets you spawn at the base, though.
EDIT: I think I understand the difference between SP and MP. SP missions start with the player. I assume base is BLUE at T=0, so the player is spawned. Then, one second later, the base turns RED.
In MP, you pick at slot at T>0, the base is already RED.

This should be fixed in the next update (same issue than this one).

Thank you, I'll check these aircraft compared to others.
Generally speaking, if you set Visibility setting to the max in DCS, if a light happens to disappear too quickly, it's model-related, which means a change has to be done on the 3D model of the object.

For me, it works as long as I call the proper radio menu (ARC-210).
 
JTAC_OK.trk

If found a way. I redid the mission and it worked:
I removed all "Hold" commands (because they don't seem to work along with "Embarking"). I set the second "Embark" with a "ON LAND" waiting time of 5 minutes. But if I do the same things to your mission file, it doesn't work. There must be an explanation... 🤔
I couldn't have the infantry group stop after the last disembarking.
EASY-emb_fix.miz

1. Ensure your Windows Power Mode is enough (Settings > System > Power > In "Power mode", choose between "Balanced" and "Best performance").
(note my PC is currently set to "Best power efficiency" and I don't have your issue)

2. Ensure Power consumption and carbon emissions option is disabled (right below "Power mode").
(disabled on my PC)
3. If Hardware Accelerated GPU Scheduling is enabled, disable it (Settings > System > Display > Graphics > Click "Advanced graphics settings" then disable "Hardware Acceleration GPU Scheduling").
(disabled on my PC)

@Mric29 I suspect Dynamic weather. It is active in both missions, and you may not know but it is obsolete and should not be used until it is redone.
Can you try the same mission with Static weather and tell me if you keep reproducing the issue?

@Northstar98 This should have been fixed in October. Can you please confirm it is fixed for you?

Then you are certainly affected by this bug:
It's reported internally.

OK, I'll report this then.

The crash comes from the F-15E dll. This is a module-related crash. The thread will soon be moved to the F-15E subsection of the forum.

I checked the mission files: two missions happen over Caucasus (13 and 14), and one happens over the Channel ("Channel bonus"), but this last one is not "listed" in the campaign, which means it won't cause you any trouble in case you don't have the Channel terrain installed.
 
In case you won't or can't install the Caucasus terrain, here's what you need to do:
1. Move these two files away from the campaign folder (.\DCS World\Mods\campaigns\P-51D The Blue Nosed Bastards of Bodney):
BNBOB - 13.miz BNBOB - 14.miz 2. Now, make two copies of "BNBOB - 01.miz" and rename them using these names:
BNBOB - 13.miz BNBOB - 14.miz

Issue reported.
Thanks for the heads up.

Have you sensed a changed in the air? Because I've just tested a first fix yesterday. I've asked for some more fixes (I spotted a few more issues). Stay tuned.