Derbroomaster

Bump. This is still happening.

Be aware that this profile's author does not support this profile. Many screens haven't exported for a while and there are no responses to inquiries.

Latest one. Just now. Track radar in the TADS. Within 4km. Lased. Repeated commands to fire ignored.dcs.log PersianGulf_007-20240730-190750.trk

OK, just ran into it again. Multiplayer. Heading to enemy base. George says "target in range" almost right after I tell him which one to engage. No lasing. I give the command to fire with the response "Engaging" each time. Nothing. Log and track files included. PersianGulf_007-20240725-145458.trk dcs.log-20240725-203715.zip

Submitting my own example of this problem, with files. dcs.log PersianGulf_006-20240713-144542.trk

This needs to be in the Bugs section or we need to understand what is keeping it from being there, please.

I first reported this in April and came up with workarounds that no longer work. We should not have to continue to develop a body of workarounds for features that should function.

Is this not a bug?

This was with Limas. Clear view of target. In the TEDAC. No data sent because George would not lase.

Not only this, but I had an instance today where George simply didn't lase the target at all after tracking the target selected from his list of seen targets. It's sitting in his sights and nothing is happening.

As @GeoS72 said, please submit a track file and/or log file for the session you're describing. Hopefully something will be done if enough people supply these files.

This no longer works. Nor should it really have to be something any of us must do to get this to work. I just came out of a very frustrating session where George lased an SA-8 repeatedly from range, then finally said we were in range. Gave consent to fire repeatedly. Nothing. I have included log and track files. This really needs to be addressed, please. @BIGNEWY @Flappie PersianGulf_006-20240713-144542.trk dcs.log

UPDATE Just over the past weekend I had to disconnect one of my SSDs because of constant boot errors after coming out of POST. Additionally, the GPU was plugged into the wrong power slot in the PSU. After disconnecting the drive, plugging the graphics card into the correct PSU slot, and deleting and reinstalling DCS, I have had no problems in the editor.

Just to be clear, are you saying to have FF enabled in the Special tab under OH-58D, and additionally ensure Force Trim is NOT enabled in the sim?

I stand corrected. This issue remains. I have cleared the shader cache, formatted the DCS drive and done a clean reinstall. No mods. Had one day of editing for about 2 hours with no crashing. Since that one time, I have not been able to have an editing session without crashing. dcs.log-20240510-182741.zip dcs.log-20240510-185404.zip dcs.log-20240513-205642.zip

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.