Flappie

Look no further: your C:\ drive is as full as can be:
Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 0.2 GB Total Space: 113.8 GB File System: NTFS Model: Samsung SSD 840 Series Drive: D: Free Space: 181.3 GB Total Space: 476.9 GB File System: NTFS Model: Samsung SSD 850 EVO 500GB Drive: E: Free Space: 503.7 GB Total Space: 953.9 GB File System: NTFS Model: KINGSTON SA2000M81000G It badly needs some air. Try to free up at least 20GB.
Also ensure your pagefile is stored on another drive (a fast one, with at least 50GB of free space).

Here is your crash stack:
2022-08-05 21:05:05.702 INFO APP: Invalid pilotid, initiator pilotid: 26, target pilotid: 0 2022-08-05 21:05:10.994 WARNING LOG: 2 duplicate message(s) skipped. 2022-08-05 21:05:10.994 INFO EDCORE: try to write dump information 2022-08-05 21:05:10.994 INFO EDCORE: # -------------- 20220805-210511 -------------- 2022-08-05 21:05:10.995 INFO EDCORE: DCS/2.7.16.28157 (x86_64; Windows NT 10.0.22000) 2022-08-05 21:05:10.995 INFO EDCORE: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe 2022-08-05 21:05:10.995 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 0A748C15 00:00000000 2022-08-05 21:05:10.998 INFO EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World;C:\Program Files\Eagle Dynamics\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: '2278-' 2022-08-05 21:05:10.998 INFO EDCORE: OS-Version: 10.0.22000 () 0x100-0x1 2022-08-05 21:05:11.231 INFO EDCORE: 0x0000000000488C15 (DCS): SW + 0x162DD5 2022-08-05 21:05:11.231 INFO EDCORE: 0x0000000000487469 (DCS): SW + 0x161629 2022-08-05 21:05:11.231 INFO EDCORE: 0x0000000000476572 (DCS): SW + 0x150732 2022-08-05 21:05:11.231 INFO EDCORE: 0x0000000000476673 (DCS): SW + 0x150833 2022-08-05 21:05:11.231 INFO EDCORE: 0x000000000012DD26 (WorldGeneral): AI::MultiTaskState::onEvent + 0x56 2022-08-05 21:05:11.232 WARNING LOG: 1 duplicate message(s) skipped. 2022-08-05 21:05:11.232 INFO EDCORE: 0x00000000000C8F38 (WorldGeneral): wControl::onDamage + 0xE8 2022-08-05 21:05:11.232 INFO EDCORE: 0x00000000000C8ECD (WorldGeneral): wControl::onDamage + 0x7D 2022-08-05 21:05:11.232 WARNING LOG: 1 duplicate message(s) skipped. 2022-08-05 21:05:11.232 INFO EDCORE: 0x00000000008CA846 (DCS): SW + 0x5A4A06 2022-08-05 21:05:11.232 INFO EDCORE: 0x0000000000098A90 (Transport): woCar::takeDamage + 0x1C0 2022-08-05 21:05:11.232 INFO EDCORE: 0x000000000008589E (Transport): woCar::PostCollisionProcessing + 0x46E 2022-08-05 21:05:11.232 INFO EDCORE: 0x00000000008A9262 (DCS): SW + 0x583422 2022-08-05 21:05:11.232 INFO EDCORE: 0x00000000008A825F (DCS): SW + 0x58241F 2022-08-05 21:05:11.233 INFO EDCORE: 0x00000000002038D8 (WeaponBlocks): wVStartAutopilot::simulate + 0xEB48 2022-08-05 21:05:11.233 INFO EDCORE: 0x00000000000425D2 (WeaponBlocks): wPNCoeffCalcBlock::operator= + 0xC832 2022-08-05 21:05:11.233 INFO EDCORE: 0x000000000011DA3A (WeaponBlocks): wClusterStarter::simulate + 0x5DEA 2022-08-05 21:05:11.233 INFO EDCORE: 0x00000000000200FA (blocksim): wSimulationSystem::simulate + 0x14A 2022-08-05 21:05:11.233 INFO EDCORE: 0x000000000006AFA9 (WeaponsBase): wAmmunition::simulate + 0x149 2022-08-05 21:05:11.233 INFO EDCORE: 0x00000000001356DB (Weapons): wAmmunitionDecoy::spawnSnare + 0x7CB 2022-08-05 21:05:11.233 INFO EDCORE: 0x000000000013D4F8 (Weapons): wAmmunitionSelfHoming::simulate + 0x158 2022-08-05 21:05:11.233 INFO EDCORE: 0x0000000000067DCA (WeaponsBase): wAmmunition::Class + 0x9A 2022-08-05 21:05:11.233 INFO EDCORE: 0x0000000000003AD6 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x466 2022-08-05 21:05:11.233 INFO EDCORE: 0x0000000000003F3D (World): wSimCalendar::DoActionsUntil + 0x1FD 2022-08-05 21:05:11.234 INFO EDCORE: 0x0000000000841155 (DCS): SW + 0x51B315 2022-08-05 21:05:11.234 INFO EDCORE: 0x0000000000840EAE (DCS): SW + 0x51B06E 2022-08-05 21:05:11.234 INFO EDCORE: 0x00000000008568FB (DCS): SW + 0x530ABB 2022-08-05 21:05:11.234 INFO EDCORE: 0x00000000008276C4 (DCS): SW + 0x501884 2022-08-05 21:05:11.234 INFO EDCORE: 0x0000000000827A9D (DCS): SW + 0x501C5D 2022-08-05 21:05:11.234 INFO EDCORE: 0x0000000001D472DC (DCS): AmdPowerXpressRequestHighPerformance + 0xED62D8 2022-08-05 21:05:11.234 INFO EDCORE: 0x0000000000A7150E (DCS): SW + 0x74B6CE 2022-08-05 21:05:11.234 INFO EDCORE: 0x00000000000154E0 (KERNEL32): BaseThreadInitThunk + 0x10 2022-08-05 21:05:11.234 INFO EDCORE: 0x000000000000485B (ntdll): RtlUserThreadStart + 0x2B 2022-08-05 21:05:11.379 INFO EDCORE: Minidump created.  
I don't see anything obvious in it. Have you tried a DCS repair yet? Choose the "slow" method.

