EtherealN

You would probably have to contact customer support. http://www.digitalcombatsimulator.com/en/support/

While definitely desirable, a combat simulator has a problem that MSFS (and XPlane) does not have: it has to be theoretically capable of running the entire map, since there is "risk" of there being active units conducting battle precisely anywhere on that map. Even a "bubble" system like in Falcon 4 doesn't quite solve this, since this needs to be possible in MP as well; and what happens when actual players are well dispersed and you can't scale with bubbles anymore? There probably is a solution to these issues, there usually is, but it's not exactly easy. One option I could imagine (but that is kindaugly) would be to have overlapping but otherwise separate maps, where if you leave an area for another, the former area gets dropped an nothing gets to happen there. But this gets sort of ugly whenever action starts happening around the edges, and doesn't solve the MP issue.

IMO, a better seting for a concept like this would be some action in the pacific or north atlantic. Lots of water -> less polygons -> possibly greater area -> still realistic placement. Add carrier-enabled aircraft and you also ensure that you don't have to fly multiple-hour sorties everytime; when desired, just place the carriers closer.

Incorrect. It actually makes stealth even more important; it allows you greater room to get in a desired VID position without the bogey or their radar sites knowing what you are doing, reducing the risk exposure that comes from a VID ROE. Also, part of the job for stealth planes is to ensure that no-one will want to actually fight a war with you, since they'll know you will take air superiority (or strike ground targets with impunity). And in the event of a full-scale shooting war (say, US vs Iran) the VID ROE might not be in place at all, as well, of course. It is usually conducted in theaters where the enemy has a considerable air disadvantage (for example numerically), where "shooting whatever looks to not be friendly" carries a significant risk of accidently popping some stray businessjet or airliner etcetera. EDIT: Also, there is nothing in a VID that necessitates that you sacrifice energy advantage. You don't have to fly fingertip with a bogey to see if they are indeed bandits. ;)

You fail to note that iranian F4s are not "enemy" fighters. Iran is not at war with the US. VID and visual threat assessment is standard roe there: you have to be REALLY sure about the necessity before attacking someone you are not at war with. (And indeed, VID has been a frequent ROE requirement even in some wars.)

Regarding serial key: note that Upgrade and non-upgrade versions are separate, check that you have installed the one that is appropriate for your license. You can read in top left of the activation box. The upgrade version wil say Black Shark 2 Upgrade. If you have an upgrade license, and the activation box does not have the word upgrade, you should remove Ka-50 and then install using the module download that is marked as upgrade.

As mentioned, this is IE trying to be smart. The only people who can "fix" it is Microsoft.

Before i tried them i felt normal boards were just fine. Then tried a Razer Blackwidow Ultimate and got hooked. A while ago i emptied a can of beer over it (oops) and had to let it dry for a few days after cleaning it. Was so horrible i bought another Blackwidow to ensure my backup keyboard is also mechanical... Basically, they are like TrackIR: before you try you feel you are doing just fine. After you try, being without feels horrible.

Most likely you have previously used that serial number with another account online. This sometimes happen because A10C standalone originally simply assigned to the first account that uses it online. You can verify this through this page: http://www.digitalcombatsimulator.com/en/myserials.php Log into your account and then check that page. If the A-10C is indeed not on this page either, most likely you have at some point used a different account with this product originally. (Might be one created in the MP interface itself.) To solve this, you would then need to contact customer support service through this page: http://www.digitalcombatsimulator.com/en/support/ Include the relevant information and this can be investigated to see if there is some other account you might have used.

Ill PM you my mail adress, send me a note there. Email is easier on hotel internet. :)

In the main screen of the single player menu, do you see a dollar sign on the Ka-50 icon? If installed properly, there should be no dollar sign there. Just to be sure. In the Module Manager, have you ensured that you have properly gotten logged in? You should see your account name in top right corner. (Unfortunately I cannot double-check right now, I am traveling.)

I don't know, never dug into that side, but I suspect it is possible. (There's a lot of interesting things you can do in LUA, but there are limits.) It will flag you as a cheater in multiplayer though, so make sure you have an easy way to revert any changes you want to make.

