c0ff

It says: "branch": "openbeta", it means that you either did "DCS_updater update openbeta" there, or edited the file, or replaced it from an openbeta install. To fix this either remove this line or cmdline this: bin\DCS_updater.exe update release

please, attach the autoupdate.cfg file from your release install.

We have our own seeds of course. Pretty fast ones.

I disabled the torrents as the default route of the updater. Our seeds keep working as usual. You may cancel the update and it will ask you to use HTTP.

Thank you for the reports, guys. We have to do some changes to the torrents, because it seems like only update downloads tend to stall. Installing full modules works blazingly fast. I've temporarily disabled the torrents until we rework things a bit.

nice you have a dedicated thread for torrent talks. Sorry that it worked out not so great at the start, but it was the only way to see how it will behave in the wild. It seems like most problems are related to how the files are layed out in the torrents, because while update downloads crawl, installing a full module is blazingly fast so far. We gonna make an experiment or two with the layouts, will see how it goes. Also, there's an idea to let users seed what's downloaded, many people asked for this option. Thank you for your support.

HTTP downloader tells the uncompressed size in the top line because decompression is done on the fly, true DL size is on the left below the progress bar. Torrent downloader tells the compressed size because decompression is done in a separate step. Sorry, this is misleading a bit. Fixing requires some non-trivial changes.

updater 2.6.3.26 is out: supports so-called 'web-seeding' - if it can't find data among the peers it will download pieces from http, so it should be best of both worlds. still, pressing cancel on torrents asks to go old-school http which may be better or worse depending on the current conditions. to use new updater you should completely cancel current update process and start again from the 'Update DCS World' menu entry.

updater 2.6.3.26 is out: supports so-called 'web-seeding' - if it can't find data among the peers it will download pieces from http, so it should be best of both worlds. still, pressing cancel on torrents asks to go old-school http which may be better or worse depending on the current conditions. to use new updater you should completely cancel current update process and start again from the 'Update DCS World' menu entry.

looks like you managed to start dcs_updater twice. thanks for the report

1.5.1.47285.107 is live on Steam openbeta now

$INSTALL_DIR/autoupdate_log.txt and $TEMP_DIR/autoupdate_templog.txt

not yet.

cancel in fact does this. it does not pick up until next day though, unless forced. a bug to be fixed. thanks for reminding.

sorry, some technical delays. we are working on this. many changes these times, you know ;)

it depends. 2.6.2.25 reached 2-8 MB/s here, so it's the question of tweaking the beast. thanks for massive testing btw. your patience and understading is really appreciated.

no user settings yet. most links afaik are full-duplex so your uploads do not hog the downloads.

2.6.2.25 should be better. cancel and restart, please. it will go http if torrents are cancelled, but please give it 2-3 minutes and report how it goes. thanks btw, 2.6.2.25 will squeeze the most of the partially downloaded torrents so it makes sense to try even if you go http then.

2.6.2.25 should be better. cancel and restart, please. it will go http if torrents are cancelled, but please give it 2-3 minutes and report how it goes. thanks btw, 2.6.2.25 will squeeze the most of the partially downloaded torrents so it makes sense to try even if you go http then.

At the top of your autoupdate.cfg file, and this is NOT a joke: "WARNING": "DO NOT EDIT this file. You may break your install!",

It tries to redownload what it can't get, several times before giving up.

yep, an issue. it should try again next time if an updated failed. needs to be fixed.

And hope it's not a bios-level infection... I heard there're rootkits which hide in the bios flash!

looks good. a weird problem, indeed.

Please, post the result for edCore.dll as well.