OK. Your game crashes between M2000C and MiG-21bis sounds loading.
See my log:
2022-08-03 18:43:09.685 INFO SOUND: Added sound path: ./CoreMods/aircraft/I-16/Sounds 2022-08-03 18:43:09.712 INFO SOUND: Added sound path: ./CoreMods/aircraft/M-2000C/Sounds 2022-08-03 18:43:09.749 INFO SOUND: Added sound path: ./CoreMods/aircraft/MiG-21BIS/Sounds And yours:
2022-08-04 05:59:45.865 INFO SOUND: Added sound path: ./CoreMods/aircraft/I-16/Sounds 2022-08-04 05:59:45.880 INFO SOUND: Added sound path: ./CoreMods/aircraft/M-2000C/Sounds 2022-08-04 05:59:45.890 INFO EDCORE: try to write dump information 2022-08-04 05:59:45.894 INFO EDCORE: # -------------- 20220804-055946 -------------- 2022-08-04 05:59:45.896 INFO EDCORE: DCS/2.7.16.28157 (x86_64; Windows NT 10.0.19044) 2022-08-04 05:59:45.899 INFO EDCORE: G:\Games\DCS World OpenBeta\bin\edCore.dll 2022-08-04 05:59:45.901 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 1CB6776A 00:00000000 2022-08-04 05:59:45.905 INFO EDCORE: SymInit: Symbol-SearchPath: '.;G:\Games\DCS World OpenBeta;G:\Games\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'Griffin' 2022-08-04 05:59:45.907 INFO EDCORE: OS-Version: 10.0.19044 () 0x300-0x1 2022-08-04 05:59:46.113 INFO EDCORE: 0x00000000000E776A (edCore): edvfs::ZDriver::create + 0x105A 2022-08-04 05:59:46.116 INFO EDCORE: 0x00000000000E67E4 (edCore): edvfs::ZDriver::create + 0xD4 2022-08-04 05:59:46.119 INFO EDCORE: 0x00000000000E0D7E (edCore): edvfs::Metadata::parseMetafile + 0x392E 2022-08-04 05:59:46.119 INFO EDCORE: 0x00000000000E26F3 (edCore): edvfs::Metadata::parseMetafile + 0x52A3 2022-08-04 05:59:46.119 INFO EDCORE: 0x00000000000E484A (edCore): edvfs::mount + 0x6A 2022-08-04 05:59:46.119 INFO EDCORE: 0x000000000082CE07 (DCS): SW + 0x506FC7 2022-08-04 05:59:46.119 INFO EDCORE: 0x0000000000848047 (DCS): SW + 0x522207 2022-08-04 05:59:46.119 INFO EDCORE: 0x0000000000849C80 (DCS): SW + 0x523E40 2022-08-04 05:59:46.119 INFO EDCORE: 0x0000000000847078 (DCS): SW + 0x521238 2022-08-04 05:59:46.120 INFO EDCORE: 0x0000000000007AC5 (lua): luaD_growstack + 0x845 2022-08-04 05:59:46.120 INFO EDCORE: 0x0000000000018D94 (lua): luaS_newlstr + 0x5254 2022-08-04 05:59:46.120 INFO EDCORE: 0x0000000000007E04 (lua): luaD_growstack + 0xB84 2022-08-04 05:59:46.120 INFO EDCORE: 0x00000000000024D6 (lua): lua_call + 0x26 2022-08-04 05:59:46.120 INFO EDCORE: 0x00000000000F3023 (edCore): ED_start_lua_usage_calculation + 0xE3 2022-08-04 05:59:46.120 INFO EDCORE: 0x0000000000007AC5 (lua): luaD_growstack + 0x845 2022-08-04 05:59:46.120 INFO EDCORE: 0x0000000000018D94 (lua): luaS_newlstr + 0x5254 2022-08-04 05:59:46.120 INFO EDCORE: 0x0000000000007E04 (lua): luaD_growstack + 0xB84 2022-08-04 05:59:46.120 INFO EDCORE: 0x00000000000024D6 (lua): lua_call + 0x26 2022-08-04 05:59:46.120 INFO EDCORE: 0x00000000000F3023 (edCore): ED_start_lua_usage_calculation + 0xE3 2022-08-04 05:59:46.120 INFO EDCORE: 0x0000000000007AC5 (lua): luaD_growstack + 0x845 2022-08-04 05:59:46.120 INFO EDCORE: 0x0000000000018D94 (lua): luaS_newlstr + 0x5254 2022-08-04 05:59:46.121 INFO EDCORE: 0x0000000000007E04 (lua): luaD_growstack + 0xB84 2022-08-04 05:59:46.121 INFO EDCORE: 0x0000000000006F7F (lua): lua_getinfo + 0x133F 2022-08-04 05:59:46.121 INFO EDCORE: 0x000000000000812E (lua): lua_yield + 0x9E 2022-08-04 05:59:46.121 INFO EDCORE: 0x0000000000002576 (lua): lua_pcall + 0x66 2022-08-04 05:59:46.121 INFO EDCORE: 0x00000000000F2E89 (edCore): ED_lua_pcall + 0x59 2022-08-04 05:59:46.121 INFO EDCORE: 0x0000000001D53661 (DCS): AmdPowerXpressRequestHighPerformance + 0xEE265D 2022-08-04 05:59:46.121 INFO EDCORE: 0x0000000001D48EE3 (DCS): AmdPowerXpressRequestHighPerformance + 0xED7EDF 2022-08-04 05:59:46.121 INFO EDCORE: 0x00000000008449D6 (DCS): SW + 0x51EB96 2022-08-04 05:59:46.121 INFO EDCORE: 0x0000000001D4724D (DCS): AmdPowerXpressRequestHighPerformance + 0xED6249 2022-08-04 05:59:46.121 INFO EDCORE: 0x0000000000A7150E (DCS): SW + 0x74B6CE 2022-08-04 05:59:46.121 INFO EDCORE: 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14 2022-08-04 05:59:46.122 INFO EDCORE: 0x0000000000052651 (ntdll): RtlUserThreadStart + 0x21 2022-08-04 05:59:46.220 INFO EDCORE: Minidump created.  
Try this:
Go to "G:\Games\DCS World OpenBeta\CodeMods\" Delete both "M-2000C" and "MiG-21BIS" folders (I suspect one of them, but I'm not sure which one). Run DCS repair once more (the utility will download about 5 GB of data).

