TAW_Blaze

Can't wait for this.. it's crucial to building the right SA.

There was already a thread in some random section but it got lost in the past months.. I'm curious whether the amount of cockpit shakiness we have is realistic or not. To me it feels very overdone but I'm no expert. It's particularly annoying when fighting guns, it makes aiming far more difficult. Can anyone comment? I also don't recall having similar features in any other aircraft, although I don't fly them often. Is it a testbed for now?

Even if R-27R was a bit better, the MATRA is much closer to the performance of an ER than a R or AIM7. It accelerates better and has a much higher top speed. Whether this is realistic or not I don't know, but if you're trying to outduel a MATRA in a fair fight with 27R or AIM7 you're just getting yourself killed. What you can do instead is bait out his shots since he only has 2. Notching also works pretty well against the baguette radar.

Actually almost every squad in SATAL is using J-11s or Su-27s. Most of them not exclusively, but there are a lot of them. 77 having the same range as a 73 is an over exaggeration, while it has poor range it is quite deadly within 5 miles. 27R is just overall garbage especially when it has to turn. If someone thinks they can fight a fair fight 27R vs AIM7 obviously he will lose unless the Eagle driver is an idiot. If you have first shot at short ranges with 27R you can win but this needs to be setup right by notching or hiding. No doubt there's a lot of talent in the 51st but mostly it's down to dedication and knowledge. I see a lot of dedicated people flying all the time and I also see a lot of people who know quite a lot but can't fly enough. These 2 things rarely meet and what's even less common is these kind of people being in the same group. Sadly in my experience since Hornet release the general A2A quality has gone downhill outside tournament play.. If you're flying on 80s loadout servers you might want to load 73s instead. Those things are insane when fired near rear aspect. In any case I'm not seeing any facts how the 27R is not meeting realistic performance. Manufacturer max range shot supersonic at 40kft or higher does not translate into how it performs in DCS. Not that in similar scenario the missile can reach the marketing numbers. But every missile is broken so this is no surprise. The problematic part is that russian radar guided missiles seem to be more prone to stupid guidance issues (i.e. chaff resistance). If you want to have any hope of helping ED improve the missiles, provide them data instead of creating a thread every month that this or that missile sucks and it's unfair.

There are people flying regularly on the 104th server who kill Eagles,Hornets and whatever blue has with F-5s. All missiles are broken. Some more than others. But there is no bias. The only joke here is this thread. Looks like you don't even have any more arguments to add so instead you went for a weak attempt at offending me.

No. SATAL is where some of the best squadrons compete with each other. Flying on a public server is like sleepwalking compared to SATAL / SATAC. You can fly around in an F-5 with 2x AIM-9P5 which is one the worst missiles in game and still kill 120C equipped F-15Cs and Flankers. Ask any of the red guys going around in the 104th. Actually yes. It was alternating R27ER and R27R vs AIM7 between rounds. So one round Eagle has the advantage with AIM7 vs R27R, the next is AIM7 VS 27ER and Flanker has the advantage.

SATAL begs to differ. Also last year SATAC winner 51st flies all flankers.

The better lesson to learn is unless you're afraid to bruise your ego it's better to ask questions so you get your facts straight sooner. :)

shh, that only happened once :)

You win BVR fights by setting yourself up to survive. Situational awareness (SA) is the biggest factor, most people I see online commit into a fight and get killed by someone who they never knew was there. Before you take the fight you should try to understand how many friendlies you have, where they are relative to you and whether you can count on them to do anything at all (usually not). What's equally important is to keep track of where bandits are, which ones are dangerous, and where the fight is taking place. If you're over enemy ground outnumbered it's better to extend out than to try and fight it out while the other bandits will be a step ahead at collapsing on you. You can also help this by choosing the direction you fight. At the expense of not flying straight at the enemy you can set yourself up to have a clear direction of engagement and also a clear window where you can get out if necessary. Generally i.e. in an F-15 you want to start thinking of gettig out once you're below 8k lbs of fuel and latest at 6k. This will ensure you can burn away at M1.5+ with a clean jet that nobody will be able to follow and if your exit window was set up correctly you should have no issues getting home. Make no mistake, people online will chase you full gate for 10 minutes STT locked with no regard to their surroundings or their ability to ever go home. The other typical mistake is going tunnelvision on far bandits ( > 30 miles) and overpreparing your fight. Your priority is searching for things right in front of you where they can pose a lethal threat by hiding extending, notching or behind terrain. Maintain SA of far bandits but focus on this and very often you'll find people hiding right under your nose, whether by accident or by good teamwork does not matter much. Even inside 20 miles of the bandit it can be crucial to keep searching for others if you're confident enough you can get back to your original target in time. The duel is just a small part of the work. What I would highlight here is that ARH fights you can usually get away clean and feel quite safe. SARH duels on the other hand are usually a dance to the death and it's not uncommon that both of you will die. If you're running around with SARH I would generally not recommend taking fair fights, especially if you're not experienced. Try to ambush people, have energetic superiority, etc. Beyond all the fighting and tactics what's one of the most important things is to be able to quickly realize what's going on and react on it. Knowing how far you can push it will help you immediately decide whether you can continue fighting in a given scenario or it's done but you can still get out of there if you go for it. Of course if you're too close already then the decision is already made and you're going to have to fight it out. In the end it all comes from experience. Most important of all, use Tacview.

