Flappie

The absence of heat blur coming from helicopters exhaust is old. I've just bumped the internal report.
All helicopters are affected by this issue (except the AH-64D which apparently does not produce heat blur at all).

This bug was reported a few days ago.

Try the lowest graphic settings (Options > System > Click the "Low" preset button) and see if it works any better.

Thanks for the track. That is very strange indeed.
If I recall correctly, the dynamic weather is obsolete since we got the new clouds (DCS 2.7). It should not be used at the moment.

I agree. When I landed at Kampari, I had no more fuel.
Issue reported.

This issue was reported a week ago.
 

It was reported earlier. I'll bump the internal report.
 

The loadout fix for mission 6 is part of today's OB update.

Fixed with today's OB update.

Hello.
The easy way:
Run the mission. Once the mission is loaded, exit DCS. Browse to "C:\Users\your-login\AppData\Local\Temp\DCS\Mission". Create a zip archive which contains the whole content of this folder. Rename the .zip file to "mymission.miz". Voilà.

Let's see. The error springs from this part of the script:
if event.id == 1 then -- shot event, from player if not event.weapon then return end local uComms = bombRange.unitComms[uName] if bombRange.mustCheckIn and (not uComms.checkedIn) then if bombRange.verbose then trigger.action.outText("+++bRng: Player <" .. pName .. "> not checked in.", 30) end return DCS says uComms equals nil.
This looks like a custom script issue.

This was reported earlier, but thanks for your post anyway. 👍
Devs are working on this issue.

It's LShift + F10.
You can simply disable them in the DCS options:

Fixed in today's OB update.

Yes, the JAS39 mod is known to cause such issues with current OB. The Su-30 mod as well

This issue is reported. A fix is in the works.
 

Update the Su-30 mod.

Empty these folders:
Saved Games/DCS.../fxo Saved Games/DCS.../metashaders2 then see if DCS keeps crashing.

You probably have "TAA" anti-aliasing enabled in your DCS settings. You should try MSAA instead.

@Riddick The next OB update should fix the problem.

Hi @Miccara. You're not the first one with unexpected failures in your mission file. We don't know how it happens, but it's quite easy to solve.
Here's a small guide:
If you have any idea how failures got there, I'm all ears.

I don't see any changes.
Procedure:
Store a target:
Lock a target. Specify the target type (first line of the PRTz box). Press "SEND MEM". Open the ABRIS map and check that you've just created a marker for this target. Send this target through the datalink:
Reset the Shkval (Backspace). Specify the target type (now it must be blinking on the ABRIS map). Press "All" to select all 3 wingmen. Press "SEND MEM". Send your target marker to the Shkval:
Reset the Shkval (Backspace) if it's not already in that state. Specify the target type (now it must be blinking on the ABRIS map). Press "DL INGRESS". Light up the Shkval (O). BS3 datalink.trk

Fixed with today's OB update.

Issue 1 and 2 fixed with today's OB update.

Fixed with today's OB update.