Santi871

The problem is not with extrapolation but with the draw rate of all HAFUs on both the radar and SA screens. I don't know why but the way it's coded means HAFUs are redrawn at a relatively slow refresh rate compared to something like bricks. I'll see if it can be fixed, it doesn't happen in the Viper.

The acceleration vector in your track is happening because the target is maneuvering, not because of your own maneuvers. If I try it with a mission where the target is flying in a straight line, there's no acceleration vector no matter how much I maneuver. If you manage to find otherwise, please let me know. accel-vector.trk

It's known and fixed internally.

Then again, we're talking about a plane with lots of stupid little choices. Why is there a HOTAS shortcut to go from RWS to TWS but not one to go from TWS to RWS? Why do I only have the choice to zoom into the SA but not out (without cursor bumping)? Why do I have no option to show the altitude of targets at all times without having to play TDC/step box/undesignate minigames? Why can't I couple the SA/HSI range to the selected radar range? Just odd stuff.

Exactly. Things like "can X RWR detect Y signal" are very closely guarded secrets. So it's a matter of seeing why the current assumptions/logic are the way they are. I didn't code it so I have no idea.

Every RWR is different, and what's more, anyone who knows the answer isn't going to tell you regardless of which specific RWR we're talking about. But if we want to make assumptions and generalize, which is fine for DCS, I would say no, you shoudn't.

I'm not sure what we're talking about anymore but there seems to be some confusion. PDI is not CW. Only F and later Sparrows support PD guidance. STT is also neither PDI nor CW. PDI is a specific waveform to guide Sparrows that support PD guidance. Nothing to do with the AMRAAM whatsoever.

It's known. My speculation (so don't quote me on this) is that given that IRL there will almost always be at least one advisory (CDATA), the recommendation to keep the radar and SA away from the LDDI is still a thing, so it hasn't been given much priority to fix. Again, I'm speculating though.

Yes

This is already fixed internally, sorry, I didn't notice this thread

Here you go:

You are confusing L16 message transmission capabilities with awacs capabilities. You could transmit 300 messages a second, but if your radar takes 10 seconds to complete a rotation and update a target, then that target will be updated every 10 seconds. That's why I asked if this is for all of L16 or just the awacs.

Please expand on what and why you think it's wrong. Is it just awacs? Or all of L16?

Are you suggesting that an AWACS would provide an update rate higher than every 1 second? Or am I misunderstanding?

TUC interrogating in LTWS is a bug. There's no TUC automatic interrogation. The L&S can be auto interrogated but the on/off option for that is in the az/el page. It does initialize to on so I'm not sure whether it's being simulated here or not.

Yup. I'm not entirely sure fox3 can be told to guide to an arbitrary point in space right now but I'll ask. I suspect it might be a current engine limitation.

Like I said, I can reproduce in OB but not internally, so better to wait until next OB and then I'll check again

Okay I just tested it with a different miz, it's working correctly as the extrapolated aspect isn't updated with the "real" aspect. Edit: I can reproduce the bug in OB but not internally, so will check after the next OB update to see if it still happens aspect-memory.trk

Yes, the fix is in testing.

Both their velocity and acceleration are being extrapolated, so if they were turning at the time they were lost by the radar they will continue to turn in memory. In the track for this bug https://forums.eagle.ru/showthread.php?t=268730 you can see they recommit but they appear to continue turning in the HUD. With that said, trackfile memory shouldn't be controlled by the raw hit timeout setting so it shouldn't be possible to manually select 32 for trackfiles. Do you have a track that shows the aspect on the HUD updating as they recommit? I'm not 100% convinced

Pressing RAID in RWS still should switch to TWS without an L&S, but in that case manual centering is selected.

Yes, though it is generic to the gbu-38 and not specific to an airframe.

Thanks, it's much more clear now. Will report.

Your targets are too closely spaced together, and they are notching your AMRAAMs, then AMRAAMs are then reacquiring wrong target. I just tested it with properly spaced targets and it works fine.

TGT should stay boxed. The diamond in HSI/SA page should move to the new location, but that part is bugged. Also when creating a designation with FLIR or HUD, TGT doesn't become boxed and the diamond doesn't show in HSI/SA, but both should happen. It's reported.