EtherealN

Ah, okey. :)

Well skouras, they answered the question without indicating that the steps were not required to avoid having to re-purchase, wihch the OP asked and is a pretty important thing. Deactivation is NOT required to avoid re-purchasing. I just wanted to be really sure this was made certain. :)

Steam version lacks Module manager because Steam itself handles this and auto-update. Some module icons are missing on steam because they are not yet released on Steam, FC3 (will not be released on Steam due to licensing issues with Ubisoft) and UH-1 (soon).

Do note that deactivation is not technically required to install on the new machine without having to pay again. Downloads are available from our site even without login; they are always available on http://www.digitalcombatsimulator.com You have 10 activations - these are machine activations - on each license key (if you run out, you will regain the last activation automatically after 30 days). So you are able to download and install directly and then simply activate as normal, if you so desire. Deactivation allows to re-use the old activation used on the old computer, but is not technically required to get your games running on the new computer.

Steam DRM does not support 64-bit.

Hm. I'll check with admin.

Would indeed be quite nice, but do you feel the same if this would mean delays to the F/A-18C? Not sure the resources exist to do "full-fidelity" versions of both these aircraft at the same time.

In your quickstart manual there is directions to deactivate, which allows you to re-use your existing activation.

See my signature. It links to the FAQ which contains this information: http://forums.eagle.ru/showthread.php?t=67747 What are your ticket numbers?

In future, please mind the forum rules. We welcome criticism but require productive criticism. See 1.10. Also, putting random symbols to hide profanity does not make it evade rule 1.1. I'll give you all the chance to start this over on a clean slate, so thread closed.

? Not sure what you mean here.

C&C is owned by Electronic Arts. Origin is owned by Electronic Arts. ;) As mentioned, there are exceptions, but I am not privy to what was done in the background to make it happen. Hopefully it can be made to happen, but it's not an automatic thing.

http://en.wikipedia.org/wiki/Multithreading_(software)#Multithreading

Which version of DCS World do you have installed? You can see that in the bottom right of the menu screen. You can update DCS World through selecting the "Update DCS World" link in your DCS World start menu folder.

Just in case you are not aware of how Module Manager works: Access it through the normal single player menu: Ensure in the top right that you are logged into your DCS account. Once confirmed that you are logged in, simply press "install" on the module you want to install. Note how modules with licenses associated to the account have the "buy" link changed to "install". You can see the difference between the Su-25A and the A-10A here on this screen. When you press the Install button, DCS World closes to allow the updater to do it's work, after which DCS World menu will reappear and you can continue playing.

Before you flush, perhaps you might want to check in to see if this can be solved for you? :) What exactly did you do? What was your install path? I tested Su-25A install through Module Manager just now and it worked.

Well spotted, thanks.

Okey, I missed the "don't" and read is as a "do". Well. Sorry, oops. What I said still counts though. ;) If it's in beta, and also in release, no worries, feel free to ignore. In case you don't understand why: imagine the workload of digging through thousands and thousands of bug reports that you already know about. It is literally better to miss a few than to have several people employed full-time ONLY to remove duplicate bugs. This is about work flow control, not perfection. Perfection is unfortunately not possible in the real world.

I feel you are making a problem out of something that isn't a problem. ;) Here's the stated goal: Users get a chance to check it out, and if they find a bug that is new compared to the release version then we'd love it if they report it. Not talking about new to the test team. Talking ONLY about "it happened between release code and beta". That's really all there is to it. Yes, there probably will be cases where our response is "thanks, known". Well that's fine, isn't it? Because then you know we're already on it. The difference is simply that if it already exists in the older, release, version - then for ease of work you can feel free to assume that we already know about it. And you can make that assumtion because we told you to. :)

Report them. Seriously, when we say "already known", that's not an "eff off". That's "already known", basically letting you know that yup, we know about it.

I'm sorry, but you're not reading it clearly. "DCS Open Beta Testing As DCS World ever increases in complexity and scope, along with a continued expansion of new modules, the testing task has reached the point where we cannot expect our internal and external test teams to catch all the problems in a reasonable amount of time. As such, starting with DCS 1.2.6 we will first be releasing new DCS versions as open beta. Our team and the external testers will be closely monitoring reports and entering valid bugs into our bug tracking database. We will ask reports only be submitted for new problems that did not exist in the prior version. We sincerely hope this will improve the quality of the final version." Thus: Beta: 1.2.6 Release: 1.2.5 If you find a bug in the beta, check if it exists in release. If it does exist in release, no worries, we probably already know about it. If it does not exist in release, it is by definition "new", since it has occured between the "release" and the "beta". Then report. See my title. :D

People that do not have FC3, will not have the FC3 manual. These manuals are for the separate Su-25A and A-10A modules. If you have FC3, you can safely ignore the modules and thus their manuals, because you already have everything, including the manual chapters that tell you how to use the aircraft.

Falcon, here's the procedure: Step 1: Play in "beta" version, notice something and go "hm... that's funny". Step 2: Play in "beta" version, make it happen again. Go "okey, this is wrong." Step 3: Play in release version, make it happen again. IF success == 1 THEN report = 1 ELSE ignore = 1 If you don't want to do that, just ignore all of it and play release, and then everything will be like it always was.

Under this system, you'll get access (if you so choose) to those test builds earlier. Thus, compared to the present, the testers will not already have been hammering on that branch for a month or two when you report it. Then there are the cases when people report bugs that already have 3 open threads about them, but didn't do a search. :P But this is irrelevant anyhow: note what Matt specifically asked; bugs that are NEW to that version. Thus, if you get your 1.2.6, find a bug... check if it is in 1.2.5. If it is in 1.2.5; ignore. (We probably already know about it. )If it is not in 1.2.5 and thus is "new": report. Easy. ;)

Su-25T manual was in there because it comes with DCS World. Su-25A and A-10A manuals were omitted by mistake from those that have those modules. Those that have FC3 however already have the relevant information, as part of their FC3 manual.