OpticFlow Posted February 27, 2021 Posted February 27, 2021 I couldn't find info in the manual what the units on the horizontal scale in the radar scope mean, but they look pretty close to KM. However they are slightly off, is that bug or the scale means something else? Here is a screenshot to illustrate what I mean: Target is locked, distance to target from the in-game labels is 8.7 km, distance mark in the scope is slightly more than 10, say 10.5 units.
rossmum Posted February 28, 2021 Posted February 28, 2021 (edited) Once you lock the target it transitions from B-scope (which those markings are for, they are indeed range markings along the Y axis and are indeed kilometres) to C-scope (?) with ranging data - it's like the Hornet's AZ/EL page. Putting the target directly in that little crosshair like you've done means it should be smack bang in the middle of the pipper. From memory, the X axis markings are kilometres offset at approx. 15km range - but I could be wrong, I need to double check. They're not degrees because the radar scan zone is about +/-30 in azimuth. In search mode, with the target not locked, you should see that contact just below the '10' marker. Edited February 28, 2021 by rossmum bad at scope terminology 1 1
Frederf Posted February 28, 2021 Posted February 28, 2021 From Czech, I hesitate to say manual, for RP-22SMA the marks are said: 2. Aktuální vzdálenost k cíli. "2. Current distance to the destination." It seems most likely that the spread of the birdie marks which can be chosen in scale by the engineer independently would chose to make them equal to the actual range unless there was some benefit otherwise. Also I believe the 0 range position is not the center of the display or the middle of the center birdie but the vertical line labeled with "0" which is tangent to the circle in the center. DCS is not doing this, but has the birdies completely collapse at 0 range. Instead zero range picture should look like: /\(__/\__)/\ with ( representing the aiming circle curve. Notice that all diagrams which show the autotracking mode the minimum line length of the central feature is always wider than the aiming circle in the middle. The "0" is showing zero range vertically in scanning mode as well as zero range horizontally in the tracking mode. The shown target is (I think) at ~7.5km range. The light pink line represents the minimum firing range down to zero range. The green line segment is not part of the range scale as it is less than 0 range. The purple vertical lines are all 34 pixels apart. I believe that the difference between measuring from the "0" mark to "10" mark or center to "10" mark could explain confusion as to what the scale means. 3
OpticFlow Posted March 2, 2021 Author Posted March 2, 2021 Thanks for the info! Seems like the range scale of the locked target is in KM, which means there is a bug in the current implementation because the indicated range is incorrect (around 20% more in my example).
Fri13 Posted March 3, 2021 Posted March 3, 2021 Good thread. It would make sense to have the range to the locked target, instead just having to wait a triangles (in the above image they are yellow big pointy triangles, while in game they are just bars?) to reach the end of the line and then get the launch authorization. i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
Frederf Posted March 3, 2021 Posted March 3, 2021 They are a spike like on an occilloscope because that's essentially what it is. It will look sort of like line and sort of like triangle. There are pictures of the real scope around.
Recommended Posts