c0ff

I can suggest you to either use an autoexec.cfg workaround or wait until the next openbeta which is around the corner.

It was never implemented and with recent changes to Steam authorization it became possible to do, but requires some work. Can't make any promises at this point. So, at the moment you better go standalone if you need offline mode. Note: The standalone installer can pick up files from Steam if DCS is installed into the standard Steam library. If it is in a different one, then you'll need either a dcs_local_source.txt trick or just move the files to the future _downloads folder of your standalone DCS.

No offline mode in Steam at the moment.

tech savvy users can set up a symlink for _downloads and manage it themselves.

I beg to differ. The reasons mentioned above.

any logs?

Thanks for the feedback. This will become the default in the next openbeta.

Hi guys, Finally, you can pre-order the remastered Lockon Flaming Cliffs 2 Soundtrack here: http://c0ff.bandcamp.com/ Full release on all platforms will come October, 10th.

Not yet. I'll add a feature request.

it could be a Steam glitch. There were no related changes on our side.

This is a driver bug. The proper workaround will be out in the nearest openbeta.

Looks like something resolves the site DNS name into localhost (127.0.0.1) for the updater.

He meant Saved Games/DCS.openbeta/Sounds/

You have to update to 2.5.5.41371.1 first. DCS_updater.exe update 2.5.5.41371.1

Me neither. If you had them installed, why did you reinstall?

It is not. That build is no longer available.

Yep, the list of functions in API/DCS_ControlAPI.html#export-api needs an update, but the actual list is the same as in Export.lua by design.

They should be. I've just checked the code and Export.* contains all the API available in Export.lua, except for a couple of deprecated functions (which you definitely do not use).

Hooks have almost all Export API calls available to them. If you miss any functionality, please tell.

Thank you very much for the log. Try again please, I've tweaked some settings on our side.

Not of the updater, but DCS itself. One of the reasons: no updater in Steam. (another one, DCS must clean up its own stuff, not relying on external tools, especially on the distribution platform which should not know the specifics of DCS, or whatever it distributes).

Then, most probably, something on the software side was blocking DCS_updater. I bet you installed the release version into a different location and that (supposed) firewall rules just do not apply. P.S. You cannot update a module separately from DCS. I guess you meant "installed one of the modules".

I guess, in order for people to use the new API, we have to drop the support for the old ways

This is already implemented with the hook scripts. The documentation is in API\DCS_ControlAPI.html

Need more details. File a support ticket, please.