Egyptian F-16s and RWR tones
-
Do the Egyptian F-16s have the same nails and spike tones on the Israeli F-16’s RWR as the Israeli F-16’s themselves? If so, how do you keep your situational awareness up beyond visual range if your RWR has a bunch of 16’s on it, some which may be hostile or friendly - exclusively through AWACS calls or buddy spike replies, or something else? Finally, is there a way to change the RWR tones for hostile F-16s so that the two are differentiated, like in Falcon Online?
Thanks!
-
Welcome to the club…
Awacs? if they are available. Else Vis ID. Some guys use the tgp but I don;t know if this is a real practice.
-
Not sure if they do any more, but assuming that they do, you can still keep reasonably safe.
AWACS calls, buddy spikes, and procedural ID. Anything flying away from me outside 40 miles, dont care about. Anything flying towards me outside 50 miles, or inside 40 miles regardless of direction, I care about. Closest hot group, lock em up, buddy spike or declare to get an idea of ID. Repeat for all hot groups inside 30 miles. Anything changes to be a hot group, add it too. If you start feeling you like you know the ID of all the hot groups, start again on the cold groups. Flying towards your mission area, you should be able to keep at least a 30 miles radius around you that you know the groups are friendlies. Ideally more, out to that 40 mile radius. Any hostiles within 30 miles are a potential threat, but hostiles inside 30 miles and cold, pursued by AI, are not your problem. Hostiles inside 30 miles and hot are a threat, which you need to react to. If there are AI flights around like F-15s, you might be able to drag the threat group into them. If there are not, or you just want the action, you could turn hot and try to get some missiles off onto the hostile group.
Procedural, anything flying towards me with 800 knots + closure is automatically suspect; if they are the closest hostile, start getting into a position to shoot. If they are the closest bogey, do it anyway, but hold fire until you get a better ID. Anything flying away from me is not an immediate threat, so worry about them when/if they turn hot. Anything that originated over enemy territory is automatically suspect, but is not automatically hostile. If they get within 30 miles, lock them up for raygun, but get confirmation on their ID. I once started to engage a threat I watched on radar climbing up and away from an enemy airfield… only to discover I was formating on a friendly F-16 with empty bomb racks.
Cant wait to play through ITO on 4.33, Ive still been immersed in KTO. Would be good to hear if the Egyptian birds have the same RWR tones.
-
RWR works by receiving radar emissions, determine direction, RF characteristics and strength of signal.
based on the characteristics it determines the radar type (not threat type). it then based on the radar type displays an estimated threat type and distance based on known radar transmission strength.the sound the system makes is usually a mimic of the “sound” the radar emissions do, pitch changes on the frequency of the radar and stuff like that.
so if two planes have the same type of radar they will sound the same, and show the same on RWR.
even more, several types of aircraft can be interchanged. SU-27 and Mig-29 for example, cannot be for the most part determined in 100% serenity.Falcon does it differently,
in flight sims, you always know everything. you then just mask away things which are “out of bounds”. it is actually very hard to introduce real-world errors into the simulator.
So in flight sims, you know what type of aircraft you are facing, and which radar he has. which in turn has a “sound file” and “icon number” to show on RWR.
so you can clone an F-16 radar, change the sound and the icon number (to say mig-29) then attach it to a specific F-16 variant in the game. heck with the correct DB edit, I can make a mig-21 show up like a AAA gun. -
Its not so hard to make such errors. The program knows all… but not every method needs to know all. This would be most evident in programming a full EW overhaul for BMS.
-
Its not so hard to make such errors. The program knows all… but not every method needs to know all. This would be most evident in programming a full EW overhaul for BMS.
random is a very hard thing to code in a reliable and realistic way. in some cases you have “double trouble” - take the HARM for example.
seeker has its own precision error, say 1 degree. the closer you are to the target, the closer that 1 degree circle will be to the target (as from 10nm it’s a pretty big circle). so you have to take that into account when deciding there the missile with “think” the target is (as it knows exact location at all times in game).
then let’s assume radar turns off. missile then needs to go on alst known position (which may or may not be anywhere near the target). then you get INS drift, that is changing from system to system. between types and between individual systems. so one missile will have the same drift tolerances as another of the same type, but it doesn’t mean in drifts the same, one drifts up and north, the other down and west, both at different rates.
now you need to try and figure out where the missile “thinks” it is and how it would steer to where it thinks the target is located. both can be quite far away from where the missile and the target are actually located in the falcon world. which the game has a really hard time to “forget”.that is the reason that up untill 4.32, HARM in POS mode were super effective. and in 4.33 they are Meh… INS drift, if target will not light up in time for the missile to get a fix. it will probably miss.
-
Perhaps its my lack of programming Falcon, but from a programming viewpoint that does not seem particularly complicated, just time consuming, to code.