NineLine

Thanks I will check this as well, with new fog coming visibility tuning will need to be done.

We believe this is correct based on available, public references. If you have contrary, public evidence, please message me with it.

I'm not sure what you mean, you can boresight on a building.

Thats interesting if true, that shouldnt be. I will check this mission shortly. Thanks!

I think its more of a mission issue, but I am looking into it. Thanks!

I will need a track without any mods required. If you can recreate it on the Caucasus map, even better. Thanks.

Can you share you mission or a track and I will take a look.

DCS: AH-64D | Radar Map Mode In this DCS: AH-64D video, we’re back to the Fire Control Radar, or FCR. We’re going to go over the Radar Map, or RMAP, mode. Like the FCR GTM mode we discussed earlier, we can still use the FCR to detect and classify ground targets and low-flying aircraft, but we’ll also be able to generate a radar-image of the terrain to provide target reference and situational awareness. Let’s get started. I’m at a 60-foot hover and we’ll first get the FCR up and running by bringing up FCR and then the Utility page. From here we’ll unpin the Mast Mounted Assembly, MMA, override the BIT to save some time, and exit the utility page. We’ll now make the FCR our sight. By default, we’re in the familiar GTM format, but let’s switch to the RMAP format by adjusting our controls on the CP/G left handgrip. You can also set on the Pilot’s collective mission grip. Set LHG FCR Mode Switch – RMAP (Radar Map) to the binding of your choice. We can now see the FCR format on the left display. Let’s discuss it. The main display, or FCR Footprint, is in a traditional B-Scope format of azimuth and range, just like most air-to-air radars you’ll find in DCS. Note that when scanning, the scanning azimuth will stay stabilized along that azimuth, regardless of aircraft maneuvering. With the left and right arrows, we can shift our scan left or right, just like in GTM. Remember that you can only do this when the FCR is not transmitting. The top of the display represents 8km and 45-degrees to either side when the scan size is in Wide. There are three horizontal range lines that indicate 2, 4, and 6 km. In between, along the left side of the FCR Footprint are small lines indicating 1, 3, 5, and 7 km in between ranges. Sweeping back and forth when the FCR is transmitting is the Scan Wiper alternating between near and far scans. At the top center of the FCR RMAP display is a small line, this is the FCR Center Line. To the far left and right of the FCR Center Line are three additional lines that indicate medium, narrow and zoom scan sizes. Medium is a total of 45-degrees, Narrow is a total of 30-degrees, and Zoom is a total of 15-degrees. These can be selected either from the CPG Right Handgrip FCR Scan Size Switch or the Pilot’s collective mission grip. [Using ZOOM (button R1) enters a 6:1 zoom area, but this is different than the Zoom Scan size.] You can adjust display brightness with the Brightness (BRT) knob and brightness of the radar video image using the Video (VID) knob. I generally max-out the VID knob. You’ll notice many similar functions in RMAP as we saw in GTM, they all behave the same. These include the Next to Shoot (NTS), C Scope (C SCP), number of detected targets, ZOOM, RF Handover (RFHO), Acquisition Source, antenna elevation control, and storing Target points (TGT). Please see my earlier FCR GTM video on these. Regarding antenna elevation control, one particularly useful function of RMAP is to see whether your FCR is reaching the intended area on the battlefield, which may not always be the case in areas of hills and valleys. If you have dark bands of radar dead space running along the top or bottom of the FCR Footprint, you may wish to manually adjust the antenna elevation. For example: if the bottom of the FCR Footprint is entirely dark, you may need to manually adjust the antenna elevation down until you have a complete picture, which may happen if you are hovering over a hill and attempting to scan down into a valley below. Target detections in GTM and RMAP are interchangeable when not transmitting. Meaning, you can perform a scanburst in one mode, switch to the other mode, and the targets would still be displayed. You’ll note that we have a few target detections and indentations. These operate just the same as in GTM. The big difference is that we can also make out the terrain in relation to them. As you can see, the targets lie between lighter areas that indicate terrain relief (reflected radar energy). Because we are so low, the display is quite dark. However, looking outside, we can see the valley indicated on the RMAP. So, we can determine that the targets are in the valley ahead of us. Dark areas on the RMAP indicate surfaces that are not reflecting radar energy, or they are in a radar blind spot. Meaning, obstructions from terrain elevation make the area appear as black. You never know what may be waiting for you in one of these “dead spaces”. Beware. Just like GTM, we can send a radar-Hellfire down range using RMAP. I’ll switch to LINK to get my eyes on it. From this angle, I’m not getting a good look at it on the TADS. I’ll still WAS my Hellfires and fire off a couple. As mentioned, the RMAP picture is not fantastic when scanning very flat terrain at shallow angles. I’ll bring ‘er up to 300 feet and you’ll see a dramatic difference. Particularly with the VID knob up, you have a much clearer terrain picture using RMAP, and we can detect several more targets with the higher vantage point. This is a great tool for building battlefield awareness. Let’s use our last two Hellfires on them.

I'm looking into this, thanks.

You dont have to send a track file and settings if you don't like, but please keep any responses here related to the report. This is not helpful. Thanks.

I'll pass along to the team the request, but I haven't heard a lot of news right now. Sorry.

I have not seen this, does it happen every time?

Are the replays you are trying to view the same version as what you are trying to watch in, meaning were they recorded before an update?

Next time, if you do, crash, send the entire zip folder it creates and we can have a look to see if we can see anything. Thanks!

Hi, did you get this sorted? If not include your mission and issue you are seeing and I can take a look, thanks.

Include a track and a screenshot of your settings and we can take a closer look. Thanks.

I'm sorry I do not have any new info on this currently. Soon as we do we will share. Sorry.

We will have some news on this soon, we hope to make MT the only version available soon. Thanks.

I think the OP was already answered so I am going to close this, keep the bug reports coming as you see them. Thanks all.

Thanks, its a good idea, I might mention having something like that in the manual, a kind of best practices.

These are the options from the sim, correct?

You can make a bug report about that with more information and I would be happy to report. Thanks.

We appreciate the feedback, good and bad. We want you all to keep us honest and keep pushing us to be better. We only ever ask for it to be constructive and mature, which yours has always been as far as I can remember, so no worries at all. We do hear you even if it doesn't feel like it. Thank you, we appreciate it.

This is already reported internally, thanks.

We havent taken over the MiG-21, so not sure what you mean.