ZaltysZ

Yes, but... you must take into account the aircraft involved. Most instructions are intended for modern BFM, what means high Gs dogfights with fast jets, and assumption, that attacker needs to get into plane of motion of the target, sit at correct range and at relatively low angle-off, or else it will be very hard to get correct firing solution due to insane deflection angles required and errors introduced by aircraft aiming system. Defensive BFM relies on techniques, which complicate attacker's efforts getting into such position. Keeping your lift vector on the attacker is one of such techniques. However, if we do talk about BFM in WWII context, you should be aware of lower speeds, lower Gs, and so on, what makes positional requirements for shooting somewhat less strict. If human pilot has something like 20mm guns at his disposal, he can easily prefer taking out of plane snapshots at high angles-off instead of getting into position behind the target. If target blindly tries to put its lift vector on such attacker, target can easily victimize itself, because putting lift vector on attacker usually presents larger area to be shot at.

Gyro works fine, however it has to be set properly (correct target size and distance) and you should be pulling constant Gs in the plane of motion of target. Target size setting is no brainier, and distance setting can be made easy by using such "impure" means as HOTAS (i.e. constantly adjusting the distance while aiming, so that sight circle always surrounds the target perfectly). The hardest part is constant Gs and staying in plane of motion of target as this requires some cooperation from target. I use the gyro against easier targets: AI, cooperative human pilots, which are: a) preferring 2D maneuvers, b) not seeing me (like when I do BnZ) c) being predictable (like they are chasing my wingman). In other cases, I prefer static sight, but leave the gyro on too: static is for aiming and gyro is for coordinated flying (if both of them are not lined up, there is a need to step on the "ball").

Nope. You might have malware in your browser. Whatever browser you are using, check extensions/addons and remove weird ones.

Just get near the surface of runway, flare and pull a little bit more. Plane will stall and you will end with a nice 3 point landing.

Just to make sure... are you holding the launch button or just push it briefly? P.S. other reasons why MAV can want not to break with you: 1) not selected as weapon (check HUD or DSMS) 2) flaps are down.

You are reading too much into this. Russian change log is more precise, it explicitly mentions just "target's flight parameters" ("параметры полета цели"). Basically, SAMs used to check only the range (if target got into the pre set "zone" around the launcher, then missile was launched - poor man's DLZ). Now, target's position, speed, direction and altitude should be able to distort that zone. I.e. Ka-50 flying into the SAM should get launch at it way closer to the SAM, than F15C doing the same at near supersonic speed.

Speed is a function of nose pitch angle and rotor pitch (blade angle). This means, if you fix nose pitch and blade angle, aircraft will settle at certain speed, and you will be stuck at that speed unless you change either nose pitch angle (using cyclic) or rotor blade angle (using collective). So, if you tell AP to hold certain nose pitch angle and stay at certain altitude, it may look like it is also holding the speed. However, this is only a side effect, and AP does not care about the speed. If you want AP to keep certain speed, you must tell it not to keep nose pitch angle, but vary it accordingly to speed instead . This is possible in ROUTE mode. If you need to keep flying at precise speed while not on flight plan route, make sure you have no waypoint selected. This way you will be using so called "route without task" mode, and AP will try keeping commanded speed for straight flight. Always remember that AP is intended for fighting small oscillations and deviations only. It needs aircraft to be in roughly correct attitude before it can make it into precisely correct attitude. This means, that it won't hold 50km/h if you release trim button while cyclic is in pretty far forward position and so on ;) It does not have authority to overcome that.

Do not use your wheel brakes for steering. They are not normally intended for that. Line up for take off, begin the roll with nose wheel steering on, correct direction if necessary. This should be sufficient initially. Turn off nose wheel steering when you pick some speed and continue steering with stick. Wing, which has aileron up, will put more pressure on its wheel and will cause it to slow down a bit without you touching the brakes. This should be enough for keeping you aligned until you get into the air. Make sure you don't land into the middle of the runway. Try landing at the start of runway. Having such great aid as Total Velocity Vector (TVV) on the HUD makes this very easy. Touch the runway and just roll. Don't touch the brakes. Use stick (ailerons) to steer. Aircraft will bleed lots of speed by itself, and you will have only to switch to nose wheel steering and use some brakes just before the turn into taxiway.

If you are using area tracing - sure, but if it is in point track mode, TGP will hardly wander away from target, unless you do some crazy maneuver.

Higher RPM = more responsive speed control: better acceleration with opened throttle and better deceleration with closed throttle. It is easier to abort approach or even landing this way if emergency (like sudden attack on airfield) arises, however it requires more precise throttle movement for keeping desired approach speed, because slight throttle movement might result in quick aircraft speed change. Also, running on higher RPM should help more in keeping spark plugs clean, which is pretty important when you are low and slow. I think manual recommends 2700 rpm, just because it is "maximum continuous".

Shouldn't the weather settings be fixed for this competition? :smartass:

Auto actuator works in a way something like this (a bit simplified): it knows 2 temps: min (let's say lower mark of green zone) and max (let's say the red mark), then: a) if it senses the temp below min, it closes the doors until they are fully closed or until temp rises above min b) if it senses the temp above the max, it opens the doors until they are fully opened or until temp drops below max c) if it senses the temp between min and max, it leaves the doors alone. System is intended to keep the temps between min and max, however it does not care what you get exactly: it might be near min, near max or in the middle. In addition, operation of doors isn't very fast, so if you are not very friendly to system (like long shallow dive, quick energy bleed, prop hanging or prop hanging, steep dive) you can easily end with temps outside of operating range for a short time.

