c0ff

What's an actual ping? ICMP requests are handled by the OS. The server list shows effective pings - the time between DCS client sending a request and receiving the reply, including all DCS server processing (these requests are of the highest priority, but still...)

It can miss a local modification when neither file size nor file modification time did change.

dcs.log please

Were there any requests?

Uff, I'm very glad to hear you have this solved now! Those "magical" problems with computers.... Thanks for reporting!

Wow! I'm glad it's all good now. Thanks for reporting back!

https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

registered a feature request.

https://forums.eagle.ru/showthread.php?t=98014&page=12

Hi! Please, try disabling A-10C, Ka-50, and Flaming Cliffs modules and rerun the mission. You can do it by temporarily renaming Mods\aircraft\A-10C\entry.lua Mods\aircraft\Ka-50\entry.lua Mods\aircraft\Flaming Cliffs\entry.lua files into smth else.

Why? when this: DCS_updater.exe install PERSIANGULF_terrain is a much safer bet.

Given their Path's are properly set up in the registry (which is done once by the installer).

Which CPU model do you have, exactly? If you can, please send me your CPU-Z info. Via PM if you like.

It will be nice to see the list of offending files. Also, 1) have you tried repair with cleanup? 2) have you any usermods installed in the Saved Games?

A mystery... Router port-specific firewall rules, may be?

logs logs logs logs...? Unlikely. It's absolutely the same.

The sounds in 2.5.5 are not packed and thus do not have any checksums. The "invalid gzip stream" error comes from WWII Units module, which is packaged exactly the same in openbeta-2.5.6 as in the release-2.5.5. So this error may happen in both builds for you, and most probably it does, you just don't use these units and thus never noticed the problem. And the sound issue is immediately noticable.

From the log INFO SOUND: Added sound path: Sounds INFO SOUNDER: Loaded 207 packed sounders. This is good and how it should be. However, this is not: ERROR EDCORE: loadFilePackage() failed: invalid gzip stream ... ERROR SOUND: can't load proto file "/sounds/24/sdef.tar:Aircrafts/FA-18/Cockpit/Betty/fuel low.sdef": /sounds/24/sdef.tar:Aircrafts/FA-18/Cockpit/Betty/fuel low.sdef: unexpected end in precompiled chunk ... These are things that are non-conditional and should just work. More over, one file failed, while others in the same package did not - looks like RAM or disk (cable?) fail.

Still, this is a dcs.log from my openbeta install: INFO SOUND: 0: ID: "{0.0.0.00000000}.{26b17728-2f99-4d1f-a95f-c797ec7fcfc2}", Name: "DELL U2415 (NVIDIA High Definition Audio)" INFO SOUND: 1: ID: "{0.0.0.00000000}.{a3908766-7b5e-48e5-bc83-a348b916e89b}", Name: "Speakers (Realtek High Definition Audio)" INFO SOUND: Added sound path: Sounds INFO SOUNDER: Loaded 207 packed sounders. Note the last 2 lines. They are missing from your log, meaning that main sounds are not loaded by the engine. Now the question is why...?

Yes looks correct. You are supposed to create the file if it does not exist.

Sure!

Your log is missing the line SOUND: Added sound path: Sounds Right after the audio device list. Something is wrong with your install.

A couple of questions on your log: 1) SOUND: 0: ID: "{0.0.0.00000000}.{03434be1-80c2-400f-9124-43cf3567a817}", Name: "Audio numérique (SPDIF) (High Definition Audio Device)" ... SOUND: Opening default audio device Isn't SPDIF your default audio device by any chance? 2) ERROR SOUND: source_add(host:WorldFX, proto:SonicBoom, alt_proto:): can't find proto Do you happen to have Sounds/ folder along with Sounds.edc/ one?

I'd also suggest fixing the Path in the registry HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World [OpenBeta]\ If you install several copies, the updater tries to pick files from the ones it find in the registry, where appropriate. This reduces DL traffic.

This should not happen. Nor anything should require admin rights, unless it asks explicitly (like the updater does). autoupdate_log.txt from the install folder AND autoupdate_templog.txt from AppData\Local\Temp\DCS.openbeta\ will be nice to have.