c0ff

Some of the changes to the game and official modules will definitely be forbidden, but only those directly related to the DRM. All other modification to the existing files will be ok for SP and non-IC servers. I'm not sure about adding textures/sounds: adding a file to the game will imply a module, because game, as planned, won't see any files not listed in the manifests. So, this will require to have a manifest, though it is still an open question how to implement this requirement in the most transparent and user-friendly way. Probably, it will be able to do on-the-fly manifest creation for 'Saved Games' mods. Things are not set in stone yet.

DCS includes manifests, which contain hash/size information about core game files. Modules, located in the game install folder are required to have manifests. If case of any manifest check failure, the client is marked as non-IC-compliant and he can't enter servers requiring the IC. Currently, only a selection of files is checked. Sound/texture modifications are not checked yet. Modules, located in the 'Saved Games' folder are not expected to have manifests, yet. The big plan is that: 1) the installed game files are not allowed to be modified. 2) all modification to the game can only be done via user-created 'modules'. Be it sound, texture, model, or unit modfication or a mix of such. 3) each user module will be required to have a manifest, created by an official tool (most likely, the tool will be shipped with the game). This will make the modifications to the game identifiable and controllable - that is, server owners will be able to control which exact versions of user-mods are allowed to be used by their clients. And of course, all this implies a published documentation on how to use all this features.

Can you, please, reproduce the situation with at least 1 client and send me the dcs.log from the server?

Don't know about "they", but we are. It will require some means to identify the user mods, though - this is not implemented yet.

The old IC method will not return because it was trivial to hack it around. May be it was not a common knowledge, but the method was fundamentally flawed. Not that the new method completely replaces the old one as of now. There's still much work to do. But this will be work in the right direction.

по какой причине?

They will have different version numbers. Still there won't be any way to roll back since the pulled version is not available to the public.

There are no plans to disallow mods. However, there will be some changes in modding methods, to make them more refined and structured than the current "just change the game files" fashion. Old method of IC just can't reliably work, because its underlying assumptions were wrong.

Update: the fix was implemented and successfully tested internally. It will be released to the public in the nearest update.

It seems to be a bug in the Visual Studio Runtime library. Some other applications hit the same bug (VIM editor, for example). We are looking for a solution...

looks like a bug in the torrent library. thanks a lot for the logs, a real help! to be fixed...

you can easily make your server post any its info wherever you choose by using Lua-scripts as documented in API/DCS_ControlAPI.txt

no

You can use both. About your first post: install command is case-sensitive.

1.5 does not use XMPP anymore. So it's only HTTP http://www.digitalcombatsimulator.com:80 HTTPS http://www.digitalcombatsimulator.com:443 and TCP/UDP on 10308 (by default) for MP traffic.

It is not visible for the servers which were not visible before, if that makes any sense :) We'll definitely fix this. edit: btw, nice login, speaking as a 0xC0FF now :)

Hmm, seems we need to repackage the installers. Thank you for the report!

There is a problem with Win7 w/o SP1. Please, get the newest updater from here: http://updates.digitalcombatsimulator.com/ it has a work around for this problem. or consider installing ServicePack1.

DCS uses 3 directories in total: 1) install dir 2) Saved Games\DCS (or DCS.* for openalpha/beta) 3) AppData\Local\Temp\DCS (or DCS.* for openalpha/beta)

No and no.

sure. in the near future the updater will ask to clean up those.

Can you elaborate on that? With the logs, please.

Разрешить пользовательским Lua-скриптам получать информацию об объектах игрового мира. Это касается работы функций Lo* в Export.lua и Export.* в *GameGUI.lua

that's the same issue as with the updater. a compiler bug which shows up on pre-SP1 Win7 machines. We've added a workaround to the DCS, it will be out in the nearest update

API/DCS_ControlAPI.txt