Default774 Posted November 2, 2022 Posted November 2, 2022 (edited) As shown in the 16_rws_expected track, the expected behaviour of the cursor after commanding a SAM lock on a target is that the cursor snaps to target, allowing you to command an STT lock on your target without having to reposition your cursor over the target. The radar screen when in SAM will automatically reduce radar scale when the locked target comes within a certain range, however, this transition of radar scale causes problems with the aforementioned behaviour of the cursor locking to the locked target. When a SAM lock is commanded on a target that is near or within the range where the radar scale will automatically scale down, the cursor will either not lock to the target at all, or lag behind. This lag means you can no longer TMS UP to command an STT lock on target without repositioning the cursor. In some circumstances, especially in closer ranges, the cursor might not lock onto the target on the radar cursor at all. This behaviour gets more apparent the closer the target is. 16_rws_expected.trk 16_rws_snap_1.trk 16_rws_snap_2.trk Edited November 2, 2022 by Minimalist 1 1
ED Team BIGNEWY Posted November 2, 2022 ED Team Posted November 2, 2022 Hi, do you have any public reference for this behaviour? if so please PM me 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
Default774 Posted November 2, 2022 Author Posted November 2, 2022 19 minutes ago, BIGNEWY said: Hi, do you have any public reference for this behaviour? if so please PM me thank you To be honest I am not sure why this is needed. The radar cursor soft locking onto the target already happens in the OB build (as is shown in the expected trk) so I assume the radar cursor doing this is intentional, the problem lies in that it doesn't work properly when you lock the target at certain ranges/scale settings. If you want evidence that the radar cursor is actually not supposed to lag behind the target or not track it at all under these specific conditions, then it unfortunately ends here as I don't have any evidence to suggest that is the case. I haven't been able to find any reference that the cursor is supposed to follow the bugged target in the first place (MLU manuals do not mention this behaviour occurring at all), so that might be worth a look at if the cursor following the target isn't actually intentional.
ED Team BIGNEWY Posted November 2, 2022 ED Team Posted November 2, 2022 I will ask the team to be sure 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
Geraki Posted November 3, 2022 Posted November 3, 2022 This is the AUTO SAM function of bugged target in FCR When we TMS forward to bug a radar target the cursor remain "stack "with bugged target until the pilot can slew the cursor in order for example to bug another target in FCR and pink pong the bugged target in RWS and TWS mode , the cursor in bug target mode follow the bugged target until pilot slew it, if he bug another target (soft lock) the cursor follow the new bugged target. If the pilot want to slew the cursor the cursor "unstack" and move in FCR area. 2
Recommended Posts