Inanity

Having the same issue but also including the laser designator where it states its on "LASE" for the WSO but "ARM" for the pilot on the tpod and vice versa. Regardless if its auto lase or manual.

Produced on DCS version: 2.8.4.38947 Open Beta on map Syria in a multiplayer server. Note that I currently don't have any stores and it's a brand new F/A-18C in the same multiplayer session (no ATFLIR) See the attached image. Reproduce steps. 1. Cold start the F/A-18C on the carrier 2. Fly a sortie with the ATFLIR up in the centre MFD. 3. Crash and respawn 4. During cold start (before the INS alignment) the HSI should show the last captured ATFLIR image from the previous sortie

Any updates on this? I understand if it's not high priority but I wanted to bump that the issue persist on version: DCS 2.7.12.23362 Open Beta (digitalcombatsimulator.com).

The issue I'm having is I can't see the ranging details in the HUD when TCN is activated and boxed in the HSI set to A/A in the Hornet. Example with A/A on: Example with only T/R (note that T/R shows ranging info in the HUD) The above is illustrated on DCS: 2.7.10.18996 Open Beta on a single player mission with a KC135MPRS "TXC" tanker set to 32Y

Mine was specifically when the mig-21b used the guns on a Viggen. Fingers crossed. Hope its resolved!

Ran the entire track on 0x and it didn't crash or freeze DCS for me. Note that the issue is not 100% crash for me. It used to happen 1 out of 10 runs. I'll try to post updates if I come across it again. I think after the Viggen changes maybe it got resolved in the process?

Sorry for the late response. Didn't get notifications. There was no crash .zip since the game stopped responding and I had to stop the process in order to exit. Attached the mission. Air_to_Air.miz

Yes. It was a custom made mission through the mission editor. Only Viggen and Mig-21 in it with no other assets or mods

Reproduced it but no crash.zip file under /Logs. Game didn't crash but it stopped responding and I couldn't get back in and had to force close the client. Attacheddcs.log

I'll post a new ZIP from the Logs folder if I run into this issue again. Thanks

I ran into this issue several times as well. Below is the details: Offline - Mission Editor Viggen (set as player) Mig-21 (set as AI) On Caucasus Version DCS 2.7.1.7029 Open Beta Error causing the crash: DCS: Can't find score constants for GSH_23_HE dcs.log

Just for clarification I've ran into this issue without any mods installed. It seems like the chance of the freeze occurring increases the longer you stay in game. The numerous times it occurred to me was after an hour of orbit before weapon release.

Do you happen to have a dcs.log you can attach? I've had this happen to me on both Nevada and Persian Gulf.

Same crash occurred just now. Details: Persian Gulf GBU-12 first bomb release As stated before every crash the track turns into a mission: CAS_Sultan_P2-20210503-203403.trk dcs.log

Unfortunately no. The track is 59MB which is the reason I made a recording based on the replay. I uploaded it to a google drive since I couldn't attach it here: https://drive.google.com/drive/folders/1xY0XjtbFU9r5BOHyX86BJHPYzAiAK3D4?usp=sharing The case occurs around 10.21:39 in the track. I'm trying to reproduce it as well and hoping to provide a shorter track.

So after a full clean reinstallation of windows and running the latest windows 10 updates the same crash occurred for GBU-12s See attached for windows update status and dcs.log and track. Updated details: Running on Nevada (Multiplayer on dedicated server) No mods dcs.log JTAC_Airport_Nellis-20210430-190850.trk

Ran into this issue where the emergency jettison triggered when I was dropping a GBU-12 in CCRP mode. I realize it will be hard to prove since the linked video indicate that the emergency jettison button is pushed but I can assure you I did not push that button. I've double checked my bindings and I couldn't find any trace that my weapon release button would cause emergency jettison to be triggered. If that would be the case this would occur every time I weapon release. However I do have the emergency button bound on a separate button which is far from accidental triggers especially when I'm already pressing on the weapon release. The reason I think it's a bug is that I've had another friend run into the same exact issue. Details: Running with TrackIR 5 (NoVR) Running Syria On multiplayer dedicated server No mods installed Tacview 1.8.6 VPC MongoosT-50CM2 Grip stick Clean install of DCS 2.7.0.5118 Open Beta Clean windows installation with the latest windows updates Loadout: 9X BRU-33 2xGBU-12 Fuel tank AIM-120C-5 AN/AAQ-28p AIM-120C-5 Fuel tank BRU-33 2xGBU-12 9X If it's not clear in the video my laser code was set to 1788 along with the GBU-12s. DCS: World - Bug report: Weapon release may cause emergency jettison to trigger - YouTube

I'll do a clean installation of Windows 10 and see if I can reproduce the same case. Thanks for the input.

As you can see I'm getting an error on one of the security updates: KB5001330. They seem to be security connected. I've not had any other DCS crashes apart from the ordinance drop from the Hornet and specifically the weapons stated above. More details of the KB5001330 update: https://support.microsoft.com/en-us/topic/april-13-2021-kb5001330-os-builds-19041-928-and-19042-928-cead30cd-f284-4115-a42f-d67fec538490 https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=3dbb1426-3e2c-42ff-980f-1f4456c0d687#Overview PS: Thank you for the warm welcome! I've been a long time lurker though

Reproduced with GBU-12s and MK-82s so far. Details: Game froze when pressing weapon release (ordinance never dropped). DCS stopped responding and crashed Running with TrackIR 5 (Not VR) Happened both on Syria & Persian Gulf Both sessions in multiplayer on a dedicated server No mods running on either server or client Tacview 1.8.6 installed on both server & client (was running at the time) Clean install of DCS 2.7.0.5118 Open Beta Loadout: 9X BRU-33 2xGBU-12 Fuel tank AIM-120C-5 BRU-33 2xMk-82 500lp AN/AAQ-28 Fuel tank BRU-33 2xGBU-12 9X Unable to add a replay track since the crash caused the track to convert into a regular mission file. Can provide a server track if needed but its over two hours long and the bug occurs in the first hour. See attached for system specs and dcs.log when the crash occurred between 2021-04-26 19:26:39.621 - 2021-04-26 19:50:50.686. dcs.log.old DxDiag.txt