ZaltysZ

Are you mixing the course with bearing? The bearing arrow shows where location point (i.e. waypoint) is. The course tells from what direction you are supposed to approach that location point.

PATH mode is supposed to keep your aircraft on flight path, which is defined as line between your aircraft and its TVV (total velocity vector) upon activation of AP. It does not keep altitude or course directly, and can mess up if flight parameters change drastically during its operation: like in prolonged or too steep ascends/descends, bank angles nearing 10 degrees. It is good tool when you have to take a dip into MFDs while climbing, but it is dangerous to leave aircraft unattended on it. If you want to go for glass of water, trim your aircraft and put it on ALT/HDG mode or bank it and put on ALT mode.

or just shoot at things from 50-100m. :)

and "I saw once on History Channel..."

Save it for time when Spit ad BF will come out. MP crowd will surely find lots of flaws which prevent them getting victories. :pilotfly:

HEI: around 2g of explosives + around 2g of incendiary charge. MinenG: around 18g of explosives.

That switch turns on/off the gyros of sight now instead of power for bulb.

Almost. Sometimes simple automated reduction is enough, but sometimes such reduction creates a "mutant", which has to be corrected manually without adding too much details (increasing poly count) - it takes time.

AMDs with VCE (http://en.wikipedia.org/wiki/Video_Codec_Engine) should be able to do the same what NVIDIA >= 6xx cards do: use built in H.264 codec to do high performance screen capturing. Unfortunately, there is still no utility like ShadowPlay for AMDs, but I think new version of RadeonPro will have new functions for this. Some users have tried to achieve capturing in their own way:

I use NVIDIA Shadow Play (available for 6xx cards and newer). It is still immature, but works well enough. In fact, recording is always on for my MP flights as there is not much performance decrease (1-2FPS) The tricky part is recording the TS3 chatter. ShadowPlay records everything you hear, but it can also record your mic. Unfortunately, it is unacceptable the way it does. It does not have controls to change mic input gain, reduce echoes and noise, so your own voice usually sound very bad (too load, too silent, too much hiss and etc.) when compared how other people sound on TS3. I use specific approach for recording voices: I make Shadow Play record only in-game (what I hear) sound, but connect to same TS3 room twice using 2 separate tabs: one tab has muted speakers, and another one had muted mic. This way I hear myself when I am talking, and so my voice gets recorded to video with the same quality as others. Unfortunately, this approach requires a bit of training. It is not so easy to talk when your hear your own voice with slight delay: it can make you sound weird, stutter, and it can make you feel like you are always interrupting somebody. However, once used, you will be able to record high quality captures pretty much in effortless way (no sound track cleaning, no merging of separate voice tracks and so on).

DCS update with Mig-21 coincides with NVIDIA driver and game experience update. There was even some sort of hype over Mig21 subforum about increased fps with new drivers, so I think lots of guys updated them. The problem is that new NVIDIA Game experience version has something changed in its Shadowplay (screen capturing component), and that greatly messes up with apps, which are run without admin rights and are not in foreground. I suspect ShadowPlay is running with elevated permissions without providing UI access rights to processes with lower privilleges, and preventing propagation of keys strokes among them that way. If I have Shadowplay enabled, TrackIR software does not see key presses for centering, Teamspeak does not react to keyboard based PTT buttons, games have problems alt+tab'ing out and in (sometimes DCS even stops reacting to keyboard at all after alt+tab'ing back). If I disable Shadow Play, everything works ok. Please note, I run mentioned software WITHOUT admin rights. So, If you have NVIDIA card, have NVIDIA Game experience installed, try disabling ShadowPlay and test alt+tab'ing. If it solves the problem, give feedback to NVIDIA. I described the problem here: https://forums.geforce.com/default/topic/775771/geforce-experience/geforce-experience-2-1-2-feedback-thread/post/4317393/#4317393

Mirage III

You will hardly break it while flying fast. Try turning at 300km/h or so. The reason why most people break engines is overheating, which happens because: 1) not enough airflow over radiator while flying slow on full power for too long 2) lagging automatics of radiators (if you fly at high speed for long enough, your radiator will close, however if you bleed all the speed suddenly, it won't be able to open up fast enough to cope with sudden change of airflow and spiked temperatures).

You can use the fuse switch to tun the sight on/off and the switch on the sight to turn gyros on/off (handy if you need a fixed sight).

Are you judging this by acceleration and speed? There was a change to ASI, which previously showed higher speeds, so now it may look like Dora is slower and bleeds more speed in maneuvers.

Search for updater shortcut in start menu. It does forced check for update.

Sights know your acceleration (from gyros) and distance to target (sight setting). They calculate the lead assuming that target has exactly (or almost) the same acceleration. In practice, if you want gyro sight to be useful, you have to set correct distance, get into the same plane of motion as target and match the Gs by steadily tracking the target (having dot on it). Then rounds will land directly on it. P.S defense against such sight is simple - non uniform 3D maneuvering.

Pulling stick fully back on initial roll out is often a desirable action. It creates additional downforce on the tail and loads tail wheel more making it harder to slip and more responsive to steering. However, one must not forget to gradually release the stick as aircraft speeds up and rudder authority is gained. Failing in that will result fatal "jump and crash" situation. P.S. the same goes for Dora, however it does not have steerable tail wheel, so pulling back, locking and loading the tail wheel will make Dora somewhat less steerable, but more directional stable.

There is a hope we will get EDGE (new rendering engine) till 2015. If DCS is the sole reason for upgrade, wait for EDGE at first.

Yes, because it is not trimmed for idle :)

The most maneuverable was F series. G6 suffered from weight creep and aerodynamic uncleanness (bulges here and there, non-retractable tailwheel and so on). I am too lazy to look for exact quote, but Rall has said something along these lines: G6 wasn't terrible, we did ok with it, but it was far from F agility wise.

Ground adjustable trim tab. You can't change it. Some MG151/20 ammo had detonator timers, so that missed rounds would not land in some farm or street and cause damage.

Take cold start quick mission with P51, go to external view, then turn camera so that you will see rudder and tail wheel. Move rudder left and right and observe the tail wheel - it will move a bit left and right too. That is why you can steer P51 easily. Do the same with Dora, and you will see its tail wheel being static, because it is nonsteerable (it can be either in "it does what it wants" mode or locked when stick is pulled back).

P51 has steerable tail wheel, Dora doesn't. That "small" detail makes a huge difference.

P-39 has adequate performance up to 4000m. Yes, it would suck as strategic bomber escort or interceptor, but if you are hunting or covering tactical bombers/ground attack aircraft, then P-39 is a nice tool to do the job. Eastern front featured lots of ground action and CAS, so P-39 did very well there. It would be the same in DCS with ground war based missions.