Radar cursor in CRM SAM mode
-
Hi,
When operating the radar in CRM mode and designating a contact by TMS up, my radar cursor is stuck to that target. As far as I understand from the Dash-34 manual chapter 1.4.4.3.3 (Target Acquisition and Management), one should be able to still move the cursor around and designate a second target by TMS up, upon which the DT (dual target) SAM submode becomes active.
Can anyone guide me to what might be going wrong for me? Why is my radar cursor stuck on the first designated contact? With the first contact designated, the radar is definitely in SAM mode and scanning the ±25deg space around it. I just can’t move the cursor anymore.
Cheers
-
Hi,
Dual Target SAM mode explanation can be found in this thread. I too found some issues getting it to work as you can see by my post. The short video is very interesting.
Regards
Dram. -
Hi,
I have the same problem too. Well it is not about not working. It’s just that it is no longer that user friendly & convenient compared to 4.34
When in 4.34, once i TMS up the first target, i can easily slew my cursor to the second target even when the FCR range is bumped to 80nm.
Now in 4.35, once i TMS up the first target, the cursor is stuck on first target even if i slew my radar cursor. I need to keep holding my cursor slew for 2 sec + more in order to move the cursor away from the first target.
If cursor is moved anywhere near the first target, it would very annoyingly get “attracted & stuck” onto the first target again too.
The efficiency of DT SAM in 4.35 just becomes poorer compared to 4.34, which forces me to use TWS mostly now.
And very strangely this DT SAM in 4.35 would only work when the radar scale is within 40nm range. If FCR is at 80nm scale, this DT SAM submode does not work at all - cursor is just absolutely stuck on first target.In my opinion and personal feeling, i think this might be a bug because in 4.34 this was never an issue.
But not sure what the opinion is from the development team & other players.
Still prefer the much more user friendly DT SAM submode in 4.34 -
From memory this is an issue of cursor input deflection and possibly screen resolution and frame rate.
Ensure that cursor speed is at least 100% in the Config.exe/falcon_bms.cfg. Ensure that your cursor controller can generate 100% axis deflection in all directions reliably. Possibly test with button (non-axis) cursor input to see if binary input can override the snap attraction.
-
Hi Frederf
Thanks for the feedback.
My cursor speed is confirmed 100% and cursor controller is also working properly.
I do a few tests again and can still confirm the same result.
When the radar scale is bumped to 80nm, the cursor would just absolutely stick with the first target as if there’s no such thing as DT SAM mode.
Only when the contact is within 40nm and that radar scale is bumped to 40nm, cursor would then be able to slewed away from the first bugged target if cursor slew is held for more than 2 secs.
And this is regardless of using throttle cursor slew or key board (non-axis input)
This situation did not exist in 4.34 but only became a problem with 4.35The difference is very obvious between 4.34 vs 4.35
-
philip40912, sometimes your method of holding cursor slew for a few seconds seems to help. Othertimes, the cursor stays glued to the first target. I also checked that the axis reaches full deflection and that cursor speed is at least 100% in config.exe, as per Frederf’s suggestion. Nothing seemed to have helped. Can anyone confirm that this “snapping” is working as intended? Especially since in 4.34 it wasn’t a problem. Couldn’t find anything posted to the BMS bug list and not a lot of helpful discussions on the forums.
Cheers
-
philip40912, sometimes your method of holding cursor slew for a few seconds seems to help. Othertimes, the cursor stays glued to the first target. I also checked that the axis reaches full deflection and that cursor speed is at least 100% in config.exe, as per Frederf’s suggestion. Nothing seemed to have helped. Can anyone confirm that this “snapping” is working as intended? Especially since in 4.34 it wasn’t a problem. Couldn’t find anything posted to the BMS bug list and not a lot of helpful discussions on the forums.
Cheers
When radar range is at 80nm scale, the cursor stays absolutely glued.
Only when radar range is below 40nm scale, holding cursor slew for a few secs would then start the DT SAM submode.
In my opinion i think this should be a bug. -
I’m able to get the cursors unstuck from an IL-76 using the 80nm and 160nm range scale. It takes slightly less time at the 40nm scale.
-
I remember it getting stuck for me too. IIRC, I noticed that if I waited for the antenna azimuth marker at the bottom of the scope to get lined up with the target, then I was able to move the cursor at that moment only.
-
-
This post is deleted!