c0ff

It is monotonic. It gives the (fractional) number of real time seconds passed since the process start. Not affected by OS clock adjustments. The documentation needs a correction, indeed. Thanks for pointing this out. The resolution is at least 1 us (1 microsecond, 0.000001 sec).

The proper API is Sim.getRealTime() or DCS.getRealTime() (Sim. is the new API namespace, DCS. is its alias).

Hi Bucic! Nice to see you! Your report is sufficient enough, thanks! DCS uses our own proprietary sound engine.

This is a drawback of a solution for another problem, caused by aliasing in listener (camera) position from the sound engine perspective.

Most probably the virtual camera reports invalid veloicity value, which makes the sound engine to apply an unnecessary Doppler shift. FYI we don't use WWISE.

Thanks! This is some weird Windows issue, because DCS sound engine explicitly asks for the device to be open in AUDCLNT_SHAREMODE_SHARED mode.

DCS has 2 indepentent audio ouputs: one for World sounds, another one for Headphones. The latter always runs in stereo (2 channel) mode. You can select 2 different output devices for them in the options, if you want.

You can try it with this line in the autoexec.cfg file: sound.driver_name = "spatial" EDIT: it's pretty taxing on CPU because Windows Spatial Sound requires rendering audio to 17 independent channels. 16 directional and 1 LFE.

I think we've found the cause. The fix is being tested internally. Many thanks to @Flappie for the dedication, methodical testing and very quick feedback!

Dear guys, thank you for checking with Google's DNS servers. It confirmed that the issue is with C-Ares library (a DNS resolver) which we used in this update. It turns out it has problems with some OS/firewall/ISP/router combinations. We already disabled it in the internal version and the fix is going through our release pipeline (testing, merging to production, testing again ...)

.\bin\DCS_updater update 2.8.3 will update to the most recent 2.8.3.xxx version

That's possible to implement. Noted.

Hi! Sorry for the delay. We fixed the installer some time ago.

We found out there was one more problem, apart from incompatibility with LG Screen Splitter and we solved it as well. Next openbeta should be ok.

There's a more than one problem with the start. On of them is LG Screen Splitter software. We're working on a workaround atm. All other problems seem to be already resolved in the internal builds.