Baikingu

Here is a simple demonstration of the issue. With a track as requested :) In the track I enter TWS and the contact becomes L&S. I put the radar scan in auto then I do a "defensive crank and dive" then put the contact outside the radar gimbel intill track is lost. Notice the radar is still in Auto mode. when I turn back I have to press the push button to get it back to manual mode so I can adjust my radar elevation to reacquire the contact. TWS scan auto to man.trk

Hi! First of all glad to see bugs getting some most needed attention:) Keep it up please:thumbup: So when I designate a contact in TWS and put scan in auto I'm have read that if "lock" i lost the radar scan will automatically revert back to man mode. This does not currently happen. Whitch resorts on fumbling with push buttons in the heat of an engadgement to get it back to man so I'm able to reacquire. Its super easy to reproduce. Simply designate a contact in TWS and put scan in auto. Then turn so the contact exits the radar gimble. Now notice the radar search is still in Auto. This also happens if the contact notches you. So is this as it suppose to be or is it a bug? Thanks

The range you set on your radar scope in the cockpit (lets say 40 [nm]) does not imply that the radar will only scan out to max 40 nm. The nr. 40 in the top right of the radar display only indicates the radar scope's current "zoom". The radar it self will scan out to 180 nm and beyond. (All though you prob. won't get a radar return[contact] at 180+nm. hence the 180 max range "zoom") As for up close you have to concider that the radar beam emitted from your radar is in a cone shape protruding out from the nose of your plane in a about a 3 or 5 degree angle (not quite sure of the degrees). See pic. As you can tell the closer the target gets the more you/the radar has to scan up/down/side to side in relation to the target to keep it in the radar beam. (cone) In STT the rader focuses in one target only and follows it automatically up/down/side to side with in the radar gimble limits to keep lock. But in TWS you have to do this manualy if you don't put it in AUTO mode. Then the radar will center the scan zone on your L&S cue and follow it with in the radar gimble limits. Note: TWS was not implemented in till late last year if I remeber correctly. Before that we only had LTWS which is essentially RWS just with the ability to see L&S then you hover the TDC over a radar contact. THis might explain why you could "unlock" with RESET before

I know. I was one of the ones to report the bug a while back. Was under the impression it had been fixed. [happy face]. (apart form the DT2) Apperantly its not [sad face]. I really hope it get's fixed soon. As i consider radar/missile (fox3) to be a core feature. Especially after years of development. Thanks

Really!? I have only tested it against AI. And they only seem to start defending when the missile is within 10nm. Anyway if that is the case its a shame. Don't really want to keep flying the Eagle for CAP sorties all the time. (as i don't own the Tomcat/Viper etc.) The situational awareness in the Eagle is awfull.

Hi! Good stuff getting the aim-120 TWS mid-course guidence issue fixed. :thumbup: But I discovered that there is still no mid-course guidence data-link for the DT2 target. I soft-lock two targets in TWS. First one L&S and the other DT2. Shoot on L&S target -> undesignated -> second target now L&S -> fox 3 nr.2 The first missile tracks. But the second one behaves like "before". (Flyes of the rail stright to the last radar return at launch but doen't track the target) See track. Thanks TWS DT2 no guide.trk

I did more testing and sure enough the elevation < does change with the target. But the TDC dosent update. So then I guess i lose lock because of sudden aspect change from the target maybe.

The thing is that as soon as I see the target drop below or climb above my scan elevation I loose lock (after about 3 sec [hit memory]) and the contact disappears from the radar-scope. And its not because I get notched.

Quick question. When locking a target in TWS and on AUTO Azimuth centering. Should the radar elevation also follow the target if it dives/climbs? As of now it does not. And i can't adjust my radar elevation manualy either. When in AUTO Azimuth.

So the 2.5.6.45317 Open Beta obviously did not address the [no mid-course guidence] in TWS. Its not mentioned in the changelog. And my testing today confirmed it has not been fixed. But the lofting capability is back now which is good :)

The 2.5.6.45317 Open Beta patch seems to have fixed the lofting issue. But the steering dot is still not working as it should. A bit off topic: but I tryed a lofted shot at a beaming target at 28k 50nm. My missile lofted to 100k alt and actually flew past my target at mach 2.1. The missile did not seem to be tracking though

Yeah I have posted these issues in the bug section. Both the mid-course guidence and steering dot lead bug. Santi871 said the TWS mid-course guidence bug was already reported internally. But I have'nt gotten a confirmation about the steering dot lead bug yet

When i tested the aim-7M the missile would'nt even track the target. And i had good STT lock the whole time. But i guess that would need its own bug post thread.

Good to hear! :) Thx for reply