I don't think RAIM prediction is broken. I think airfield database is. RAIM calculation screen expects up to 4 character callsign indicating airfield in ABRIS database, however most airfields has no callsign at all or has more than 4 characters as callsign in BS2 (1.2.7). It is very obvious if you go to NAV>SEARCH>AIRFIELD and cycle through airfields in database.

Lots of us don't buy a gaming computer. We build one and constantly upgrade. It is hard to judge how old our computers are. I.e. I still use i7 920 I have bought in 2009, I still use HDDs I have bought in 2006, but I also use VGA and SSD I have bought last year. My computer also had a RAM upgrade (6GB@1333 -> 12GB@1600), new PSU, 2 other VGAs between 2009 and 2013.

And aside from power failure :) https://www.usenix.org/system/files/conference/fast13/fast13-final80.pdf

Read that thread very carefully. OP of it even had stutters when OS was on SSD, and DCS was on separated disk (HDD). It was solved by changing SSD to newer one (EVO). I guess the problem has been related to TRIM implementation of that particular drive. One other poster had similar problem and it went away by disabling TRIM. People concentrate on the reading part of disk usage (loading textures and etc.), but don't notice that DCS does lots of writing/reading to user home folder (temporary files, logs), which resides on OS drive by default.

Larger SSDs have more chips on them, and this allows higher parallelism, what results in better performance at higher queue depths. 250GB outperforms 120GB, 500GB outperforms 250GB and so on, however difference isn't so noticeable at higher capacities as is between 120GB and 250GB. If you are going for RAID, make sure your controller is able to pass TRIM to separate drives in array. EVO is a bit newer, and is supposed to be an upgrade to non Pro version of 840. EVO and Pro performance is very similar in real world and even close in synthetic benchmarks. Theoretically Pro should have a longer lifespan due to usage of MLC, and not TLC, which is used in EVO. Unless you are going to do lots of writing (like in server environment), this should not be much of concern to you. Basically, if price difference between Pro and EVO looks petty to you, get Pro; if not, get EVO. :)

DVI-D single link cable will fit into DVI-D dual link connector on the VGA. Some holes will be left empty on VGA connector, but they are not used for single link connection anyway, so everything will be fine.

This is one of the reasons why some pretty big web sites still do not support IPv6. User installs the OS, and OS comes with IPv6 enabled by default. User enters URL in the browser, browser makes a DNS query to get IP of the web server to which URL points to. DNS server returns bunch of IPs: IPv4 and IPv6. Browser prefers IPv6, so it uses IPv6 for connection to web server if browser OS supports IPv6. Unfortunately this is a fruitless effort, if ISP does not support IPv6 or there is no IPv6 over IPv4 tunneling present. After a while, IPv6 connection attempt timeouts and browser fallbacks to IPv4. This causes huge delays and makes you feel like your browser is crawling. Disabling IPv6 or telling your browser to prefer IPv4 solves the problem, however this is unknown or too cryptic for lots of users, so big websites simply drop IPv6, so that even clueless users won't get those delays, which may negatively affect how much users browse that website, and in turn, cause damage to revenue. P.S: By the way, Win7 solved that issue on its own. If it sees that computer has only link local or Teredo IPv6 IPs, it resolves names only to IPv4, unless name does not have IPv4 IP at all.

Oh, dear neighbor, is that really that bad there? :)

The thing with IPv4 address space is a bit tricky. IPv4 addresses are allocated in blocks by regional registries, then given to local registries by blocks too and so on. When they say, all address space is almost exhausted, it does not mean that almost all IPs are allocated to some hosts, it only means that almost all blocks are allocated from the point of view of top level registries. Situation might be different at lower levels. Some countries, ISPs like to hoard IPs (i.e. they request way larger blocks than they need or have done that in the past). There is no 100% working mechanism for reclamation of such unused IPs, but it is still done in some ways (i.e. some companies approach others with offers to buy their IP ranges and so on). I would say if having IPv4 internet routable address isn't still too pricey for ordinary home user, then real exhaustion hasn't happened yet. :)

I don't remember them nor in BS2, nor in BS1. They might be a removed feature from pre release version, and just were forgotten to be removed from manual. Judged by their orientation, they look like they might have relation to XTE and might be an aid in choosing interception heading.

The easiest way to check the difference is by looking at vertical speed indicator. Take off with min throttle and then with auto, you should eventually build more m/s on auto.

Which version? 1.2.7 or 1.2.6?

Do you have an HDD too? If yes, could you try one thing? Reenable DeleteNotify, create TEMP folder on that HDD and change environmental variables (TEMP, TMP, TEMPDIR) so that they will point to it. You can do that via Control Panel>System>Advanced System Settings>Advanced>Environment Variables. Change only "User variables" and then restart PC. Constant truncation of temp files is probably the reason why trim gets triggered.