Derbroomaster

Ah, I see. Unfortunatlely, the PC in question is used for editing only, and has no controllers to do what you're saying.

No, this is a new map created from another one, just adjusting time of day and unit composition, etc.

No-go. Waited about 5 minutes or more before starting into the editor. Crashed pretty soon after I opened a map. dcs.log-20240417-193628.zip

I'll give it a go and report back. Thanks.

No mods installed (that I'm aware of). Every single time I've opened a mission in the ME, it's just been a matter of time when the program will crash. Log files attached. PC In Question: OS Name Microsoft Windows 10 Home System Type x64-based PC Processor AMD Ryzen 5 7600X 6-Core Processor, 4701 Mhz, 6 Core(s), 12 Logical Processor(s) Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.1 GB Available Physical Memory 24.9 GB Total Virtual Memory 67.6 GB Available Virtual Memory 58.6 GB Page File Space 36.5 GB ZOTAC RTX 2070 Super 8GB VRAM DCS installed on a 1TB Samsung 970 nVME drive. dcs.log-20240415-132038.zip dcs.log-20240417-124203.zip

So far, what works for me to help avoid this situation is to ensure I don't use Ground Override when starting up in order to pre-set things for me as the pilot. Once in flight, if I still encounter AI not firing even with clear line of sight, no YAW or Ballistic limits, I do one or more of the following: *Cycle Master Arm off, then on. *If "Missile Type?" shows in the TADS, hop in the CPG seat and cycle Missile Select (Salvo vs RF, iirc), then come back to the Pilot's Seat. *Have George AI cease fire, then have him WAS the Hellfires again. I've been able to wake him up using one of these. Annoying, but it works.

Was there ever an answer for this? I run into this a lot myself, including just last night when flying with my squadron. It's beyond annoying.

Does this happen when you start on something moving, e.g. a carrier or other kind of ship? My buddy and I have a very similar problem when trying to start a multicrew mission from a ship. The CPG is instantly greeted with "Rotor RPM low," the ENG screen shows the engines in distress, and the TEDAC is not powered on. When the Pilot moves his collective or reduces then increases throttle power, the ENG screen returns to normal, and the TEDAC powers up after about five seconds.

Yes, I've been using it since I posted about it. Works great.

Has anyone here seen and/or used this profile? It was just recently uploaded in the User Files section. https://www.digitalcombatsimulator.com/en/files/3335588/ If you have, please let me know your thoughts and whether it was difficult to employ in Helios.

Followed your instructions and tested it three times. It appears to be the solution. Thanks very much for your assistance.

Bump. Still happening. No mods. Crashed this morning with only AH-64D module installed.

Mods out, page file at 32GB. If anything, it crashes sooner.

Correct, I took the mod folders out. I will double the page file to see if that works. I'm gathering that mods in general are having a tough time since 2.9 came around, but don't know any specifics.

Just tried without any aircraft or unit mods. Same result.

dcs.log-20240113-150340.zip Log attached. Game crashes every time I'm in the editor after 10-15 minutes or so. I've adjusted the page file from auto to 16GB on the drive where DCS is installed. Driver updated.

You appear to have wanted to clarify, which I appreciate. Thank you.

Indeed. I was attempting to see if @CallsignFrosty would care to provide more mature feedback.

I don't understand the point of posting this link. Can you elaborate?

Pretty sure he means this: https://www.tenforums.com/tutorials/121191-clear-environment-data-windows-mixed-reality-windows-10-a.html

For anyone running a HP Reverb G2, ensure you follow the directions in this link: After doing these steps, I have no more issues, and everything looks great. I don't know why the thread in the link isn't pinned, but it sure ought to be.

I just followed the directions above, and so far so good with my G2. Thanks very much for making such a cogent description of what to do and where to find and employ the necessary resources to do it. Also: How the heck is this not pinned?

No terrain mod. It's never in the same place when, regardless of whether I'm running in ST or MT. Just happens quicker in MT.

Playing in Caucasus on Multiplayer map. Log and DXDiag files attached, as well as VR settings. I'm consistently experiencing crashes in ST after the latest update. I've pretty much given up on MT as that is a sure crash after only minutes of game play. DxDiag0314231403.txt dcs.log-20230314-195822.zip I neglected to add system specs & VR headset: Processor AMD Ryzen 7 5800X 8-Core Processor 3.80 GHz Installed RAM Corsair Vengeance 32.0 GB DDR4 3200 (4 x Device ID D8749A90-EBC2-49B6-8D28-8308E9ABFEA9 Product ID 00330-80000-00000-AA577 System type 64-bit operating system, x64-based processor nVidia RTX4090 24GB RAM 1TB Samsung 980 NVmA 2TB HDD 1TB SSD (System) MoBo MSI X-570 A Pro PSU: Corsair RM1000X VR: HP Reverb G2 v2

Fixed. Double-mapping between Axis and non-Axis controls.