I have noticed that the steering dot is completely off. My understanding of the purpose of the steering dot is so the pilot can line up the jet for a close to optimal intercept course for the missile at launch. So that the missile can fly "stright" of the rail to get a proper lead on the target with out having to do to big corrections. Correct me if im wrong :) This at the moment is far from the case. Test parameters: 1 target beaming me co-alt (28k) at mach 0.9 In my first test. I put the dot in the center of the ASE. Get a shoot cue. Shoot aim-120C (at 7.5nm) and just after launch the missile has to do a 12 G turn to get the correct intercept course. Note: the steering dot is dead center of the target box. this already tells me something is off. On the second test. I put my nose on a 20 deg lead on the target. Get no shoot cue. Since the steering dot is not even in the heads-up display. Shoot aim-120C (7.5nm). Missile flyes almost straight of the rail to get a proper intercept course on target. All shots was in STT lock. I think its a result of an improper intercept calculationfor the missile in general. On some other testing i did from longer ranges (24nm) on a beaming target. The missile has to keep a continuous turn to intercept the target (target not maneuvering). This bleeds constant energy. In contrast the SD-10 flyes close to straight to intercept a beaming target conserving energy. Side note: The SD-10 also lofts. The aim-120 does not. For reference see this hud tape of a real mig kill from a hornet. Go to the 2:30 minute mark. You can clearly see the steering dot is leading the target way outside the target box. Another side note: Tested the aim-7 as well. they got no guidence at all. just went straight. aka broken atm. steering dot center 8nm 120c.trk steering dot 20 deg lead 8nm 120c.trk steering dot center 8nm aim-7m.trk

Hi. I have tested the aim-120 guidence because i felt something was off. Turns out i was right. In my test i have a target beaming me at mach 0.9. I shoot at around 24nm out. 1. in TWS 24nm missile speed at target mach 0.77 2. in LTWS 24nm missile speed at target mach 1.2 1.When launched in TWS the missile just flies toward the target (where it was at launch). Only when it goes pitbull at about 10nm away does it try to intercept. This results in the missile having to take a high-G turn (tacview shows 18 G's) to correct the lead as it is way behind the target. It obviously misses the target. 2.Then when I launch in LTWS it gets guidence all the way to the target and hits at mach 1.2 So clearly something is not right. Thanks F-18_TWS_AIM120C.trk F-18_LTWS_AIM120C.trk

Yeah it seems weird right. Here is screenshots from tacview from my testing for both mid-course guidence and steering dot lead calc. Note: in all 3 tests I lead the target much more than the steering dot suggests 1.The first one is me fireing at about 21nm in TWS. I lead the target about 14 deg. at launch (Steering dot shows just 2-3 deg. lead). You see the missile taking a pure pursuit of the rail (wich it should'nt) the fly stright intil pitbull and then pull 19.7 G turn to get proper intercept course. It misses ofc. You can see its only at mach 0.56 (way slow) as it misses. 2. The second one I launch in LTWS 21nm out. Leading the target 13 deg. at launch. (steering dot showing again just 2-3 deg lead). But now the missile at least goes semi-straight of the rail and gets mid-course guidence. Hits the target at mach 1.37. A significant diffirence I would say. 3. On the third one I launch in LTWS 5.5nm out. Now having to lead the target about 23 deg. at launch (again the steering dot only showed 4-5 deg lead). So clearly something is not quite right at the moment with radarTWS/aim-120 and lead calculation modeling. I have also noticed that the aim-120 never lofts anymore.

Agree. I remember flying the F-15C years back and at ranges close to r-max the steering dot would lead above the target to get a good loft shot.

Yes i know. It would seem logical that at 11nm the dot would be leading the target more than just 1-2 deg when the target is moving mach .9 beaming. So i had to my self lead the target as much as 23 deg to get a stright of the rail launch Im on 2.5.6 open beta. And in LTWS since TWS dosent provide missile mid-course guidence

So I have done som testing. 1. First of all when engaging bandit in TWS-mode the missile gets no mid-course guidence after launch. The missile turns at the target but then just flyes stright until pitbull. This ofc. results in the missile having to do a max G turn to intercept as it is way of course 90% of the time. Thus using just about all its energy. I'm able to get mid-course guidence in LTWS-mode. But I am under the the impression that it should also get guidence in TWS. 2. The steering dot is not correctly showing the proper lead for a good launch. See the video from a real mig-21 kill around the 2:30 min. mark ( ). You can clearly see the steering dot is way outside the Target-box. In my testing the steering dot stays just about in the center of the target-box. Resulting in the missile has to do a strong correction turn of the rail at launch to get a proper intercept course. Thus again bleeding unnecessary energy. And yes I center the dot and have a shoot cue. 3. Thirdly the aim-120 never seems to loft any more. Should it not loft automatically at close to r-max shots? On the steering dot issue i found that if I pull lead on the target. Which ofc puts the steering dot outside the allowable steering error circle (thus no shoot cue) but stil shoot. I get a much better missile launch (going almost stright of the rail). In the tracks you can se I'm leading the target by 13 to as much as 28 deg to get the proper launch. Hope this is not to hard to fix as it really cuts the aim-120 range almost in half. Oh and I did search in the forum(bug) but did not finde any adressing these issues. Thanks steering dot 120c 13 deg lead 21nm ltws.trk steering dot 120c 13 deg lead 21nm tws.trk steering dot 120c 24 deg lead 11nm.trk