A couple years. Know how long it usually takes to develop something like that? A couple years. ;) That's the reason so many shooter devs license someone else's engine; they don't want (nor can afford, usually) to spend 2 to 7 years building a competitive engine before they can properly start on their actual game. The days when competitive game engine took a couple months to a year to make are long gone.

Topic is Igla. If you have concerns about other users, bring them to a forum moderator or community manager, don't derail threads with discussions about who has what attitude.

Oh maaaaaan! That right there is how I got into flight sims. :) We got it on a CD when we bought our Pentium 75, bundled with the Soundblaster. I had flown some Falcon games before on Amiga, but never got into them. Yeager got me hooked though. (Still remember when family went to germany for a meetup with my family there, and I went to Karstadt supermarket to find myself an analog joystick specifically for that game. :D )

Another classic: Setting up sound cards. Every single game. Good memory from when me and a mate tried to get Warcraft 2 running. After digging through IRQs and DMAs, the setup program had this voice recording to announce that "yup, it works." It said: "Your sou-n-n-n-n-n-d ca-ca-ca-ca-ca-ca-ca-rd worrrrrrrrrks pe-pe-rfeck-ck-ck-tly."

Or when "pirating" music software meant borrowing a stack of 30 floppies spreading a zip archive from a mate in school, only to get a CRC Fault on number 28. That taught me. :D Though turbo button in my case, my computer-illiterate father was convinced, meant that our IBM 286 (_actual_ IBM, not just compatible!) turned into a 386. Looking back, I think he was had by a salesman. :P I actually missed the 486 generation - moved from 286 to Amiga 500 to Pentium, aside from a bunch of 486es school had that were meant for writing our papers, but we used them for playing Hearts (after we got Windows 95), Doom and Wolfenstein. :P (Then we got some nice Pentiums in the "media room" that were capable of running Command & Conquer... Chaos ensued. :D )

...and the younguns today complain about steep learning curves... :music_whistling:

Start > All Programs > Eagle Dynamics > DCS World > Documentation

http://www.digitalcombatsimulator.com/en/files/ A bit too simplistic analysis.

Mmm... The Daily Fail. :D

Not sure I see where you consider the problem is. It detects the incoming signals, analyzes them really fast*, and then sends signals on a return vector to confuse the echo the threat gained. Works the same against missiles and aircraft. (Though different sets have varying vulnerability.) ECM knows the enemy missile's frequency though listening to it. If the missile can beam you, inverse square law means you have way stronger signal from it, than it gets from your echo. * This is a computation problem. You just need to get a sufficiently strong computer in there, and electronics that are fast enough to get the computed appropriate "response" signal sent back to the threat. This is the same as the self-defence jammers fighters have had for a long time. You can see the A-10C in DCS do this if you carry it's pod; it'll see the threat and defend against that specific threat. NOTE: only that threat. "Real" ECM doesn't really work like you see in most simulators; they (including Flaming Cliffs aircraft) have noise jammers, which are different, and not very effective against modern equipment.

You're a MANPAD trooper? There are people here with direct experience. ;) Remember that the term "Igla" is like "Sidewinder". A lot has happened in all those years. The first generations of Sidewinders were crap. Modern ones... not so much.

Considering he had rotor intersections and (presumably) slammed into the ground... Yeah, he probably was on fire. :D

If you look closely at the memory compatibility charts (assuming your vendor supplied a proper one), you'll note supports above 1333 and/or 1600 (depending) as "OC", for "overclock". What it means is that they have tested these memory sticks at their design specifications and they work. But the memory controller and BIOS/UEFI will still consider this an overclocked memory. (I have the same processor as you do, and I similarly had to reconfigure my 1600MHz memories from 1333 - but my manual warned me about this. It is normal.) Have you run Memterst86+? I would recommend doing so with the sticks in the operational positoin first, just to make sure there's nothing wrong with them: http://www.memtest.org/ It might be total coincidence, I've had mysterious things like that happen to me a few times on previous machines; sometimes the memory controller (depending on it's status as well as that of mobo connections etcetera) is more sensitive to faults on some ports; similarly support for given configurations of sticks can sometimes only be for specific port setups. (Black magic.) Since it worked previously, it shouldn't be a support issue, but it is possible (if remote) that something happened on first boot after the reseat of the cooler that damaged the controller and made it more sensitive. Either way, a full memtest run should probably be your first step.