AvroLanc Posted January 26 Share Posted January 26 A bug since the FCR patch, it now seems that the CPG's NAV range (NX.X etc) is not updating when slaving to a TSD selected ACQ source. The problem only occurs after using a LASER range with that ACQ source. I.e. You select, either by CAQ or COORD page, a Point ACQ source and select 'Slave'. The NAV range now correctly says NX.X. If you now use the laser to get a laser range the range readout displays the laser range, however reselecting SLAVE should slave the TADS back to the point and reselect your NX.X nav range......which it does not.......the laser range remains. You can get the Nav range back by re-selecting the ACQ point, or selecting a different one etc. But the way it worked in the past was slaving reset to the NAV range. Maybe the changes introduced with the FCR introduced a bug in the logic. See track. Thanks. Nav Range Slaving.trk 1 Link to comment Share on other sites More sharing options...
ED Team Raptor9 Posted January 29 ED Team Share Posted January 29 Reproduced and reported. Thanks. Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head Link to comment Share on other sites More sharing options...
AvroLanc Posted January 29 Author Share Posted January 29 3 hours ago, Raptor9 said: Reproduced and reported. Thanks. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts