MARLAN_

It is not anywhere near that bad real world.

As far as I'm aware, you can launch on an offboard track file - you wouldn't even need radar contribution and could bridge that offboard information from L16 through your aircraft, transmit through your radar, to the missile - albeit with a lower data rate than with radar contribution. The target could even be launched on outside of your radar gimbal limits (thus totally unsupported after launch) and be able to fly to last known intercept, like how in DCS if you lose radar contribution after launch. I'm not quite sure what you're asking with AACQ - if the track was designated as an L&S and is not inside your scan volume, but is inside your radar gimbal limits and you command FACQ or AACQ (SCS right) your radar would command STT about the L&S, if you were in TWS AUTO, your radar would automatically slew towards the L&S (and if it was outside radar gimbal limits it would move towards that side of the radar until the track entered your radar gimbal limits)

While MSI isn't fully implemented in DCS, in the future when it is, you WILL be able to designate tracks that are not inside your radar scan volume. Also note, designating an L&S is NOT a lock.

Six'thd (noticed this also)

Seems related to the following linked post as well, where exiting TWS SCAN RAID will move your scan volume to the center of the RDR ATTK display regardless of where it was originally pointing. As seen in the track, while in a crank and utilizing TWS SCAN RAID the bandits will fade until lost (initializing using 16 second timing) and will be regained immediately once TWS SCAN RAID is lost/exited (and the scan volume slews back onto the bandits, since it teleports back to center), later in the track I change the timing to 2 seconds and you can see the issue happen rapidly. Let me know if you need evidence regarding TWS SCAN RAID should be centering on the L&S and I can PM it. TWSSCANRAIDNotCentering.trk

Should just be a depress & release on the ATTK or AZ/EL page when there is no Target Under Cursor.

I think I did a poor job of explaining the problem to the team, here's a quick picture to help explain the problem @BIGNEWY On the top half, the current DCS implementation, the LOST cue is displayed as soon as the blue fighter begins his crank, because the red fighter is no longer inside RMAX, but in that example, the LOST cue should not be displayed at all, because the red fighter has not maneuvered, and is still inside the original WEZ. The blue fighter maneuver should not change the missile in flight (orange arrow) to cause a LOST cue. On the bottom half, shows how it should work. In this example, the red fighter decides to maneuver, and he exits RMAX, which means the missile (orange arrow) will no longer be able to kinematically intercept its target, thus LOST should display as soon as the red fighter crosses the RMAX boundary. Additionally, if the red fighter decides to turn back around and flow back towards the missile, causing him to re-enter RMAX, the post launch HUD Time-To-Active/Time-To-Go and RDR ATTK "A" (husky) or flashing "A" (pitbull) will be displayed again.

Looks awesome as far as I can tell! I don't know if it's important enough to squeeze in, but only the lead would report base, wingmen would only report "Dash 2, Gear" - At least, this is what I've been told by a USN F-18 pilot, it probably changes based on field/branch/country/etc.

Turning into the wind at the inbound call would work as a general fix, but there should also be a mission editor trigger to turn into the wind, that way milsim groups can command the carrier to turn into the wind at specific times (cyclic ops event windows) - right now with wind that doesn't change we can just tell it to turn into a specific heading, but when dynamic weather is implemented we would need a "turn into wind" function in the editor or otherwise.

Track File ScanRaidUndesignate.trk

Currently pressing the undesignate switch will exit TWS SCAN RAID, it should switch L&S/DT2 or Track files as normal.

There should be consequences for overstressing the aircraft. The consequence should not be your wings exploding. I already mentioned examples of good consequences. Wing explosions is not a good placeholder until proper damage modeling is implemented. Until that time that proper damage modeling is implemented it would be *more* realistic to take no damage at all than to have your wings detonate.

People want realism in their simulation. Wings breaking off by using the paddle switch is not realistic. It's that simple. How people use the paddle has no bearing on the discussion which is that the wings breaking off is unrealistic and silly. This is a grossly unrealistic feature in the simulation. Until proper damage modeling (permanent wing bend, performance loss, FCS failures, fuel line leaks, etc) is modeled, total catastrophic failure of the wings should not happen. Maybe if someone is trying really hard to break the wings (10G+ pulls repetitively 20+ times) they might snap off. All you are arguing for Gypsy is for a less realistic sim, maybe you are biased by your feelings on how people use the paddle, but that should have no bearing on creating a realistic simulation.

The AIM-120C is supposed to loft, that is normal, although it may not be normal that it always lofts despite the initial shot angle, but I haven't tested this much yet. The ASE dot however, is not supposed to be only centered on your target, it should guide you into the most optimal firing position considering lead and loft, the current implementation isn't accurate. For now, you can improve your kinematics by ignoring the dot, and pulling some lead and loft on your own.

Of course! It almost seems the behavior has been inverted since I last looked. Now they always leave their formation lights off no matter what.

You are right! Sorry, I could have swore the last time I checked it behaved how I mentioned, maybe it was a stealth change in the update, or I missed it in the notes from a previous patch. I usually make sure before posting a report except this one time since I was fairly sure, that shows me for not checking! Either way, glad to see the AI keep their formation lights off now! Thanks for checking.

AI leave formation lights on at all times, even if the flight lead turns them off. In addition, formation lights are used at night time, or in low visibility conditions (flying through a cloud layer for example) so any time AI are used for videos/screenshots it takes away some of the authenticity.

I brought it up because it sounds like they are issues possibly caused by the same problem

The radar in DCS moves ~30 degrees per second (you can time this) which should mean any turn you do wouldn't affect the radar, it seems to be lagging behind more than it should be as far as I can tell. Roll itself though, should have no effect on the radar.

High quality equipment is a huge difference in the level of precision you can obtain, however you need to be skilled already to take advantage of that increased precision. So that means, yes, definitely, better equipment is absolutely a big deal, but until you have the skill to utilize the higher precision it won't magically make you good at flying.

The part where rolling affects the radar seems to affect the A/A Radar as well. It would likely be quite difficult to find specific evidence that says the radar doesn't get degraded by rolling. The F/A-18C pilot I know has said the radar should not be affected by rolling, if that helps at all. It's particularly silly for A/A, during a re-attack, or even a CRANK, you can lose radar SA with the DCS modeling causing roll to degrade the radar. (Not entirely sure if it's specifically roll, I've just noticed loss of radar SA during cranks/re-attacks, it may have something to do with G, I just tested now and was able to reproduce it, but I am unsure what exactly is causing it)

If you employ in STT the bandit will receive a track indication (from STT) and then a missile warning once the AMRAAM goes active. If you employ in TWS the bandit will only have a search indication, and then a missile warning once the AMRAAM goes active. For the record, "soft/hard lock" isn't a thing, the only lock is STT. In TWS you designate targets (L&S, DT2).

FRM-000 also explains the kinematic portion of LOST. Ill PM that as well to BN once I get off work. (PM'D)

Cat herder

I think it would probably be common sense you would not get a "LOST" indication (indicating the missile in flight is no longer able to kinematically intercept it's target) due to your ownship heading changing while the missile is already in flight. I'll see if I can dig up proof but I'm almost certain the current implementation is not accurate. It also causes a ton of confusion (I've had at least 10 people be confused now thinking their missiles are lost when they crank).