NineLine

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.

The last one was a little light, but I don't think it is fair to judge based on 1 patch, previous too that there were quite a few, and because of the new patch timeline it can take a little longer to get things out to everyone based on internal testing. August 14 (interim patch) Fixed: RWS target symbols no longer show altitude when cursor is hovering over it August 9th (major patch) Fixed: Crash during rearming in some cases. Fixed: Freeze/CTD when selecting STN field in TNDL page, from dynamic spawn only Fixed: FCR is detecting targets ignoring scan volume. Fixed: HYD OIL PRESS and TO/LDG CONFIG lamp housing. Fixed: Typo on throttle RNC - RNG. July 22 (interim patch) Fixed: Crash during rearming F-16C in some cases. July 11 (major patch) Radar: Introduced false targets. They are caused mainly by internal receiver noise and ambient noises at receiver input. The radar internal circuits maintain false target rate constant with an average frequency of one false alarm per minute. Fixed: Сrash when switching weapons when using unlimited weapons. Fixed: Crash when receiving SEAD Target into steerpoint 127. Fixed: Crash using GBU-24. Fixed: ACM modes stop working if you lose lock. Fixed: Laggy HUD TD box. Fixed: Level 5 gun piper. Fixed: ACM lock lagging/lost. Fixed: Bomb mode selection not updating dynamically. Fixed: Unable to bug MSI tracks that are correlated to radar memory tracks. Fixed: Non-selected AGM-65 seekers that are not in TRACK mode are not resetting to SLAVE or BORE modes. Fixed: Search target hot lines don't work. Fixed: AGM-65 can become non-space stabilised after launching. Fixed: Elevation bar scan values are wrong in certain circumstances. Fixed: Texture artefacts and geometry errors. Fixed: Maverick seeker LOS slave to FPM at TMS Down Ignores SPI. Fixed: TGP cannot change level setting in MGC mode. Fixed: FCR "NONE" hides everything, including your own FCR tracks. Fixed: FLCS TO/LDG Gains affected by weight-on-wheels. Fixed: In external view, pilot helmet clips canopy when looking back. Fixed: Inconsistencies with the JDAM AD CNTL settings. Fixed: CBU-87/97 inconsistencies with CCIP/CCRP calculations. Fixed: Impact Distance setup in SMS ripple is halved on impact. Fixed: Need to reverse left arm patch orientation. Fixed: TNDL Power resetting to HIGH in ME. Fixed: HARM in POS missing leading zeros on bearing in HUD. Fixed: AGM-65 in EO-VIS mode removes range scale after first launch. Fixed: Switching AG Weapon on SMS page keeps delivery mode of previous selected AG weapon. Fixed: Able to move A-G radar cursor without SOI. Fixed: Rename option on HSD CNTL page 2 to "A SMDL". Note: Although not ready for this update, the Sniper Advanced Targeting Pods is in advanced development and planned for release later this year. June 5th (F-4 interim patch)) Fixed: Сrash when switching weapons when using unlimited weapons Fixed: Reverse left arm patch orientation Fixed: Bomb mode selection not updating dynamically May 22 (F-4 Release) Added new model pilot - work in progress. Added improved movements of the pilot head and torso - work in progress. Added Maverick and HMCS Auto-Boresight, automatic for hot starts. Cold starts require manual boresight. Fixed: Increased G-warmup effect time. Added Bomb Fuze Options and Settings from ME - work in progress - missions where laser code is set to anything but default (1688) will need the code edited in Mission Editor using the new method. Fixed: Tuning the IFA alignment and further FIXes. Fixed: Missing scale on the standby attitude indicator. Fixed: GPS time starts at 00:00 when entering a mission. Fixed: FCR Air to Air Header fix. Fixed: Wheel friction imbalance. Fixed: FCR target Min/Max altitudes inverted in negative antenna elevation. Fixed: Handoff from TGP to TV-guided AGM-65's is partially functional using TMS Right. Fixed: RWR displays radars in "Track" mode in the inner "Missile Launch" ring. Fixed: CCRP lateral drop limit too small. Fixed: Scan volume twitching around when bugged target near or beyond gimbal limit. Fixed: RWR SYS Test no longer functions. Fixed: True heading on ICP stuck at 00. Fixed: Boresighting Mavericks is aligning with point mid air. Fixed: HSD zoom glitch. Fixed: Spotlight scan volume and EXP reference box snap from centre of display instead of appearing directly at cursor location. Fixed: Entering OVRD while in spotlight search can cause radar to stop working. Fixed: TGP does not take INS drift into account well (coordinates and height of the point changes). Fixed: Rolls left under positive G. Fixed: Search target hotlines don't work. Fixed: RWS SAM cannot change radar range scale is designated inside an auto-range zone. Fixed: Maverick seeker LOS Slave to FPM at TMS Down ignores SPI. Fixed; Right MFD rocker switch labels incorrectly refer to Left MFD. Fixed: JDAM with nose plugs fitted show 0 second AD in SMS by default. Fixed: Exhaust "turkey feathers" graphical clipping/misaligned. NOTE: The Sniper Advanced Targeting Pod is in active development for release later this year.

Have you tired resetting your VR view? Recenter? I moved this to VR as I do not think its a F/A-18C issue, but sounds like maybe something on your end.

We are still very actively developing the Viper, and we in fact welcome and enjoy the user feedback to have us look at things that might not be up to snuff, this is one of the many reasons we do Early Access. So maybe take a break and try out the F/A-18C for a while, but trust me, we are not giving up or finished with the Viper at all. Thanks

As I said, it will be investigated. There is no need to be rude. Thanks.

Yeah track doesnt seem to work here either. I tried setting down an Sa-11 site from templates in the mission editor, and it seemed to function and reload, etc as expected. So maybe its something in the mission? Scripting or something else?

Reported, thanks!