Thanks. I don't see any sign of DCS_manifest.bin in the log, probably becasue the repair utility doesn't see the problem.
Have you tried the following steps?
Delete /DCS Wolrd.../Mods/aircraft/Mirage-F1/dcs_manifest.bin Run a DCS repair

@Rudel_chw  I've just found an even better source of information here, about the ATAR+: http://www.aeromed.fr/AEROMEDN59.pdf , page 14.
It reads:
This modification was interesting. It consisted in adding to the ATAR 9K50 a true ADF (allumage dans la foulée), just like the one from the Mirage 2000 M53 engine.
It might be necessary at this point to explain how the good old ATAR 9K50 afterburner sequence worked, before comparing it to the ATAR+ sequence. To sum it up, the pilot needed to wait for the 9K50 to almost reach its dry thrust nominal speed engine before initiating the afterburner sequence (figure 1).
With this modification,the afterburner sequence could be initiated in anticipation, well before the dry thrust nominal engine speed (figure 2). Anybody who worked with afterburner-equiped engines knows that igniting fuel in a nozzle strongly reduces the pumping margin because of thermal obstruction [overpressure] if the compressor compression rate is not maintained to a more or less constant level.
Regulation anticipates the afterburner sequence by controlling the nozzle opening. This can be observed on combat aircraft during takeoff. If the nozzle stays closed, the engine will pump and risk a compressor surge, and it won't be able to give the expected thrust boost, a source of disappointment for the pilot. If the nozzle is opened too much, the engine won't ignite.
This ATAR+ modification was only working below 27.500 feet (more or less) because this information was transmited to the engine by the aircraft air data computer. The trick was -among other things- to trigger overspeed (engine speed going from 8400 rpm to 8900 rpm - this was used over M 1.4 until then) as soon as the throttle was moved to the afterburner position, which allowed the engine to meet the proper afterburner conditions 3 to 5 seconds sooner.
 
