c0ff

Expect to see Doc/Sounds/sdef_and_wave_list.txt file in the coming OpenBetas (can't promise it will be in the nearest one). DCS World: ========== Aircrafts/A-10/APU/APU1.sdef wave: Effects/Aircrafts/A-10/APU/APU1 Aircrafts/A-10/APU/APU1Cpt.sdef wave: Effects/Aircrafts/A-10/APU/APU1Cpt Aircrafts/A-10/APU/APU2.sdef wave: Effects/Aircrafts/A-10/APU/APU2 ... You get the idea. It lists all the sdefs and waves referenced in the DCS World and its modules. You can create your own sdef files with the listed names - they will be used by the DCS instead of the stock ones. You can also reference (or replace in your mod) the listed wave files (yes, the names are w/o extensions).

The fix is being tested and hopefully will be out in the next beta.

Hi! I released my first LP: https://c0ff.bandcamp.com/ Melodic electronics. iTunes/Google Play/Spotify/etc will come later. Hope you will enjoy it.

dcs.log would be nice to have

I guess it is related to the upper layer of our DRM. Why not with other software - you just happen not to use anything with similar protection.

Can you please send me your dcs.log from the interrupted session?

Because of the protocol change. Sorry.

Mods should've beed installed like that since 2.5.0. There was a thread about that. But since the old method still worked, nobody cared.

Absolutely safe. The hashes of what should be downloaded come from our servers (digitally signed of course). The source of data is not important after that - if it does not match the hash it will be rejected.

False.

That's because Speech scripts use static folder index now. Support for user-provided additional speech files is possible, but requires some rework of speech scripts. Will add this as a feature request.

I'll repeat: changes to the game install folder will NEVER be supported. You want mods - do it the supported way. Not enough docs? Ask! Need help? Ask. I guess these questions while perfectly valid are beyond the topic.

Yes. We have to protect our IP. Not from you, if you're asking. I guess you need docs, not the original samples. (However you can still reference the stock game samples in your new sdef files). We will post the docs, including the list of filenames for sdefs and samples a bit later.

Again, there're no changes to sound structure. There is a change in the packaging of the stock sounds. It does not affect proper mods in any way. Sorry, don't understand what you mean.

There's no new sound structure.

this is not possible. please, explain what you mean, post the logs proving your words and then we'll see what's going on here.

Modifications to the game install folder will never be supported. We have an official way to create mods which has to be used. Speaking of the sound mods specifically, there is Saved Games/DCS/Sounds/ folder - for test purposes/local modifications and Saved Games/DCS/Mods/resource/YourOwnModInASeparateFolder/ where you can have Textures, Sounds, whatever, in a separate folder, ready for sharing with others. If you are missing any functionality and or documentation, and the only way to make a mod is to modify game files, please ask, we will consider supporting mods for that kind of things as well. I'll try to post a more detailed info on sounds mods in a week or so. Thanks.

You can disable the sound rendering (and loading) with autoexec.cfg: sound.disabled = true However, with 99% probability it's not the problem.

THANKS for investigation. Will look into this.

The last record says 2019-12-23 01:41:52.253 INFO DCS: Screen: MainMenu so, technically it does start ok.

Please, attach the log written right after DCS fails to start.

everthing looks good, no errors. 2019-12-19 10:55:41.294 INFO DCS: Screen: MainMenu 2019-12-19 10:55:43.887 INFO DCS: Screen: Campaign 2019-12-19 10:55:48.834 INFO DCS: Screen: MainMenu 2019-12-19 10:55:49.825 INFO DCS: application shutdown Main Menu -> 2 sec -> Campaign -> 5 seconds -> MainMenu -> 1 second -> Exit. update your graphics drivers just in case.

C:/Users/<your login>/Saved Games/DCS[.openbeta]/Logs/dcs.log

dcs.log please

It means the IP:s are correct. Try pinging them. Also check the output of ipconfig on your server machine.