correct as is Laser should auto-off 4 seconds after estimated impact when auto-lasing

[Nealius]

Per -34, when auto-lasing the laser should automatically stop lasing 4 seconds after estimated impact time. In attached track you can see the laser continues to fire for up to 30 seconds after estimated impact time, only stopping when approaching the pod's masking area. The only way to stop the auto-lase is to cycle the laser switch off and on, which is not listed as a procedure item in the DCS F-16 manual for LGB employment. Other modules utilizing LITENING also have laser auto-off after x-seconds of estimated impact time. 

Looking at up to 2 years of YouTube tutorials, this seems to have been a long-standing issue. Perhaps it was just never added after the auto-lase feature was rolled out?

Auto-lase-time.trk

Edited August 24, 2024 by Nealius

[Lord Vader]

Hey @Nealius

Please send the evidence to @BIGNEWYvia private message and we'll have a look. 

[Nealius]

Evidence PM'ed, though a chat would SMEs would be great as well, since evidence alone provided by users often gets dismissed for arbitrary reasons.

Edited August 26, 2024 by Nealius

[Lord Vader]

Hello @Nealius

We have reviewed the reference you sent to us and thank you for your care.

However, the supplied document does not cover the specific F-16CM Block 50 CCIP variant that we use as reference for our DCS: F-16C.
Our current representation of the laser timing in our simulation is accurate to the depicted tape and needs no further change.

Thanks for understanding.

 

[Nealius]

Which public document for our particular Viper indicates this? I'd like to research why it departs from common logic in other airframes using the same pod in having an auto-off for the laser, which has specific firing time and cooldown time limits to prevent damaging the pod; also why the functionality was removed in the CJ>CM upgrade.

Since it is correct, I request that the manual be updated to include laser switch off in the auto-lase GBU implementation procedure, as it does not accurately reflect actual required procedure in DCS.

Edited August 27, 2024 by Nealius

[Lord Vader]

A new up to date manual is being created for the DCS: F-16C. Please take into account this a complex document for a complex system so it's taking a bit of time to produce. When it is done, it will try to include all the systems logics currently in this module.

Thanks. 

[Hobel]

vor 4 Stunden schrieb Nealius:

Which public document for our particular Viper indicates this? I'd like to research why it departs from common logic in other airframes using the same pod in having an auto-off for the laser, which has specific firing time and cooldown time limits to prevent damaging the pod; also why the functionality was removed in the CJ>CM upgrade.

Since it is correct, I request that the manual be updated to include laser switch off in the auto-lase GBU implementation procedure, as it does not accurately reflect actual required procedure in DCS.

 

For our version, the time was simply increased.

Maybe it also depends on the DTC settings, but basically it is correct in DCS as it is.

[Nealius]

Good to know it's accurate. I would still like to know which public document was used for our avionics so I have a more reliable manual source, given the incomplete nature of the DCS documentation and the invalidity of the old CJ -34 (the only -34 I can find) on hand.

[Hobel]

vor 3 Stunden schrieb Nealius:

Good to know it's accurate. I would still like to know which public document was used for our avionics so I have a more reliable manual source, given the incomplete nature of the DCS documentation and the invalidity of the old CJ -34 (the only -34 I can find) on hand.

In my opinion, XY is not invalid per se, in fact it is very valid.

Our tape is an upgrade, which theoretically means that only new features and upgrades are listed.  

The basic workflow hardly differs in essence 

[Nealius]

Would you happen to know the name of that public document for our tape? 

Edited August 28, 2024 by Nealius

[BIGNEWY]

Hello,

We do not share real-world manuals on our forum, but please rest assured that we are using public sources and will update our own manual accordingly to reflect any changes.

Thank you