TAW_Blaze

We'll have it with advanced systems modeling, provided it exists on the real plane. AKA DCS:F15C, DCS:SU-27, and whatnot. Long way to go buddy. FC4 is prolly not happening.

It wouldn't matter as much as you think. BVR is not really about defending launches that you spotted. If you show me a VSD rundown of what's going on I can easily pinpoint where he's most likely going to fire. Although whether he fired or not doesn't matter at that point, if he didn't fire there but fired from a different position it'll have worse parameters and I might even just outright ignore it because it has close to zero pk.

Oh yes, in some cases I've had missiles hit the target with a 10 second delay if not more. Very difficult to judge if you need to fire another one.

Except we're armed with 120C5s and soon AIM-9Xs aswell. Where did the logic go..

MPRF range is 8nm. TTA/TTI is just an estimation based on the situation at the moment of launch. It doesn't account for maneuvers post launch. DLZ is also an estimation, a very broken one at that currently ingame.

If you've seen some drag charts for DCS missiles this is not so surprising. I doubt it. You could be higher up if the range is not extremely short (such as 20km or less), but it might be useful to fire in a dive in that case. It's a matter of range, your speed, his speed, your altitude, his altitude, both aspects, and another set of things. Saying the time when you fired is essentially useless especially because you didn't describe any of the above mentioned. Well, anything inside the gimbal will work, if you go closer to the gimbals it might lose lock. If you dive too hard the radar might not be able to point at the target because of physical limits. Other than that, of course you want to be below the target, the russian radars are nowhere as good in a look down situation. How much you're below him doesn't matter as long as he's within the radar's physical limits (probably advisable to keep him from being too close to the limits, if he maneuvers you'll lose him). I haven't seen your test so I can't be sure but I've seen the AI do some pretty sick notches and they'll do it quite reliably if you're the first guy shooting at them. If that's the case, no wonder it'll go for the chaff. It isn't.

VSD top left corner, given in TAS, according to the manual. Might want to read it :)

It works the exact same in DCS except for a few parameters, such as the launch ranges. There's a reason for that. You can't learn air combat by watching tutorials. Not surprising at all, most of the friendly fire in DCS is done by people who haven't even bothered to read the manual. For the time being this can't be done. The auidence is simply not big enough. I mean the part of it that actually reads the manual.

Being zoomed out is ok, just zoom in when you have to. Planes under certain circumstances are VERY hard to see even if you know where they are. That means, being able to comfortably zoom in/out while maneuvering and blacking out is extremely important. I personally use the slider on my TMW throttle currently.

Well, to be fair, many of us asked about this, I don't even remember how many times. No response was given, whatsoever. Thanks anyway, sorry for being a bit inconvenient.

It doesn't matter anyway because trim is worthless currently. No point trying to trim it out it either results in the opposite of what you want or it just doesn't do enough. It needs to be more detailed, a trim function that behaves like a massive kick on the control surface is not very useful.

I'm wondering why you're constantly leaned to the right and then looking at the left. You should lean back on your seat, recenter, then zoom in a bit, that lets you see the entire HUD.

Nice to hear from you, I'll be there. Thanks!

1) AMRAAMs are not so difficult to spot visually when the motor is burning at that range. Especially when you know where to look. Below is why that can be easy: 2) He probably knew where it was coming from since the russian RWR is very accurate at this. IIRC it'll also shows pretty well where the missile is. 3) He probably flew straight because he knew where the missile was. I'll give you the benefit of the doubt that he /might/ have gotten lucky, but it's not too likely. Honestly, as long as your blaming your mistakes on luck you'll be stuck an awful pilot. That's just how it works. There's n+1 things that he could have done to counter the notch but he did none of it, what is the real point of blaming it on something else? In the end it doesn't matter if he got lucky or not, the point is if you're learning something or not. Making mistakes on top of mistakes and then blaming it all on luck just doesn't cut it.

The plane seems to go into an aileron spin even with very light stick movement. This happens mostly at high altitude, but can also be observed at lower altitudes in some situations. From what I've heard from people that know this better than me, rudder authority is not strong enough and this could be one of the key things behind this behaviour. I'm not sure how it should work but I imagine if the rudder had as strong as an effect as it should the ARI would be more effective counteracting this, however I have no idea what the result should be. From my personal experience these spins happen mostly when you use pitch and roll at the same time. ie. you just banked the plane and you start pulling before the bank stabilized.

On top of that, that video provides nothing useful. Literally no information given. No stick input is recorded, no speed data is given, just to mention a few things.

Oh look, I've seen videos on youtube about an aircraft flying. Unfortunately that doesn't make you a subject matter expert. I know the problems I know because I talked to people who have actual knowledge in this area, not because I believe in a bunch random stuff that are based on YT videos and another set of misbeliefs.

You believe in this [redacted] that a plane should fly like this or that. You don't even know what's a problem and what's not. Take this analogy - when the PFM was out in beta everyone reported that the RPM is bugged and is stuck at 96 regardless of afterburner. Then they were told this is how it works in real life. We're in the exact same boat, again.

Maybe you should ask and wait for someone competent to respond before breaking down in rage? Btw don't expect it to be anything like it was pre PFM. There are problems but even if they get fixed eventually it might still be a lot harder to fly the plane than you'd think. I'm not a pilot either but 'ermagerd this can't be realistic' is not an argument.

PFM is W.I.P. I know atleast 2 different problems that could cause the issue, and one of those is most likely the main one. When will they get fixed? No idea.

Creating a clickable cockpit is piss easy. Creating the systems that work behind the buttons is the difficult part.

If it's so easy why don't you do it yourself. I wouldn't expect to see a functional MFD on the F-15C before advanced systems modeling.

Of course you can, however a number of things can be said: 1) AMRAAM in DCS doesn't get any support from your lock post pitbull, this is not true at all IRL. 2) AMRAAM in DCS doesn't fly to last known intercept point once losing lock, this is also not true at all IRL. Instead it'll go ballistic. Common sense would indicate to guide to last known intercept point and then detonate. 3) AMRAAM in DCS seems to never detonate when guidance is lost due to chaff (well, this is most definitely a result of the two above). In this scenario you should: A) be in STT, TWS will lose him due to the lack of radar memory model B) fire an AIM-7/9, I'd recommend the latter because the Sparrow can give away your position and result in you getting spammed to death from a burning wreck. Simulation eh.. Other than that, he used the game mechanics pretty well, you didn't. :)

N O T C H A very good one at that.