fixed TGP Laser Arm >> Crash

[ACEL]

Evening!

In multi player (Afghanistan) once TGP (both ATFLIR and Litening) active, Laser > ARM and DCS crashes.

Anyone else with the same issue?

[Harker]

Not having this problem here. Are you running any mods? There were some updates to the TGP masking logic and masking indicators on the DDI and HUD (still WIP).

[MarcT-NL]

Yeah, I had this too today. I don't do mods. I did a cleanup and repair.

I was on a MP-server where they installed the dynamic spawning. DCS crashed 2 times before I could get airborne.

When I eventually got airborne it crashed immediately after I armed the laser (I only use ATFLIR). Before I armed the laser, I set the code to 1555, which I always do.

[streamcap]

I had the same issue tonight using the Hornet, made several attempts to lase targets while armed with LMAV and GBU-12, got CTD several times in sequence. In the first track, I could fire a HARM at an SA-2 tracking radar with no issue.

I have included the server track, as well as two of my client tracks when the crashes happened.

The crashes were also reported using the reporting tool, for reference the reports were made today at approx. 21:43 and 21:57 CE(S)T, respectively.

server-20240712-212708.trk tpod ctd test-20240712-212906.trk tpod ctd test-20240712-214548.trk

As an aside, we had no issue using the laser on both an OH-58 and an AH-64 to guide munitions in, either for myself or by buddy lasing.

Edited July 12, 2024 by streamcap
Added aircraft type and notice regarding both OH-58 and AH-64 working as intended

[streamcap]

I have also tried to use various types of LGBs on terrain elements (bridges, mostly) on the Afghanistan map and that seems to work just fine - but when targeting an actual unit I get "CTD'd".

[streamcap]

One more piece of information - the bug only seems to show up when on multiplayer servers. I can't recreate it in single player missions.

[Pkdos]

Same issue here, LTD/R on and CTD

[rob10]

Had the same on MP server with highly scripted mission (so no track file).  Dropped 5 GBU-12 no problem, then crash as soon as I tried to arm laser.  Had just fired a HARM prior to arming (it was still in flight), in case that is a common factor.  GMT locked and tracking with ATFLIR.  I had rearmed on carrier prior to the crash.  This was on Sinai map.

Also the first 4 were on static objects, then 1 on a moving target after rearm then got shot down.  1st spawn was from a dynamic spawn slot.  2nd was from standard slot on carrier and that's when it crashed on arming laser.

Edited July 13, 2024 by rob10

[Gizmata]

Same issue on Multi.  As soon as I clicked the arm switch the game hard crashed multiple times (was in the air, master arm, A2G, FLIR page active (probably SOI).  I also saw a weird issue using old saved loadouts, so I created a new load from "empty" and saved that, but it still crashed the game when I armed the laser.  (the other oddity was MK83/84 were not giving MFUS options, but showing EFUS in the stores page when using an old saved loadout, but worked fine when built from scratch in the rearm menu).

 

add:  I use a unique code, not 1688, and didn't get to change it in the FLIR page before the crash.

Edited July 13, 2024 by Gizmata

[webweaver40]

Same problem in Hornet , happens after designating a target and turning on laser, both lightning and atflir

[Q3ark]

Same issue here, arm laser on ATFLIR, immediate crash. 

[Archer.xd]

For crashes its better if you guys add logs. Like Harker, I tried this myself maybe 30 times and havent experienced a CTD. Logs can indicate whats wrong.

[rob10]

48 minutes ago, Archer.xd said:

For crashes its better if you guys add logs. Like Harker, I tried this myself maybe 30 times and havent experienced a CTD. Logs can indicate whats wrong.

I generally have so few crashes that I never even thought of that.  Thanks for the prompt.  Here's my crash log from last night.

It's not a consistent one so could be tough to track down.

dcs.log-20240713-011144.zip

[Q3ark]

I’ll post a track next time I’m on DCS, so far it’s 100% repeatable 

[Knugge]

I have no track, but I and one more player I play with had this CTD when pressing LTD/R.
Some testing indicate that it only happens when equipping the LIGHTING II pod on center position (nr 5). If it is on left position (nr4) it works fine. 

[Gizmata]

2 hours ago, Knugge said:

I have no track, but I and one more player I play with had this CTD when pressing LTD/R.
Some testing indicate that it only happens when equipping the LIGHTING II pod on center position (nr 5). If it is on left position (nr4) it works fine. 

My crash was with the LIGHTING pod on station 4 each time, my wingman had it on station 5, we both had the CTD when switching on the LTD/R.  His second crash he believe he tried to VVSLV the TGP when it CTD.

[falconzx]

In my squadron many pilots reported this crash related to the laser arm, they experienced it with ATFLIR only, expecially if starting cold from an airfield and mounting atflir via rearming.
But they still not have exact steps to reproduce, it's like happening 50% of times.

[Saruman]

+1 happened to me too

[Bones1775]

has anyone experienced this in an air start jet. all my LTD/R CTD have been cold starts.

[webweaver40]

Haven't tried with air start, but the bug is definitely still there with Hot start.

[papabless]

+1

[StandingCow]

Mine didn't crash on the laser arm but rather when I dropped my GBU12. 

dcs.log-20240714-045149.zip

[MemphisBelle]

On 7/13/2024 at 12:08 AM, streamcap said:

One more piece of information - the bug only seems to show up when on multiplayer servers. I can't recreate it in single player missions.

negative, it also showed up for me on a SP Training Mission. I´ve used Mods. On a naked Vanilla DCS Test Mission (1 Airborne Hornet armed with LBG-12, ATFLIR, Maverick F, GBU V2 1000lp)....no crash

[Saruman]

No mods and I have the issue. It does not always happen, it's totally randomic in single player and multiplayer

Inviato dal mio 23090RA98G utilizzando Tapatalk

[rob10]

It would be reaaalllllyyy helpful if more people would post their crash logs.  This is an inconsistent issue (for most people) so tracking it down is going to challenging since it's not easily recreatable (and doesn't seem to have a common cause yet).