blkspade

Yeah, the problem is there is apparently no point at which they aren't flowing at the same time.

You just aren't supposed to go head-on BVR vs an F-15. There are things that you can get away with, that will work against the more practiced Eagle driver on occasion, but they are largely based on bugs/exploits. Ambush tactics are really the best way to go, as opposed to having a competent wingman and good communication. Firing early/first does no good if you aren't in an advantageous position. Given the amount of info that can be extrapolated from the radar and tews, the Eagle driver can easily discern the level of urgency. Honestly the AFM gets me killed more often than anything else lately.

IDK. A switch which has the potential to directly effect flight characteristics/performance seems like it would have more relevance as a PFM addition. Certainly more so than the fuel tank display selector that we have for whatever reason.

I think most are willing to accept the effectiveness of the notch. The real frustration comes from those who defeat AMRAAMs head-on, and continue to press when they should technically be at a disadvantage. I actually have a better chance at killing them with the Sparrow, or sidewinder even if things get really sketchy.

Though unless they are making a massive step backwards, it may be safe to assume that sim will remain dual threaded. Its also possible that the jump to the Dx11 API will offer some multi-threaded rendering advantages.

Because they both have the same AFM, they technically 'fly' exactly alike. The clickable cockpit grants you more realistic/detailed control over the cockpit instruments/avionics, as well as the C model having more up to date avionics.

An AMD 8-core setup would probably be the best way to go for a cost effective VM setup.

It should be noted that some applications are actually hindered by having hyper threading on. Its probably largely irrelevant for DCS however, since it only uses 2 threads with the 2nd being for audio.

You can reassign TrackIR-Z to zoom. This give you the ability to zoom, by leaning into the screen.

The in game behavior with ECM is quite inconsistent. I've gotten HOJ launch warnings from aircraft that are quite noticeably too far away on the RWR.

If you're moving faster than like 80 knots toward any fighter they will pick you up on radar. I see choppers all the time on radar in the eagle. They are pretty easy to to identify even before the NCTR kicks in just by seeing how slow they are flying. If you're really slow or in a hover you won't be seen.

I haven't looked at, but I assumed this was from earlier where I was sure I only got one kill on you.

The 120 the got you was fired at relatively close range, though I've seen you routinely dodge 6-8nm shots plenty.

As far as lofting goes, I have noticed that sometimes the first missile off the rail will loft while the 2nd one won't. This seems to happen shooting on a single target, with some minimal missile separation. At least that is the impression I've gotten from the tacview tracks in singe player.

Did something change in the modelling between these aircraft, or did I get better? I used to have the hardest time getting on the AI dora's 6 and if I did he'd often climb away if I did. Not only can I get back there generally easier, but I'm finding myself frequently overtaking him in the climb.

Keep in mind that there is a warm-up period of 15-20 seconds before the ECM is actually on. As such using it after the shot will only be effective if it is an Rmax shot well outside of burn-through range. Only AI and noob pilots are likely to take shots like this under the current missile modeling. Versus an eagle you'll likely be getting tws shots anyway, and thus no warning.

Even if it is 'ancient', your core 2 duo should still be 64-bit compatible. Though an OS upgrade to 64-bit would only be worthwhile if the computer already has at least 4GB. It probably wouldn't be economically feasible to invest in additional DDR2 if the system has only 2-3GB of ram. Although 2GB sticks/4gb kits are somewhat cheap.

Firstly you'll want to be taking out those bmps or any vehicles that pose the most threat to you at range with the mavericks. At whatever altitude you're at you'll want to fire them while level anyway. You'll be lighter after having fired them as well. As far as the nose pitching down, you'll have to use trim (nose up) to negate that. Also you don't have to fly right into the target area if you would like to get to a specific altitude first. The unit for speed in US jets is knots.

The MiG-31's R-33 is also way difficult to avoid. What I'd suggest is that you just deny them the long shot. Basically turn away or notch immediately and spool ECM. AI doesn't fire HOJ any more and will have to wait until burn through. That leaves you free to close the gap and engage accordingly. That at least works very well in the F-15 mission versus the MiG-31s.

He's not wrong you know. The sim is buggy and sadly still running on DX9. I've been a fan of the ED sims since LoMac. I have seen some of the same issues get transferred forward, and ask myself why is this STILL happening. While I wasn't (still not) a big of A-G, I was excited when they were talking about moving to DX11, back before release of the A-10C. I would have bought the A-10C day one if some DX9 api related crap wasn't going to follow the sim. Instead I picked it up much later, on sale, and solely as a precursor to to the F-18C. I still more or less love the potential of DCS. It doesn't take a wealth of time to run into some of the apparent current flaws in the sim now. I accept them for what they are as I see progress is being made, but seemingly have to attach a disclaimer to any conversation with friends about them picking it up.

The FM in both of those stands for Flight Model, which has basically nothing to do with the cockpit.

Its funny that someone else has noticed this. I was just looking into info about the F-15's handling a few days ago and came across a rather lengthy document of a report on the eagle's wing rock behavior. It clearly missing in the PFM, and I'm guessing the spin is a very early attempt at implementing it. For now it at least helps to have a little curve in the pitch and some dead zone in the roll just to cancel out the little incidental lateral stick while pulling.

As you've pointed out, the technology is there. Also as you may have noticed, it generally sucks compared to the way natural point does it. Its obviously much less work on the back end to look for little moving IR lights, as opposed to finding a human head and filtering it out from the background.

It should also be added, that if you decide to use IRST you should know that it does not IFF. So if you aren't absolutely sure that what it picks up is an enemy, you should check with your radar before firing.

Yeah, As I've pointed out before a graphical glitch tends to manifest itself as something not being rendered, or some random anomalous additions that clearly shouldn't be there. How someone would come to the conclusion that something that is rendered essentially in perfect form is a glitch kind of baffles me.