Considering the antenna characterstics this makes sense, thanks for explaining. I was working with omnidirectional microphones where this wasn't really an issue :)

I was thinking about this after I posted too. Working on a 2d field with 3 or more antennas instead of 3d would save a lot of resources while not really affecting the results from the perspective of the end user. Also like you say if even that requires too much resources then the approach of 2 strongest receivers would work I guess. Normally 2 receivers cannot determine a 2d direction of source, but using the stronger signals you could narrow down the field, which would solve the ambiguity problem. I'm not questioning the accuracy of your simulation as I'm sure it'll be great. I'm merely interested in the background of system design. Thanks for the link, that was an interesting read.

This is weird.. why are they using the signals from only 2 of the antennas? The only reason I can think of is the airframe blocking reception at certain angles. Normally you can reconstruct 3d geometry with 4 receivers using advanced correlation or equivalent techniques. I'm no expert of RF processing but I did exactly this with audio signals and it works just fine. I would expect with RF the ambient noise is not as much of a bitch to deal with and compressed signals should be easier to detect. I'm not all too familiar with ground based radars but most airborne mechanical doppler radars use chirping and/or various compressing techniques which should make it easier to detect them. Now doing this against an ESA is a different topic.. :) The error issue is there like you said, what I found is that it's especially high when the source direction is lined up with 2 receivers.

With 20/20 hindsight and total ignorance of 70s technology such a design flaw is very surprising. They must have had the deflection information for A/P features so I don't understand why it couldn't be used for this too.

This is not something new, I've had similar experiences back in 2.0 and also 1.5 but I'm reporting it here since it happen in OB just now. I was flying around on our server and I got desynced for 5 minutes continuously. During this time everyone else was frozen and floating in 1 spot in the air, and nothing was answering radio calls. After about 5 minutes I recieved some incoherent launch warnings (from a J11 about ~ 40 miles away according to RWR), turned around to extend and died a few seconds later. tacview and trk in the zip https://megashare.megahd.com.br/5090de805b4b6485c894cdfe2e23b80c

Boresight works somewhat, but as soon as you pull the target outside the circle it throws away the lock which makes no sense at all. Hopefully that'll be fixed soon :)

Can a mod move this thread to the flaming cliffs / f15 area? It doesn't belong here..

Pretty sure you're supposed to be able to slew low azimuth RWS. But currently it's not implemented AFAIK. Normally it would follow your TDC.

No idea how people spot things 10 nm away. I'm running 1440p on a 27" with TrackIR and I sit about 50 cm from the screen and I can barely spot other fighters 3-4 miles away at best without zooming in or literally knowing where to look. Hell I even fly with more default zoom than most poeple (i.e. in F-15C my usual setup is that I don't see past the canopy bow on the sides). Missile launches I can usually spot but that's a different story :)

If you're in an Eagle generally you want to finish the fight before the merge happens at all cost. In many cases if you push a merge against a baguette he will turn it into scissors which the 15 will lose pretty much all the time. In my experience the Mirage is stronger at low speeds, so you don't want to go there. If you keep the fight level and around corner speed the Eagle tends to win in the long run if you were neutral in the beginning. In a neutral merge if you turn on time and you're at the right speed you won't be at a disadvantage. I found out of plane maneuvers are difficult to counter since the other guy handles better at the lower speed regime which you will unavoidably enter while maneuvering nose high. In offensive merges the biggest issue I have is to be at the right speed when you merge and if you're not you'll either end up in an overshoot or on the wrong end of a non counterable vertical move (which is never fun). This happens quite a lot in SARH fights when you're pushing either too fast or too slow (trying to dodge those magics) and merge unprepared because everything you threw at him missed.

Yesterday I fixed it with some unplugging but now it's bugged again. :doh:

Pretty much, not many people used the 7 in the Eagle and now they are all suddenly forced to use it with a disfunctional radar which makes the already not so stellar performance exponentially worse. Whether the kinematic / guidance performance of the missile itself is accurate or not is a different debate.

Currently you have 1 PRF mode (not MED..) and the radar will lose lock every other second if either your target or you're maneuvering. Not a shocker it'll go ballistic all the time.

I agree I think it's way too overdone. Not that I'm an expert but it seems just off the charts.

I ran into a weird problem. After running the script I generally had the virtual controller and all the other devices also recognized in DCS. This way I could mix simple binds with scripts and it was quite flexible. However every now and then it was bugging out so the devices would disappear and only the virtual controller stays, which lead to the point where in the past 1,5h I was completely unable to get them back and the virtual controller is limited to 32 buttons etc. not to mention the different devices also overlap (i.e both MFDs) and some of the buttons don't even seem to exist. Not cool. I tried configuring the devices as excluded, enabled, filtered and also flat out excluding them from the script but does nothing. :helpsmilie: