CypherS

Here is a quick example I made; I placed an F15C 10nm in front of me (basically it can fire) While it is in TWS mode this what it looks like in the Tomcat and Hornet: The cat has correctly recognized this as a threat and placed it in its lethal band. However, the hornet has incorrectly placed it in the non-lethal band (If the tomcat's behavior was the same it would have been placed in the center or the RWR) When the eagle fires the result is correct both jets mark the missile as a critical threat. The Hornet seems to have a bug here as the F-15 which is in TWS becomes a critical threat despite there being no lock. The same exercise can be done with Mig-29S, once it locks you the Tomcat will place it in the critical band while the hornet will place it in the lethal band. The point of all of this is that the current logic gives no value to target lethality. We have no way of knowing if an enemy Mig-29S using TWS is in firing range for us to maneuver preemptively.

Hello Maverick, I understand that the way the Tomcat and Hornet show the threats is inverted. My qualm is that the Hornet is actually placing targets which are lethal to you (have the potential to fire) in the non-lethal zone. If you place an enemy F-15C 7 nm in front of your nose the RWR will place it the non-lethal band(outer most band for the hornet) (very easy to replicate in the mission editor), despite the fact that it a potentially lethal target (and it actually is if it is using TWS). The only time it will move to the lethal band is when it locks you.

Alright, so a bit of digging shows that the RWR is still missing something. With all due respect to ED, I will be using data from the F-14 manual. (The Tomcat uses the same AN/ALR-67 class of RWR, either the same version or actually older) The tomcat uses the older logic of displaying threats on the edge but the point I make below are on which band the threat should be sitting in. Currently, the Hornet's RWR functions as follows; A threat which doesn't have you locked and is not within their firing parameters is placed in the non-lethal band. This is correct A threat which can lock you and fire but has not locked is placed in the non-lethal band. This is not correct, such a threat should actually be moved to the lethal band. A threat which has you locked but has not fired is placed in the lethal band(seemingly regardless of range, need to test this better). This is not correct as well, it should be moved to the critical band instead. A target that has fired is placed in the critical band (regardless of range as well). This is correct

It is puzzling really. The RWR antenna can tell signal strength according to Heatblur, the F-14 uses that to identify the azimuth by checking signal strength between each antenna.

Sure I understand that. But I am asking if any enhancements on signal strength will be added to any of those screens (the rwr analog display, EW page or SA) Right now if a target decides to bluff and takes a long-range shot unless he is on your radar scope you have no way of knowing if it is a legitimate threat; the RWR will treat an R-27ER shot from 60nm the same as one shot from 3nm. Especially if no one else has eyes on him for the contact to show on the SA page

Are we getting any improvements to the RWR, EW or EW elements of the SA page? As it stands it only allows us to guess the bearing to the threat, but no signal strength is given like the F-15C. Will this be added to the SA or EW page?

Is the text on the AMPCD SA page messed up for anyone? The threat rings are messed up and the data below the staple doesn't completely show

So the maverick is working fine for you with no curves or deadzone? For me, it's like trying to hit an and with a mallet. The slightest movement of the slew controller causes the maverick to move a lot and thus it doesn't lock

That isn't an actual mouse pad on the razer. Its a normal 8 way hat which is why it slews perfectly. Seems like for people who use an analog sensor the issue has not been solved

Pardon my ignorance but I do not think there is a slew control on that unit.. What are you using to slew the mav?

Which throttle are you using?

I have the slew mod installed and haven't seen a difference in the latest update. It is still very difficult to slew. You need a really large deadzone because the slew rate is fixed. If you are at 100% or 2% of the sensor range it will slew at the same rate Accurate slewing seems to be a pain because of this. If I barely move the sensor it will still overshoot the target I'm aiming for

So wags just posted that the throttle has issues processing the tdc down with movement. Are we still affected with this after replacing the sensor?

So which HARM modes will we be able to use?

I can't even imagine having to slew the mavs with the old nub. Thank you delta!!

That is very weird. When I had that issue happen I just emailed them pictures and they validated which it part (friction pad) was. They then shipped them after payment

The aim-9x has its own internal cooling system and does not need nitrogen from the rails. I wonder if that switch is used for the 9x

Is your HMD on?

Has anyone managed to export the RWR correctly? When using the usual method of adding it to the monitor lua the lines come out very thin and dim

How do I enable the JATAC here? I only see a hornet with mavs loaded

I am asking about the button on the sidewall of the cockpit in red with disp written on it. That button should run countermeasures program 6 (only editable in the .lua file) However by the virtue of being an emergency button it should not wait for a program to be selected for it to function. Master arm should be enough

yes but I also think that should not matter

Is the emergency countermeasures button on the left wall supposed to not do anything unless a countermeasures program is selected? Right now if you have the CM suite on with no program selected it does nothing.. Is this normal behaviour or is this a bug?

Is it possible to use a rotary encoder to control the motion of the knob? The controls allow you to only select what position you want is to be in, but you cannot control which way it rotates

The guy above is being very humble, but he has a great video on the subject. Also I've found this video pretty useful