pr1malr8ge

Cannot take the time to read each post in this.. How ever I have a profile loaded on the downloads of eagledynamics. With that being said. I think personaly it is much easier to configure the controls your self. Mainly because you have to think of what you want to do. Therefor when you're flying you have a memory of what you placed where vs trying to look through images to figure where someone else put something.

Ha, well I've been flying the flanker some more and I can tell you that it is one finiky bird. I grasp the basic concept but trying to convert speed and altitude on the fly is proving difficult. The one thing I can say that is awesome and crap at the same time would be the SPO.. I like the fact that it can give me a borderline range of threat mainly impending missile. But the lack of what is illuminating me is a bit screwball. So with that I would say the f15 is the better choice to learn Bcm and ACM then move to the flanker.

there hasnt been an update in some time now.

So, I will give me input and this is based on me ONLY Flying the f15. You need to figure out what exactly you want to do.[assuming you're planning on flying multiplayer] 1. Lonewolf or Teamspeak wingman. With this subset it is hard to to make a choice. but since most lone wolfers are hide and go seek type flyers the Flanker i.m.h.o would be the better choice since it will allow passive searching with the EOS. That and it's better low and slow turn fighting. If you plan on being on Teamspeak. The f15 imho is a little better with it's flight char. a lot more people fly the f15 in groups. 2. BVR or WVR or HideNgoSeak BVR well again the f15. WVR well this is probably tied with the HideNgoSeak more often then naught. To me again the Flanker with its better turning, lower speed capabilities, and EOS/HMC/ and HBO abilities. 3. Flight cueing. Some people don't think of this. But for most Americans learning the Metric system can be a bit daunting. I for one hate and love it at the same time [i hate it in the aeronautical sense ]. If you cannot get used to Metric then the F15. This is one of the main reasons I do not fly the flanker. I love the bird think it's absolutely gorgeous. But the cockpit just makes me want to hurl. [that and the baby blue might as well be baby poo green if you know what I mean] But hey man to each his own and best of luck with what ever you choose.

This is all fine an dandy. as with anything it is speculation. How ever if say this is IFF only it still would be safe to assume that it can easily be observed as a direct ping to the aircraft being identified. Therefor it is just as easy for the transponder in the f15 to recognize it is being actively painted on that frq and initiate a warning on the Threat display. To add to this, saying it can't is just the same as saying you cannot identify radar either. Both are radio transmissions and both can be displayed with an approximation to relative bearing to the nose. High/low/middle and everything else can be seen. If you argue it cannot be. Then please explain how they can tell the difference between different radars mig 29, f15, f14, etc. etc. The answer is simple stolen/defected/allied aircraft brought in for recording. With that is is very safe to assume the IFF system was also recorded. Thus pretty easy to program and link the IFF system into the Threat Display of those known signals. Even then it actually probably does not even have to be tied to the IFF. If you know the frequency and frequency modulation used the RWR could see it also with out needing the IFF transponders input. For the sake of this game being simplified systems having the systems do that should not be in game.

Umm you just confirmed exactly what I've been saying. It is multiple systems linked together. Sorry that I did not distinguish that I'm talking about the output display for the pilot along with audible tones. and smoke trail for the most part would be the same as an exhaust plume. you knew what I was getting at. again I still have never said the RWR for radar pickup side was looking for an IFF signal. This comes back to the fact the IFF transponder is setup to look at those frequencies. If it detects a signal that is not friendly it should be able to display that as a threat just the same as the MLWS RWR does. For further reference what I'm going to state TWD [Threat warning display] Since I do not know its exact name. This would be the nice round circle that shows threats in the cockpit.

Then what you're saying is that the A10c's rwr is wrong and cannot display IR or deduce missile launch via smoke trails? Those last I checked are not High Frq waves. You can stop arguing high vs low frequency. Because that is not part of whats going on and none of it is Low frequency. IFF is a known narrow band of high frequency with an encoded data package not just some random generated signal. Before you go off about the above quote saying its the transponder ect.ect. this is not what I'm getting at. I'm saying the two systems can be linked just like the A10s system with its IR and Smoke detection systems. and last I checked an non matching/recognized IFF interrogation would be a THREAT. Considering if something has the capability to initiate IFF it then it would be a pretty good assumption it has the ability to lock on and attack. To say it's not a threat well then.....[shrugs]

Adding to this take the a10c it's RWR has I/R and smoke detection these systems would be as part of a cluster. One for Radar, one for IR and one for smoke each talking to the RWR. again I see no reason the IFF could not be part of that cluster. as said. Only thing that would keep that from happening would be Programming or lack of a physical datalink.

does not matter. If the IFF system registers an active IFF why can it not tell the RWR there was an active signal that does not match its own thus to give a warning. There is no outside reason the two systems cannot talk to each other. I'm not saying they do[in hindsight why on earth would they not] but arguing wave lengths ect isn't the reason they don't. The only reason that would keep them from teaming would be lack of programming and or a physical datalink between the two systems. [again why on earth would they not be. Stupid imho if they are not in real world use.]

Ok, sorry but I have a degree in mechanical engineering. [not exactly in this field but it means I'm not exactly stupid] This is a game with simplified systems[in regards to the FC3 aircraft]. Its pretty easy to conclude if the radar is turned on it will turn the entire system on Both TX and RX. To say it is not a bug when the RWR shows no warning because you think by turning on a simplified system only turns on IFF but manages to SHOW everything else in the radar's FOV is a bit absurd. Second I never said the RWR would trigger a known radar source and display it as a 29. There is no reason it couldn't show up as (U)nknown. Everyone keeps denoting the IFF being on a different frequency band then a radar is some type of magical difference is plain hogwash. They are both a frequency wave that there is an antenna to pick up its signature. It should be perfectly capable of denoting a generalized direction to the emitting source.

Never had that happen that I am aware of. how did you come about this conclusion?

No if you have someone locked in EOS, then turn on radar to IFF them they show no lock nor any spike on the rwr.. From what someone has recently just said that it will not even show up if you leave the radar on so long as you maintain a thermal lock via EOS. If the latter part of keeping radar on with an eos lock and NO spike is show on RWR this is a huge bug that should be immediately remedied.

Ok, so [from what Im gathering] the IFF antenna for both TX/RX is only in the nose. So it is safe to conclude that anything directly behind the plane cannot see or be seen by the IFF since it would have to travel through the airframe/engine/etc.? I would have thought that just like the RWR it would have external antana's on key pickup points.

One would think even if the the radar could strictly only transmit IFF that the receiving plane would generate an unknown spike that is received an invalid IFF interrogation. You would also suspect the same receivers on the plane for the IFF are also for the RWR for weight and simplicity. Thus the two are linked and if it's able to trigger iff it to also should trigger at the very least an unknown threat. [id still think unless it was a great distance would be able to logic the type]

It is passive for the most part on the active searching aircraft as there is no IFF signal being sent out [unless that aircraft is being pinged by another aircraft]. The aircraft being pinged detects the radiation and then sends back an IFF encrypted signal. If that signal matches the code on the active search aircraft then the HUD will display the target on the hud as friendly. While this is all done in an extremely short amount of time in the magnitude of .5-1 seconds, it is not exactly instantaneous. [sorry just re-read your reply and I thought you typed something different] What I am trying to get at is, that in the RU planes there are players turning on and off their radar so fast that "targeted" aircraft's TEWS does not register the radiation and remains silent. In my opinion if the radar is not on long enough for TEWS to register it is not on long enough for IFF to register and respond either. Therefor everything on their radar scope should show enemy. I also side tracked that with the fact that turning the radar on and then off [which I am assuming is in the magnitude of 1 second or less] should not even be long enough to actively show anything on the radar scope. That's like turning a monitor on and back off in that time and have the picture while on for that .5 second be bright and readable. To add, when you claimed a visual IFF, I know that did not happen. TacView is a wonderful thing for deciphering what happened afterwords.

I've been killed several times by RU planes shooting via EOS. My complaint is every time I ask they claim to have looked at me via radar to confirm IFF. The issue I have is in the f15 this does not show up on TEWS. IMHO there is no way this will not show up on TEWS and second it would not be on long enough in the RU bird to actually determine IFF. Iff is an interrogation based system. If the TEWS cannot pick up and show the signal therefor the IFF system would not either and there for would not respond. Thus everything shown on the RU plane should show enemy. I also do not believe in that time frame the radar is even be able to function at least not in a perspective of showing on the HUD. Reguardless IMHO if the IFF is able see it and to respond it should also show on TEWS.

What I suggest is for you to not consider playing Multiplayer for a while. Play some instant action games on easy and maybe turn on Symbles so you can see opponents well before WVR, and turn on god mode till you get the hang of when launching works and under stand things a bit more. Then turn them off.. Even when you can kick the AI's rear going into multiplayer is a whole different ball game. Don't get discouraged. IMHO the number 1 mistake new players do is think they can just go straight into a fight and kill.. Your number 1 priority is to take off and land. Don't push against opponents. Keep your distance stay in your own sides same cover and make them push to you. Fire your missiles at 12nm and turn and run. if you don't get a kill O well. stay alive land re-arm and keep at it. Things will start to click, and you will start getting kills. A2A fighting is as much of an art as it is science. You can do everything right and still get killed. you can do everything wrong against an opponent who is doing everything right and still kill them albeit very unlikely. Just remember Let your opponent bring the fight to you, That gives you the Highest odds of survival and of making a kill. There isn't magical eyes, or hacking going on.. The main thing going on is you just don't understand the concepts of whats going on. Here is a good place to start http://flankertraining.com/ironhand/a2a.htm

If you shut down the engines on purpose you can only restart them with the engine start key which is exactly how you start them on the ground. From what I understand the f15 has all the full systems like the a10c except for the control-ability. So doing an air start via motoring isn't possible from what I know. How ever feel free to try it. You would need the dead engine at idle and a good decent to rotor the engine to 60%. BTW if your engine was shut down because of damage/fuel exhaustion it will not restart with out landing and repairing. If it shut down due to fuel starvation because you flew inverted too long then it should restart but you need to remember it has to cool down first.

Umm, from what I understand is that the f15s rwr is as other have mentioned is a measure of signal strength and highest probable threat. There for as I would understand, that if say you're head on with a bandit at the same altitude and another bandit is closer and at a different altitude but cornering away [i.e. his radar is only scanning you on its outer gimbles] that spike of the closer bandit would show up behind the further bandits spike due to signal strength and threat coloration. Thus making it impossible to correlate any distance via the RWR. I might be wrong but that would be my take.

They were not in AB or atleast not sure, it was a dead head on. I launched with in visual range 2.5nm at max, seaker had tone and launch auth verified by lights on canopy. I saw no flares and nor was flares shown on tac view. each time the piliot had no clue it was coming and did not manuever untill I was right next to them as I was just watching with my jaw to the floor in disbelief no splash. I'll try and find the trac and tac view files.

Any known issues with head on 2.5nm head on shots with closer rate of 1200kts failing to hit? I had two example of this happen to me. Both resulted in my death. both were in enemy territory both were f15vs f15 and both were "surprise" launches by me. Both times this happened I was RTB and found an enemy f15 RTB and silent. Once I picked up the enemy I went radar off full AB and locked only with the aim 9 with a 1200+ kts closer speed I launched at 2.5nm just in visual and both missiles missed in both cases resulting in my having way to much speed to merge, of course my blood thirst got the best of me and I tried to merge rather then using my speed to extend and run. None the less, I was after talking to the opposing bandit both claimed they flared which after reviewing tac view neither did and the missile shows it went straight through the enemy craft.