Flappie

Hello Riddick, it's very nice of you to report bugs after your first days.
Nice bug to start with! It seems the standard Su-25 is also able to refill an airbase at no cost.
Issue reported. 👍
Next time you report bugs, please, please, create one thread per bug. It's way easier for us to follow.
Issue 1 was reported earlier and the report was bumped some days ago. Issue 2 has just been fixed internally. The fix should be in the next OB update. Issue 3 is now reported. 👍 Thanks!

Issue reproduced. I found a few more immortal bridges.
I'll report this. Thanks for the heads up. 👍

Hi. This will be fixed in the next OB update.
In the meantime, you can use this temporary user fix by Buzzline:
 

Found it! The "F10 View Options" is responsible for this bug. If set to "My aircraft" or "Map only", some jettisoned weapons can't be seen in F6 view.
Issue reported.

Hi. The DXGI_ERROR_DEVICE_REMOVE symptom can have many causes. Here's a sum up of known causes reported in this forum:
Windows power plan is saving energy while playing (ensure it's default power plan at least - not "eco" or anything like it) GPU driver is faulty (you can try uninstall/reinstall it - you can even use DDU to make sure it's fully uninstalled) GPU is overclocked too much RAM is overclocked too much PSU is faulty or not strong enough GPU is faulty CPU is clogged with dust ASUS GPU Tweak is playing you tricks Aorus Graphics Engine is enabled G-Sync Windowd/Fullscreen settings and DCS Windows/Fullscreen settings are not happy with each other

I used this software once for my job: https://www.nirsoft.net/utils/usb_log_view.html
It worked very well.
Your log doesn't shows the crash. It was probably an eternal freeze, which means no clue in the log file unfortunately.
I've just found someone's thread about what looks like the exact same issue. You should definitely talk to the guy:
 
Another one disabled G-Sync and the issue was gone:
 
You might have something conflicting with G-Sync.

You're welcome. Thanks for your feedback. 👍

This was fixed internally. The fix should be in the next OB update.

Hi. The problem is known and a fix is coming.
 

Hi. There's a clock icon down below the ME. It's called History filter. When enabled, the ME hides units that weren't used at the date you set for the mission.
Either change mission date or disable History filter.

To start with, I'm hoping that my little story below will convince you that I'm far from being a professional when it comes to PC optimization! My real-life job is to test software with no 3D involved.
My PC is behaving like yours when playing DCS:
GPU running @100% CPU staring at me like "give me more work, I'm bored". This made me believe for a very long time that my PC was GPU-limited, since many gamers use to say that whatever reaches 100% first is bottlenecking your PC.
A few weeks ago, I did a lot of performance tests using different DCS settings. I was astonished to get such low FPS while using moderate graphics settings. Someone suggested that maybe my PC was simply CPU-limited, not GPU-limited. I first thought: "impossible, my GPU is always @100%", it can't do more. Then I did a little search on the Internet and found out that Nvidia drivers make the best of the GPU whatever happens, which means NVIDIA GPU @100% doesn't necessarily means the GPU is the limiting factor (explanations).
I had an idea: since MSAA is post-treatment and dealt with by the GPU, why not comparing FPS using no MSAA, MSAA x2 and MSAA x4? Surprise! This made little difference, and my GPU was still running @100%.
OK, time to test my CPU. I had been using a Ryzen 2700X for many years without overclocking it, and my RAM was supposed to run @3000 MHz. I realized my motherboard BIOS was very old and decided to update it to the latest version. Another suprise: my motherboard is compatible with the much celebrated Ryzen 5800X3D. This could come in handy if my tests were to show I'm CPU-limited...
After I updated the BIOS, I checked my FPS: no change (blue curve 😐). Then I re-set my memory frequency using the new BIOS: I chose 3000 MHz (my RAM's "nominal" frequency). "No change", I thought...wait! (orange curve 😀). Then I tried my motherboard "Gaming Boost" (automatic CPU overclocking mode) (yellow curve 🤩). Then I tried both "Gaming Boost" + "Precision Boost Overdrive" together (green curve 🤨, let's get back to 3).  

I'm now convinced my PC is CPU-limited. As I said earlier, I plan to buy a Ryzen 5800X3D. I'll let you know the results.

Hi. Chances are your Windows pagefile is stored on your HDD. And you don't want that, because your HDD is certainly the slowest of all your drives.
If that is the case, either let Windows handle your pagefile (it should move it to a fast drive, on its own) or manually move it to a SSD  with plenty of free space (at least 50 GB).
https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/

@Elphaba is right, something is off:

I'll report this. 👍

All three are now reported. Many thanks. 👍

Crash reproduced and reported. Thanks for the heads up. 👍

Thanks. Issue reported. 👍

Hi. Try these:
Rename your "Saved Games/DCS..." folder to "DCS.backup" (do NOT delete it, it contains your customized controls among other things). Start DCS. If the previous steps didn't help, run a DCS repair and choose "slow" mode.

Issue reproduced and reported. Thanks @Devrim. 👍

For some reason, your track wouldn't show me the attack.
However, I spotted a difference between your mission and ED's: the "Restrict Air-to-Air attack = on" opton is missing for all 3 Su-25 flights.
Add it in and you should be safe.

Sorry, I can't replay your track because it contains mods.

Here's mine, with close-ups on impacts.
It takes quite a number of bullets, it's true, but remember it's only 7.62 mm. As BIGNEWY once said, it's more a matter of vehicle damage model than aything else:
 
Huey minigun vs trucks.trk

Hi. The problem is known and a fix is coming.
 

Hi. This issue was reported some weeks ago. It is caused by Motion Blur.

Many thanks, @Akiazusa.
Issue 2 is now reported, and I asked devs about issue 3.

Issue reproduced and reported as low priority. 👍

Issue fixed. 👍