Search the Community

I was tring to aquire enemy position using an offset from a known point (my WPT2), i knew that enemy was at 109 for 1.6 nm from it. then I've created the offset and noticed that it was pretty away from enemies because it was been created at the same elevation of father waypoint, so i tried to adjust offset elevation, and it simply don't work. I can insert the value but the offset position does not change. Also, waypoint elevation seems to be bugged too, when i tried to change it inserting a value of 170 feet, it have been changed in something like 56 after pressing ENTER. Please see attached trk elevation.trk

Hi everyone, Currently the F-16's air-to-ground radar has an overexaggerated radial footprint; the radar is able to display everything from basically ownship out to the extremes of the instrumented range and is able to do this regardless of antenna elevation angle (even with the antenna 60° above the horizon) or altitude. Generally speaking, if the aircraft's altitude increases and the antenna elevation angle below the horizon increases, the smaller the footprint that the radar covers. They say a picture speaks a thousand words so here's a diagram, that should more clearly illustrate what I mean: In the F-16CM, the AG radar makes a 1 bar scan, with a bar corresponding to ~5° in elevation (determined through simple trig in the air modes). At an altitude of 20,000 ft, with a 15° look-down angle should give me a patch between ~10 and ~15 nmi. Of course, the radar doesn't just have a mainlobe, it also has sidelobes, so the patch shouldn't abruptly terminate at those values but the brightness will gradually fall off to 0 (exactly how large it should be in total and how much it falls off by will depend on the radiation pattern of the antenna). This can kinda be seen in this video (only here the elevation angle below the horizon is very small and the altitude is ~14,500 ft), you can see that the gain reduces gradually around ~27 nmi and there are no returns closer than 25 nmi (corresponding to an elevation coverage of about 3.5° - well within the range of a 1 bar scan). However, in DCS, the footprint is currently unaffected by both altitude and elevation, leading to it being drastically overexagerrated (and even including areas the radar shouldn't be able to illuminate with its mainlobe). If I'm flying at 20,000 ft I can see everything from 0 - 80 nmi with everything at constant brightness (obviously brightness of specific objects will depend on their RCS), regardless of the elevation angle. In order to do this the radar would have to be able to scan an elevation angle of ~88°, way beyond what the radar should be able to achieve with a 1 bar scan. Incidentally at 20,000 ft it shouldn't even be possible to see returns (apart from sidelobe returns, which should be more dim) inside of ~6 nmi, as the radar's elevation limits are ±60°. Another related issue (not sure if this should be in a different thread) is that the radar doesn't seem to respect the elevation setting that well - if you dial all the gain all the way up and tilt the antenna elevation above the horizon to it's maximum, the image appears like it would normally if I turned the gain down. Go all the way to 60° down and the whole image goes more or less dark, despite the fact that the radar should be illuminating a section with its mainlobe. Essentially the antenna levation setting seems to behave as if it were a 2nd gain setting for the entire image. APG-68_AG_coverage.trk

Hi, since last update it is quite difficult to set points elevation. Did some test with Target Points, can't create a tgtpoint and set it's elevation (EHSD - >DATA ->ODU (TGTPS) -> insert coordinates - > ODU (ELEV) ->insert elevation = elevation not set The only workaround I found is to edit target point after creation to set elevation And after elevation has been set there are other bugs. 1 . In ehsd elevation is shown in meters (not in feet as should be) 2. If tpod Is slaved to tgtpoint it seems to not to get the correct elevation Waypoints, Waypoints-Offsets and Markpoints has similar problems too. Hope this will be fixed soon 'cause it really compromises harrier's effectiveness elevation.trk

Very often when I'm cruising at 30,000ft, some bandits show up at 5000ft or so, say within 40 miles on datalink. Unfortunately, Jester won't look at the datalink hostile HAFU marker, and adjust the radar elevation accordingly. He just sits there scanning at 30,000ft. Would it be possible for Jester to do some form of radar elevation search, perhaps prioritising on hostile datalink targets? It could save the effort to manually tell him to adjust his elevation.

We need it pls Pretty much every other DCS module i use supports using axis to change the radar elevation I got so used to having radar elevation on an absolute axis, it's hard for me to use the radar Please and thank you :D