Swift. Posted October 9, 2020 Posted October 9, 2020 I'm not sure if this is an error, but its certainly different to how it was before: When you WPDSG then slew the pod away and redesignate a new TGT. The FLIR will command itself to snowplough upon changing to a new waypoint, even if the new TGT isn't the WP designation. This happens in all 3 stabilisation modes. https://youtu.be/_I2ty7AbUtgFLIRWPstepbug.trk 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2
Santi871 Posted October 10, 2020 Posted October 10, 2020 It's not related to the FLIR. Changing waypoints undesignates, it's always been like that. The only thing that's changed is that FLIR designations correctly make it enter TGT steering mode.
Swift. Posted October 10, 2020 Author Posted October 10, 2020 (edited) So there is no way to enter a new WP without losing the current pod LOS? I could have sworn it used to be possible. Edit: To clarify, even when not doing a WPDSG, changing the WP still drops the pods LOS. Edited October 10, 2020 by Swiftwin9s 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2
Santi871 Posted October 10, 2020 Posted October 10, 2020 Yes, because previously it would only enter TGT steering mode when pressing WPDSG and not when designating via other methods, which was wrong. Changing the waypoint causes undesignation. The only reason it didn't before with designations other than WPDSG is what I mentioned above.
Recommended Posts