Maverick806 Posted January 21 Posted January 21 In previous versions of DCS, Holding TMS UP while in ACM BORE mode would temporarily turn off the radar and NO RAD would be displayed on the HUD. After the Dec 24th patch, I noticed that NO RAD was no longer displayed when holding TMS UP. Steps to Test: Enter Dogfight Override Mode Press TMS FWD to enter BORE mode Press and Hold TMS FWD F16_ACM_BORE.trk 2 9800X3D, 64GB DDR5, RTX 3080 Valve Index, RS FSSB R3 Ultra, TM Viper TQS, TM TPR Pedals
Delta134 Posted January 21 Posted January 21 TMS Up Long slaves the radar to the HMCS when equipped. NO RAD is not supposed to show up. This was fixed in the lates update and included in the changelog: Quote Fixed: HMCS Boresight locking - No rad but locking anyway. 1
Maverick806 Posted January 21 Author Posted January 21 The issue that fix is referencing is that the radar could previously lock targets when it was showing as off, including while in the ground, not that it could be turned off. Also, this behavior changed before the Jan 20th patch 9800X3D, 64GB DDR5, RTX 3080 Valve Index, RS FSSB R3 Ultra, TM Viper TQS, TM TPR Pedals
Delta134 Posted January 21 Posted January 21 Okay, let me phrase it this way. TMS Up should not command NO RAD in any way. TMS Aft has that function. 2
darkman222 Posted January 21 Posted January 21 (edited) 17 minutes ago, _Delta13_ said: in any way. Where is your source for that behavior? The JHMCS is still locking the first target it sees. It is simply unusable if there are multiple targets flying side by side and you want to lock the target which is the furthest away to one side. It needs to go to NO RAD first while TMS UP is held, to slew the radar, then release TMS UP, radar activates after the JHMCS slaved the radar antenna to the desired target. Besides, NO RAD seems to be stuck sometimes, not being able to activate even pressing TMS UP multiple times. Edited January 21 by darkman222 3
Delta134 Posted January 21 Posted January 21 It's in the -34. I am not sure I can share it due to rule 1.16. Additionally, ED marked the thread correct as is now. If you have conflicting documentation I suggest you send it to a CM 1
Maverick806 Posted January 22 Author Posted January 22 Interesting, there was a discussion about this a while back when this was first implemented and nobody seemed to think there was an issue with the radar only attempting to lock once TMS up was released. 9800X3D, 64GB DDR5, RTX 3080 Valve Index, RS FSSB R3 Ultra, TM Viper TQS, TM TPR Pedals
Delta134 Posted January 22 Posted January 22 (edited) Ah I see, you are correct. The HMCS specific chapter indeed suggest the radar is only commanded to radiate when TMS-forward is released. What might cause the confusion is that the ACM specific chapter does not mention this behaviour. After testing I am also experiencing the stuck NO RAD in BORE Slave after an initial lock. So there are in fact two problems: Holding TMS Up in ACM BORE SLAVE doesn't command the radar to NO RAD After an initial acquisition then debugging and trying to acquire lock through ACM BORE SLAVE again, the radar remains stuck in 'NO RAD' and it doesn't acquire a lock @BIGNEWY @Lord Vader could you please take a look at this? The workaround to getting Bore Slave to work again is by pressing TMS Aft several times until in 10x60 NO RAD, then going back to bore by pressing TMS Up ACM_BORE_SLAVE.trk Edited January 22 by _Delta13_ 2 1
Recommended Posts