Derbroomaster

I guess so. Haven't had a crash since doing this, but it seems like I should not have had to do anything.

Just did some rudimentary editing after updating the driver with an update that just recently appeared in my Geforce app. Also changed some graphics settings that didn't need to be high and reduced the initial environment by half.

dcs.log Forgot about the folder switcheroo. Here's the log file from two days ago.

Crashed while doing this. Didn't even generate a log file lol.

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.