c0ff

I'm glad it works for you now. Thanks for the feedback.

that's what happens if you don't really believe in that "tradition" ;)

oh my... i haven't checked the date :-/

Everything is working as usual here. the check is performed not sooner than 24 hours from the previous one. However, it seems like the updater can't successfully check for updates at all for you. That's why it tries to do it every run. If you wait for it to complete, what it says in the AppData\Local\Temp\DCS\autoupdate_templog.txt file?

this is not an intentional behaviour. will check this. thanks for the report.

great news! the fix will be published soon.

I've made a workaround in the updater which may resolve the crash, though I need someone to test it.

I've sent you a PM regarding the issue.

Looks like on Win7 the updater requires SP1 to work. http://forums.eagle.ru/showpost.php?p=2626474&postcount=13

You should.

Thank you for the report, we will definitely fix that!

A great suggestion! Thank you :)

http://forums.eagle.ru/showpost.php?p=2621577&postcount=5

Thank you for the detailed report. Seems like bad timing - we had a serious problem with one of the servers which you got into. Also there's no recovery path when installs for that pop-up fail - a thing to fix. Meanwhile, drop this bat file into your DCS folder and run it once - it will install all your modules but the L-39 which managed to succeed. Gizzy-install-fix.zip

your openbeta will continue to be what it is - an openbeta, either identical to the current release or ahead of it.

На одном из серверов проблема с каналом, сейчас он выведен из ротации. Для надёжности можете перезапустить обновление.

so it didn't show you a countdown, did it?

The trick was to trace the exact srvN(<-the number from the log).update.digitalcombatsimulator.com server to refresh its DNS record. The updater does not use the 'updates.digitalcombatsimulator.com' address.

https://www.digitalcombatsimulator.com/en/support/faq/399/

Well, that's not as straightforward as it used to be, but doable. Just install what you need on that "another PC" and then move the files and the HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World OpenBeta\ and/or \DCS World 2 OpenAlpha\ registry part to your "home PC". The official "offline" installers are not completely out of the picture, but are not currently available.

It would be nice to see that log attached.

1.5 uses so-called T3 terrain tech, while 2.0 - T4. The short-term plan is to use 1.5 openbeta for pre-release updates, as it always was, and 2.0 for all T4 development. When T4 Caucasus will be good enough for openbeta, i.e. relatively close to a release, we will push 2.0 to openbeta and drop the openalpha until some bright future far far away :)

Technically, you can see these 'release', 'openbeta', 'openalpha' as update channels which the builds of DCS are distributed through. We call these - branches. So, for example, build 1.5.2.48726.137 was released to the openbeta branch first. And yesterday we pushed the very same build to the release branch. They are essentially the same build of the DCS, byte-identical.

Yes. Yes. (Though, I'd delete the C:\users\me\Saved Games\DCS first.) Yes.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557419%28v=vs.85%29.aspx It's an OS kernel-level error. Most likely a faulty DX11 driver.