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.