maxTRX Posted December 15, 2021 Posted December 15, 2021 That's not as intended, is it? (clip starts at 2:04)
Frederf Posted December 16, 2021 Posted December 16, 2021 It's supposed to lase for a little while after the predicted time of impact (~4 sec) to ensure it actually lases throughout the impact which could potentially be longer than predicted. If the moving target was causing the impact to happen sooner than predicted the laser would continue to run for that 4 seconds plus the difference between predicted and actual. Does the laser run forever after the 0:00 timer?
maxTRX Posted December 16, 2021 Author Posted December 16, 2021 25 minutes ago, Frederf said: It's supposed to lase for a little while after the predicted time of impact (~4 sec) to ensure it actually lases throughout the impact which could potentially be longer than predicted. If the moving target was causing the impact to happen sooner than predicted the laser would continue to run for that 4 seconds plus the difference between predicted and actual. Does the laser run forever after the 0:00 timer? Looked like the time required for lasing was roughly doubled. Started around 118 sec. At impact, the counter was around 60 and continued. The 'LTD/R' was blinking as long as it was LOS but the counter continued outside of the Tpod limits. If I turned back within LOS, the 'LTD/R' started blinking again until '0'. Then the LTD/R switched off.
ED Team BIGNEWY Posted December 16, 2021 ED Team Posted December 16, 2021 Hi, checked with the team, the GBU-24 has an auto lase of 120 seconds regardless of TTI. This is correct as is, if you have information otherwise please PM me. thank you 1 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
maxTRX Posted December 16, 2021 Author Posted December 16, 2021 2 hours ago, BIGNEWY said: Hi, checked with the team, the GBU-24 has an auto lase of 120 seconds regardless of TTI. This is correct as is, if you have information otherwise please PM me. thank you I sort of suspected that the timer might be running some sort of auto cycle. What got me confused was 'LTD/R' blinking, from the time of release to '0' on the counter. I thought the blinking indicates that the laser was firing as long as the pod wasn't masked. Seemed a bit long but... it does the job. It's different from the way it works with GBU10, 12. Well, if that's intentional... I'm fine with that. 1
Frederf Posted December 16, 2021 Posted December 16, 2021 Paveway III is a lot smarter than Paveway II. That would make predicting flight time harder. The timer could be the unguided ballistic prediction. Flashing L is definitely showing active laser.
Zodiacc Posted April 17, 2022 Posted April 17, 2022 It doesnt matter if I box the trigger or not.After the release of the bomb laser shoots immediately and it shows time-to-lase instead of TTI and it continues to lase the target after impact.Only way to turn-off the laser is switching off the laser arm switch.
Tholozor Posted April 17, 2022 Posted April 17, 2022 REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
ED Team BIGNEWY Posted April 17, 2022 ED Team Posted April 17, 2022 post merged. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Recommended Posts