Xhonas

Hello there ! @BIGNEWY Any news regarding this?

Hi there @Lord Vader. Yes, i have the target in STT. So, after firing the missile, you can press the PB 10 (in the right mfd in this case) to switch to flood mode and guide the missile. It goes into flood for a few secs, and after that it returns back to tws/rws for no reason and that interrupts the guidance. I believe that is a bug because about 2-3 patches ago if you pressed the PB 10 after firing the missile the radar would switch to flood and guide the missile all the way if kept inside parameters, and in many other modules you can switch to flood / illumination mode after firing in STT. It would not switch back to tws/rws uncommanded like its happening right now. If thats not a bug, then fine, its just that it works very differently from every other module that have the same system. This was a very useful function to use against beaming targets trying to break your radar lock by notching. https://streamable.com/hxlswo Check this video. Both missiles guide in the flood mode after pressing PB 10, guidance is interrupted after the radar switches back to tws uncommanded.

HRP | Trigger - MiG-29A HRP | Fiber - MiG-29A HRP | Derby - F5 (WHERE F5?) / Mirage F1EE (in case no F5) HRP | Brand - Mirage F1EE HRP | Juquinha - Mirage F1EE HRP | Ghost - GCI

Hi there. There is an issue with the flood mode in the F/A-18. After selecting the flood mode to guide the Sparrow, the radar switches back to TWS after a few seconds for no reason, completely trashing the missile. Aim7 flood mode.trk

Hello there. Currently there are some issues with the APG-73 that makes it impossible to use the Aim-7 vs cold targets in the F/A-18 First issue is: When you are in STT and shoot at a target with the Aim-7, the radar will enter the memory mode and eventually will drop the lock, despite being in ideal conditions to sustain a lock, making the Aim-7 lose track of the target. Aim7 Cold target.trk Second issue: If you are in TWS with the Aim-7 selected, if you fire an Aim-7, the radar should automatically command a lock on the target and switch to PDI. But thats not what happens. Instead, the radar maintains whatever PRF you had selected previously, and never switch to PDI, making it impossible to guide the Aim-7. Aim7 tws to stt.trk

RWRs being too precise plays a big factor in this perception, and also the fact that missiles appear on the RWR when they are still too far from the defending jet, giving it plenty of time to think and defend in the notch. There are a lot of online references on how RWRs should work and EW in general, if ED used available data in our RWRs this perception would be very different. I wont send it here to avoid breaking any rules, but i believe that ED is aware of these references. Aside from fixing some problems with the Aim-120 terminal guidance, i don't think there is a lot more they can change to improve tracking targets that are in the notch.

Hello there, not sure if this could be considered a bug, but the Aim-9x behavior in the F/A-18 is questionable. I'm providing 3 tracks to help explain what the issues are. Aim9x no radar lock.trk In this first track, i acquire the target with the Aim-9x without the help of the radar, only slaved to the HMD. I put the aiming circle at the target, and press the cage/uncage button and the missile seeker is now locked into the target. Nothing wrong so far. The problem is, the moment that i take the HMD fov off the target, the Aim-9x loses the lock on the target and is slaved into my helmet again. I didn't press anything, i just moved the HMD Fov off the target. I belive that the missile should stay locked into the target, and only be slaved back to my helmet if i pressed cage/uncage button again. The way it is working now is very inconvenient. Aim9x with radar acm lock.trk In this second track, i acquire the target with an ACM mode and with the Aim-9x selected. As soon as i get a radar lock, the Aim-9x is slaved to the target the radar is tracking, no problem. Now, if you press the cage/uncage button, sometimes the missile will get slaved to the hud (but not to the helmet), and sometimes it won't. Also, when it gets slaved to the hud, if you press cage/uncage again to slave it back to the radar, sometimes the missile will fail to track the target being followed by the radar, as you can see in the trackfile. Aim9x with radar bvr lock.trk In this last track, i acquire the target with the B-Scope and the 9X selected. For some reason, it is impossible to uncage the missile into the target while looking at it with the Helmet. The missile sees the target, you get the tone, but pressing cage/uncage does not achieve a seeker lock, neither slaves it to the designated L+S. The only way to slave the missile to the radar lock, is looking directly at the hud (if the HMD is on). If you take the hmd fov off the hud, the missile will be slaved into the helmet, and unable to achieve a seeker lock. Also, by the end of the track, you will see that the missile slaved to the L+S doesn't get a seeker lock. Just hear the tone, you get that tone that indicates that the missile sees something, but isn't in the threshold to get a lock (it makes that bap-bap-bap-bap-bap sound), despite being in perfect parameters to achieve a lock. Sometimes you get a more high pitched tone, indicating that you can achieve a seeker lock, but pressing cage/uncage does nothing. Sorry if some of the descriptions were confusing, just watch the tracks to be clearer.

I know its off topic, but what about a Su-27/30 ?

In the current patch (DCS OB 2.8.8.43704) the long-range laser lineup system is not visible on daylight and is barely visible at night. May be a multithreading problem. I would like to see this problem fixed since this system is very important to provide visual lineup information for case 3 landings. Please see the screenshots and feel free to take a look at it ingame using the trackfile: nullLong range laser unable to see.trk nullLong range laser can barely see night.trknull null

Hello there ! When flying the F/A-18C in DCS it isn't hard to notice the amount of attention that ED gives to small details. With that in mind, i would like to ask for a rudder flutter effect in the F/A-18C. Since Razbam was able to do it in the F-15E i assume that there is a technology in the DCS engine that would support this effect in our loved Hornet. Here is a video of this effect in a Real F/A-18:

Squadron: HARPIA Timezone: 17z - 20z Aircraft: Av-8B, F-5E F-16C, F/A-18C, F-15E, F-14B, JF-17 Maps: Caucasus

Squad name: Harpia Squad lead: HRP | Trigger / HRP | Derby Time Zone: UTC-3

Hello guys, just got the Sinai Map, overall looking good an running great at my system. But i have been able to find some very abnormal texture transitions, as you can see on the attached pictures. Its very obvious where the texture have been cut and doesn't look natural. I have spotted many clipped courts and swimming pools on those resorts textures. Coordinates of where this is happening are on the status bar, but there are many other places around the map that the same thing happens.

Will the new radar update feature ground clutter (false returns) when flying at low altitude in both F/A-18 and F-16 radars like seen in this video? https://www.youtube.com/watch?v=VseTWC_jSE0&t=251s already timestamped.

Hi there, in the current OB [2.7.17.29140] version, the AiM-120 fails to hit a target if it is barrel rolling. The missile will track the target all the way but it will miss by a few feet in the very last second. Please, watch the following tracks: aim120 track 01.trk aim120 track 02.trk aim120 track 03.trk aim120 track 04.trk aim120 track 05.trk