The author was a test pilot who worked on this ATAR modfication for the SAAF Cheetah.
But I guess the principle is the same for our Mirage F1 ADF. Actually, he says this modification was tested on a Mirage F1AZ.

Two attached pictures are not showing up, but I assume you have already  enabled the F10 AWACS option in the Miscellaneous tab?
If it is enabled and your F10 key is well detected in the Controls options panel, I don't see what can cause such an issue. You should open a support ticket. Log in to the DCS website, click "Support", and "Create a new ticket".

Hi. Please read this thread:
 

Don't forget to set throttle to idle before restarting aircraft.

That's certainly because you have a lot of subfolders. You should consider removing some. See here:
"J:\Program Files\Eagle Dynamics\DCS World OpenBeta\DCS World OpenBeta\_downloads\CoreMods/aircraft/Mirage-F1/Liveries/livery-name/livery.file"
There are two 'DCS World OpenBeta' folders. Remove one of them by moving the second 'DCS World...' into 'Eagle Dynamics' (or into 'Program Files'  directly if that doesn't bother you).
Another solution is to remove the 260 character path limit:
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/

The answer is yes. 👍
 
From April 9th newsletter:
 

Here's a mission with a the second rain preset.
Rain.miz

Try disabling AMD Crossfire.
 

To my knowledge, clouds are still WIP.

Hello. You're getting the DXGI_ERROR_DEVICE_REMOVED kind of crash:
2022-07-19 19:52:28.109 WARNING LOG: 1 duplicate message(s) skipped. 2022-07-19 19:52:28.109 ERROR DX11BACKEND: DX device removed. Reason: 0x887A0006 2022-07-19 19:52:30.043 WARNING LOG: 227 duplicate message(s) skipped. 2022-07-19 19:52:30.043 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2022-07-19 19:52:30.043 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183 2022-07-19 19:52:30.043 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2022-07-19 19:52:30.043 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183 2022-07-19 19:52:30.048 ERROR DX11BACKEND: DX device removed. Reason: 0x887A0006 2022-07-19 19:52:30.442 WARNING LOG: 42 duplicate message(s) skipped. 2022-07-19 19:52:30.442 ERROR DX11BACKEND: failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2022-07-19 19:52:30.442 ERROR DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG 2022-07-19 19:52:30.442 ERROR DX11BACKEND: CreateUnorderedAccessView FAILED. Reason: E_INVALIDARG 2022-07-19 19:52:30.442 ERROR DX11BACKEND: failed to create structed buffer. Reason: DXGI_ERROR_DEVICE_REMOVED To start with, please try updating Windows to version 21H12.
If thats not enough, try disabling your mods. I see a lot of mod-related errors in your log (Scripts/DCSDTC.lua in particular).

There can be two causes:
A. You changed your release version into an OB version, either through DCS_updater.exe, or through SkateZilla's GUI.
B. You have a dcs_variant.txt file in your main DCS folder.
In any case, here's the solution:
Go to your main DCS folder, create a dcs_variant.txt file if it doesn't exist already. Now open this file and simply write the name you want to see next to "DCS.".
Example: banana will give you Saved Games/DCS.banana
In your case, you just write "openbeta", without quotes.

I've just done a small test, and the answer is yes. I was in a Huey, ~500 feet above ground. I flew over a BTR-80 in a dark nigh:
No external lights, no cockpit light: the BTR turret started to spin as I was flying over it. It shot at me, but not for long. External flashing lights on + cockpit light on: the BTR turret started to spin before the BTR firing range, which gave the unit plenty of time to shoot me. UH1H_nolights.trk UH1H_extlights.trk

Yes, that's what's been bothering you. Simply delete the Config folder and you'll be free to use your own snap views.
No, but running missions in the Mission Planner does this. Because that's what it's about: adding some things into the mission, such as drawings in the Ka-50 ABRIS, snap views, thins like that. If you don't want this to happen anymore, don't set your snap views while in the Mission Planner, unless you want them to be saved in the .miz file of course.
If I'm not mistaking, the ME detects when the current map view or zoom level (or both) has been changed. Say you open the mission and the map is centered on Maykop. Then you center the view on Batumi, and exit: the ME will ask if you want to save the changes.

Yes, this was fixed on June 8th. 👍
 

Wow, this actually worked:
 
I initially did, but Windows told me it didn't existed. 😅

Good. Next time it happens to you, just backup the "Saved Games/DCS.../Config/Input" folder. It contains all your custom control bindings.

Hello. I believe you have to follow these steps:
Download the Open Beta standalone installer Run it, select destination folder (a new and empty folder) , and wait for the installer to start downloading the game. Interrupt the download and exit the installer. Now, copy-paste DCS files from Steam to the new destination folder. Run a DCS repair.

Try to place aircraft this way:
Cat 1 Leader A, Cat 2 Wingman A, Cat 3 Leader B, Cat 4 Wingman B.
If you have a flight of four, just place leader on Cat 1, and wingman 3 on Cat 3 (he's the leader of wingman 4).

Look at the end of your log file:
2022-04-19 12:28:53.006 ALERT APP: Unhandled exception: "WrappedAction" unable to create action "NoAction" 2022-04-19 12:28:53.016 INFO EDCORE: signal caught: 'Abnormal termination' 2022-04-19 12:28:53.016 INFO EDCORE: try to write dump information 2022-04-19 12:28:53.018 INFO EDCORE: # -------------- 20220419-122852 -------------- 2022-04-19 12:28:53.018 INFO EDCORE: DCS/2.7.11.22211 (x86_64; Windows NT 10.0.19043) 2022-04-19 12:28:53.018 INFO EDCORE: C:\windows\System32\KERNELBASE.dll 2022-04-19 12:28:53.019 INFO EDCORE: # 00000000 STATUS_SUCCESS at A15F4F69 00:00000000 2022-04-19 12:28:53.020 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\Eagle Dynamics\DCS World;D:\Eagle Dynamics\DCS World\bin;C:\windows;C:\windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'DCS' 2022-04-19 12:28:53.020 INFO EDCORE: OS-Version: 10.0.19043 () 0x300-0x1 One of your unit is assigned a "NoAction" action. I don't know how you got there, but you should be able to find affected unit. Unzip your .miz file, edit the "mission" file it contains, and look for the string "NoAction".

Here's a handy guide: https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/
The pagefile does not necessarily have to be on the drive DCS is installed on. Just change its initial and max sizes, and see if this solves your crash issue.