[REPORTED] RWS radar stabilization and tracking loss

Same Issue here

Footage of the APG-63 (same radar family as 65/73) shows lock-ons averaging about 2 seconds from initiation to lock-on.

 

Look around the 6 minute mark here:

 

 

 

Yes, that is not realistic. ED must think that the antenna must be stable (or oriented upright from the earth) in order to detect and track targets.. This is not the case. In the same sense, the target does not need to be in level flight for the radar to detect it. As long as the target is in the cone of the antenna, it can continue to track it, regardless if the antenna cannot roll anymore. The antenna only rolls in the first place to keep the guard antenna towards the ground (sidelobe reduction). Once a target is being tracked, sidelobes dont really matter because the radar will use range gate tracking (ignoring returns not immediately around the range of the target) and thus not be affected by close range returns from the ground.

 

The extreme antenna roll would only have a minor effect in search modes in at low altitude (strong ground return) where range gating isnt being used (because your searching all ranges). Even then it wouldn't necessarily prevent you from detecting targets, it would just lower your detection range/probability (due to worse than normal signal to noise ratio).

 

If they applied this same logic to the Flanker (which has its guard antenna fixed to the bottom frame of the aircraft, meaning it doesn't rotate to keep facing the ground) it wouldn't be able to use its radar at all if the plane wasn't in perfect level flight.

 

 

 

I imagine that has to do with similar coding to the rotation issue mentioned above.

 

 

 

Ed seems to have set the lock-on mechanic to the area on the display rather than the range/cell (ie position in space). When you turn, the radar should continue to look for the target at that position in space, not at that column on the display. Meaning if you turn right when trying to lock a target, the radar beam should look like its moving left. (its using the true bearing from your aircraft to find the target, not the aircraft relative bearing.

 

Im also not sure if ED realizes that the radar is also only trying to lock a target at within the range cell of the brick, meaning it should be impossible to lock a target on the same bearing that is at a different range. It'll also used the doppler information attached to the brick to sort even further when trying to lock it.

 

 

 

Same as my first statement.

 

 

 

Not implemented yet.

 

 

Something else that no one has brought up before. The radar bricks move properly in azimuth when you turn, but they dont move in range as you fly closer to them. I'm not sure if this is accurate or not.

 

But what this means is that if your closing in behind someone who is flying away, the bricks will actually look like they'll flying toward you as the newest bricks will be closer. This can confuse the pilot as to the direction the contact is flying via bricks alone. If the bricks were locked to a position in space (that was my initial assumption) they would appear to slowly move toward you as you flew toward that position in space until they aged out.

 

What I do know is that bricks are a static representation of raw hits at a precise time in space. The question is, is it static to a position on the earth (like a LAT/LONG) or static to the display.

 

We know its not static to the display in azimuth (bricks "move" side to side when you turn. real footage shows this to be true). So if the brick moves relative to your aspect, shouldn't it also move relative to your position.

I can't believe after everything you've written this has been marked [NOT A BUG] - surely this isn't how they're intending for it to work?!

I can't believe after everything you've written this has been marked [NOT A BUG] - surely this isn't how they're intending for it to work?!

Yep, for me also in this case the "not a bug" is a bold assertion.

Is this the same thing as the thread that they said isn't a bug for radar stabilization? Haven't seen any confirmation from officials about this issue.

No, it's quite different. It's a complete freeze of the track after lock as if it was locked in time and space, but moving away from you (range does not decrease on hud or scope)

I might have to make a nice video on this if it's not acknowledged soon.

Is this the same thing as the thread that they said isn't a bug for radar stabilization? Haven't seen any confirmation from officials about this issue.

No, it's quite different. It's a complete freeze of the track after lock as if it was locked in time and space, but moving away from you (range does not decrease on hud or scope)

 

 

I might have to make a nice video on this if it's not acknowledged soon.

I see the same issue you describe with the f18 aim 7's and aim 9. Hopefully they can confirm because there was a hotfix today but none of this stuff was in the patch notes.

Confirmed, and not fixed in the Update 7 hotfix. I have this problem every time I try to use AIM-7.

I have this problem also. I lock a target and it doesn't track then the target box fixes one one spot before dropping, switching to other weapons doesn't fix it.

Sent from my SM-G955F using Tapatalk

I have the same issue. Makes blowing bandits up WAY harder.

Guys, this seems to be mission related, I created a new test mission and it works fine there however it does not on the missions i have that worked before the update and loading them up and saving them doesn't seem to fix it.

So not sure what the deal is, something the new version no like in the mission I guess.

Guys, this seems to be mission related, I created a new test mission and it works fine there however it does not on the missions i have that worked before the update and loading them up and saving them doesn't seem to fix it.

 

So not sure what the deal is, something the new version no like in the mission I guess.

Confirm...i just tryed and is like that for me too..now i have like 20 mission made with MOOSE to throw away

:cry::cry::cry:

I tryed to make a brend new mission using MOOSE and i have the bug again..

Testbug.trk

Template_caucasus_test.miz

Did some more testing earlier.

Radar was fine in a "simple" mission that I put together myself.

Ran an Inferno mission, and the radar for the Aim7 is "locked up". Fine with the Sidewinder.

Inferno mission?

I did some more test.

If i put in a mission JUST A COUPLE of targets all runs fine. If I put several targets, then we have the wierd beheavour.

+1 Same issue.

I did some more test.

 

If i put in a mission JUST A COUPLE of targets all runs fine. If I put several targets, then we have the wierd beheavour.

Hmm, you might be on to something, the mission I made only had one bandit in it, Inferno and the Persian Gulf training mission I downloaded from user files don't work and they have tankers and awacs by default so there are many planes in the air.

But, if it were just target count then I think we'd have more complaints from multiplayer...maybe it just number of AI planes.

I haven't done any multiplayer lately, might just jump on the 104th and see what happens. Also add a few bandits to my test mission.

Guys, this seems to be mission related, I created a new test mission and it works fine there however it does not on the missions i have that worked before the update and loading them up and saving them doesn't seem to fix it.

 

So not sure what the deal is, something the new version no like in the mission I guess.

Up in the thread i put also atemplate i use to set up my scenarios. It use MOOSE framework scripts. In this mission there are several units and there i have the wierd radar beheavour.

I hope is not connected with the use of lua scripts.

Multiplayer has been mostly ok for me.

The worst one is the F15 1v1 BVR that I adapted to the F18 (just changed playable aircraft from F15 to Hornet). It happens every time on that mission.

Maybe it’s something to do with spawning scripts? That’s the mission where you can use the F10 menu to spawn various enemy aircraft for 1v1. They all spawn in the same place, just only when you select them from F10. Just spitballing though...

Multiplayer has been mostly ok for me.

 

The worst one is the F15 1v1 BVR that I adapted to the F18 (just changed playable aircraft from F15 to Hornet). It happens every time on that mission.

 

Maybe it’s something to do with spawning scripts? That’s the mission where you can use the F10 menu to spawn various enemy aircraft for 1v1. They all spawn in the same place, just only when you select them from F10. Just spitballing though...

Wich scripts are used to compile this mission? MYST?

I had the same issue twice. Once in a single player "Through the inferno" mission and the second time online in the "Georgia at war" mission form Hoggit.

Maybe it’s something to do with spawning scripts?

If it always happens with scripts that spawn aircraft, and the point in space is fixed, is it locking as yet unspawned aircraft (which are by definition stationary)?

Off Topic, but WRT the slow HUD refresh rate questioned earlier - that's as intended

Wich scripts are used to compile this mission? MYST?

Not sure, it’s the stock ED quick action that comes with the F15, I just changed the playable aircraft.

That being said, just played multiplayer for awhile and it happened a lot, so disregard my previous assessment...

If it always happens with scripts that spawn aircraft, and the point in space is fixed, is it locking as yet unspawned aircraft (which are by definition stationary)?

 

 

Off Topic, but WRT the slow HUD refresh rate questioned earlier - that's as intended

No, the HUD freezes and doesn't care if you're moving or not, it just stays the same way the moment you lock a target, it just freeze.

The locked target stays in the same spot relative to the HUD despite changing attitude or heading.

No, the HUD freezes and doesn't care if you're moving or not, it just stays the same way the moment you lock a target, it just freeze.

 

The locked target stays in the same spot relative to the HUD despite changing attitude or heading.

I had this weird bug yesterday for the first time in my little training mission, no scripts or trigger - just some AI units waiting to get shot down and get bombed. I locked my first AI airplane and it froze. Attached is a video showing the issue and a track file wich thankfully is also showing the bug if i replay it. I started the video recording as soon as i realized that i see the bug after locking the enemy airplane. this mission was opened and saved after the latest Open Beta patch.

Video should be 1440p soon.