Biga42 Posted October 20, 2020 Posted October 20, 2020 If you change the lase code to 1588 when pickle GBU-12 you got Auto Lase Fail message. Even if you change to latched on it stops lasing. dont know yet if occurs only with this lase code.
Ziptie Posted October 21, 2020 Posted October 21, 2020 If you change the lase code to 1588 when pickle GBU-12 you got Auto Lase Fail message. Even if you change to latched on it stops lasing. dont know yet if occurs only with this lase code. Changed both laser codes, in DSMS and TGP? I assisted a couple pilots today with training in the A10CII and changed laser codes with successful employment of laser guided munitions, but I did not change to that specific laser code... Cheers, Ziptie i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria
Biga42 Posted October 21, 2020 Author Posted October 21, 2020 youre right...tried today and got no fail...dont know what happened though....
ED Team BIGNEWY Posted October 21, 2020 ED Team Posted October 21, 2020 No problem, thanks for letting us know. If it happens again please attach a track replay, I have not been able to reproduce yet. thank you 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
Ziptie Posted October 21, 2020 Posted October 21, 2020 youre right...tried today and got no fail...dont know what happened though.... If you had auto lase enabled in the weapon profile and also had a lase time input (left side of specific weapon profile sub page), it could state auto lase fail if you were out of parameters to facilitate the desired lase time. for example: if you were at 5,000 feet ASL and had 10 seconds input for desired lase time - it would give you that message, but the laser can still fire - just not for the full 10 second time input. Cheers, Ziptie i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria
Biga42 Posted October 21, 2020 Author Posted October 21, 2020 Thanks Ziptie, I really know this.....but if happens again I will post a trk file. Sorry to take your time guys!
Ziptie Posted October 23, 2020 Posted October 23, 2020 Thanks Ziptie, I really know this.....but if happens again I will post a trk file. Sorry to take your time guys! No worries - just as a heads up - I tested your scenario, using 1588 (to deconflict with another laser operating in the area on 1688) and had zero issues (no autolase fail message) with the GBU-12. Good to see you didn't have any issue your last attempt either. Cheers, Ziptie i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria
Recommended Posts