c0ff

Ветка реестра с активациями у них общая. Так что если релиз с бетой на одном компьютере, то при удалении беты деактивировать модули не нужно, иначе они деактивируются и в релизе.

it will be nice if you attach the autoupdate_log.txt which is opened in the Notepad.

This is not a DirectX problem. DCS exe fails to validate its digital signature, so this is either a malware, or, ironically, an antivirus problem.

To convert your OpenBeta to release, do bin\DCS_updater.exe update @release The menu entries will still say OpenBeta though. So take this as a warning that you may end up with a version which says OpenBeta in the folder name and the menu shortcuts, while being, in fact, on the 'release' channel of the updater. Actually, better NOT do this. A MUCH better solution: Just install the release, it will pick up the files from the openbeta, and delete openbeta after that.

Они идентичны.

The today's release is completely identical to the latest openbeta. The openbeta will continue to be ahead of the release versions or on par with them.

live

The most easy way is to copy (copy, not move) your 1.2.16 to a separate folder, say, 'DCS World 1.2.16' and let the original one to update to 1.5. If you want to get a really pure 1.5 install and still save about 12 GB of downloads, then: 1) install 1.5 release into a separate folder 2) uncheck 'Start Download' box (!) at the last page 3) create a file dcs_local_source.txt in the 1.5-release install folder and paste a path to the original 1.2.16 install - this will pick unchanged files from 1.2.16 saving you about 12 GB worth of downloads NOTE: save dcs_local_source.txt in UTF-8 encoding. 4) run 'Update DCS World' for you new 1.5-release install.

Not so fast :) It will, once we fix the servers. The installer will come in the same form it was for openalpha: it installs just the updater, icons and readme, and starts a regular update. So no point to use it if you have 1.2.16 installed - it will update automatically.

Самый простой вариант - поменять ярлык запуска с DCS_updater.exe на Launcher.exe

Exactly. Files will be copied from OpenBeta, or OpenAlpha as long as the "Path" can be found in the registry. So, if you have OpenBeta installed, the actual download size will be about 0 bytes. If you don't have neither OpenBeta nor OpenAlpha, the DL size for 1.2.16->1.5.2 update will be about 6.1GB for pure World with no modules. If you have OpenAlpha installed, then 1.2.16->1.5.2 will be about 2.4GB

please, check if you can acess these links: http://www.digitalcombatsimulator.com/ http://srv4.update.digitalcombatsimulator.com/ also, check this thread: http://forums.eagle.ru/showthread.php?t=156525&page=2

To reset local DNS cache on your machine you can do ipconfig /flushdns from an Administrator Command Prompt.

Note: the IP addresses are different. The first one is a month-old address. Looks like a DNS cache was not updated on your machine.

I think yes. http://updates.digitalcombatsimulator.com/ and any srvX.update.digitalcombatsimulator.com should show the current versions of DCS release, openbeta, and openalpha, links to the installers and the zip with recent DCS_updater.exe

Something intercepts the http requests, like a proxy. "nginx/1.4.6 (Ubuntu)" is not our server.

can you open the url: http://srv4.update.digitalcombatsimulator.com/ ?

Oh, please, attach the autoupdate_log.txt file, after the updater finishes (it should show the shutdown timer counting down from 30 to 0, before closing).

Если у Вас в каталоге игры остался файл wakeups.log, пришлите его мне, пожалуйста.

your autoupdate.cfg file is broken, please post the contents

Если Вы можете воспроизвести "вылет Обновлятора", прошу Вас связаться со мной. Нужно будет воспроизвести крэш на специальной отладочной версии "Обновлятора" и собрать логи.

This "ERROR: torrent: UDP error:" - is not a problem, apart from excessive logging. The crash is the issue I try to reproduce but to no avail yet. I've sent you a message.

I need help from someone who can reproduce the crash. Please, send me a PM.

It's a problem in the torrent library. I'm in contact with the devs and we are searching for the reason... Meanwhile, I moved the torrent shutdown code to the end of the process, so at the point when it stucks all the update/install operations are completed.

FYI: we did some cleanup and the only 1.5.0.x version currently available is 1.5.0.46175.67 which was the last from 1.5.0 series.