Ghosty141

So let's get this straight. Basically the documentation CANNOT be right. It lists the yellow box clearly as RADAR FOV meaning, the radar can see everything in it's field of view. In the following screenshot we can clearly see the LST is in the box of the AZ/EL page and within the elevation range of the radar on the right side. The problem arises once I move the yellow box (or radar elevation) so that the target is OUTSIDE of the radar elevation boundaries. On the radar we can clearly see the LST is 2k ft below the cone of the radar. On the AZ/EL page though the contacts are outside of the field of view of the radar (the radar cannot see them anymore because of the elevation), they are still shown within the yellow box called "Radar FOV" in the documentation. This discrepancy makes the AZ/EL page almost worthless since I can't use the yellow "Radar FOV" box to control the radar elevation since based on it, I can slew my targets out of the radar FOV while the yellow box still indicates they are in view until they fade.

@NineLine any progess on this?

The thing that irks me about it is that it's VERY easy to misclick an MFD button and accidentally turning off your RWR which you don't notice since it only makes a sound when being turned on. Maybe this sounds stupid but, who asked for this? Have you guys noticed it in playtesting? I find it really annoying, at least let me turn it off maybe. I can only see this being useful for people without TrackIR.

Hi, this doesn't need much talking, basically the border of the AMPCD lets the clicks pass through to whatever is behind it resulting in accidental presses of the ALE47 buttons (which can be quite catastrophic ) If you click where the red arrow points in the picture you it will actually hit the ALE 47 Power button for example.

This is 100% what has happened, you can't uncage without master arm on.

I personally don't see the problem as long as you use an axis for the TDC since you can just change the curve and saturation as well as deadzone in the axis tune setting making it as slow as it was previously again.

This should be correct, TWS always needs a priority target, if none was selected in RWS it's gonne select one for you. The problem I am describing is when already having acquired a L&S target, pressing sensor control switch to the side of the radar should place the LST into STT, this doesn't always happen though since it randomly skips through other trackfiles.

This would only work within the limits of the seeker though, for example and aim9m would have a hard time the close it gets, right?

Hi! I generally agree with the notion you've explained in many other threads that artifically increasing the planes "size" to make it easier to spot is a bad solution and other steps should be taken to fix this if poissible. What I want to know your opinion on is the fact that spotting IS different depending on the resolution, on 1440p it is noticeably harder than on 1080p. That's a part of the core issue many people have with the current system. It feels bad to trade in visual fidelity for competitive edge. If needed I can try to get some examples on 1440p vs 1080p at various ranges although I'm don't have too much time at my computer right now so you might need to wait a few days for this.

Any progress on this? I personally find this one of the most annoying issues in PvP A/A fights since if a bandit is coming at you at close range in that space between HUD and HMD it's impossible to lock him unless you completely turn off blanking which is a pretty bad solution.

I can also confirm this sometimes happens. It's not tied to the missile since I've had this happen using Fox 1s (sparrows to be exact).

Firstly FACQ/AACQ are broken currently so while @sk000tchs advice is absolutely correct it's currently not a good idea to press SCS right to lock the L&S target. Check my bugreport for details (incl. track file and youtube video). TDC depress is currently your best bet. I haven't tried it yet but I this MIGHT (!!!) work if you are extremely quick and break lock immediately after firing. In DCS STT should always give an RWR warning. IRL you wouldn't lock a target in RWS mode since TWS is used for engagements. For example once you shoot an AMRAAM the radar automatically (!) switches to TWS AUTO mode, this is currently not implemented. TWS AUTO should work differently than it does now too, check this thread out for some of the details:

I found the ACM modes quite inconsistent in the hornet. With LACQ for example I couldn't get a lock on a bandit I saw right infront of me but I could see him on the radar after giving up on LACQ. Maybe it was his maneuvering but I don't know.

@BIGNEWY @NineLine I don't wanna be pushy but could you please remove the tag since it's simply false. This is a bug and should be fixed since it makes AACQ kinda useless in this situation.

Glad I'm not the only one. The "correct as is" label should be removed since the video clearly shows this is a bug.