c0ff

now.

Есть события onMissionLoadEnd, onSimulationStart, onNetMissionChanged И ещё много чего полезного - см. API/DCS_ControlAPI.txt

Ок, сделаем. На данный момент делается 5 попыток, каждая имеет таймаут 3 секунды. То есть максимальный пинг - 3000 мс.

Should work ok. As with any other crash, please, provide logs and crash-files.

Thanks.

Sorry for the delay. 1.5.5 is on Steam now.

В лобби приходит весь список совместимых серверов, но отображаются только те, от которых игроку пришли ответы. Если сервер не отвечает делается несколько попыток. Тип соединения выставить нельзя, можно поменять ограничения по скорости https://forums.eagle.ru/showpost.php?p=2509778&postcount=4

а что с ним не так?

В релиз ушёл отладочный код и строка net.use_new_fm = false стала отключать сглаживание ориентации. Так что строчку надо удалить. Понятия "доэктраполяторный вариант" не существует, потому что экстраполятор всегда был. Сейчас в релизе изменённая версия оригинального (старого). Если вас что-то не устраивает, пожалуйста, прикладывайте треки с демонстрацией проблемы.

Guys, I've made a silly mistake of reusing 'use_new_fm' parameter for other purpose and forgot about it. Right now this actually enables/disables orientation smoothing. So, please remove the line from your autoexec.cfg and everything should become perfect - at least the Teej's track is.

Interestingly, the log says STATUS: Shutting the torrents down... INFO : Kill timer set to 30 seconds... INFO : Torrents have been shutdown in time. INFO : Kill timer reset. as if torrents have shut down normally, however, it missed the "Log closed." line...

Can you please, repeat the test, after putting the attached file to the game install dir, right along the autoupdate.cfg and .dat files. autoupdate_dev.cfg

No problems. However it is much preferable have tracks from the 1.5.4. It was not in the previous version. Should work now.

Каждому у себя

Saved Games/DCS/Config/autoexec.cfg: net.use_new_fm = false

And it would be great if you can provide a short track for 1.5.4, highlighting the problems. Like this: start in the air, group and demonstrate the problem.

Just in case if you really need the old algoithm, Saved Games/DCS/Config/autoexec.cfg: net.use_new_fm = false

Yes, the netFM was reworked to combine the smoothness of the old code with the robustness of the new one.

Hope so, please check the today's update.

Clocks are synced for all players in the same server. With non-zero pings the server, indeed, can only send old position data, or better to say, it sends current positions, but when clients receive them, the data is a bit old. So, a special netFM extrapolates the positions of planes, effectively predicting where a craft should be, based on previous positions. When a craft flights straight the predicted position practically matches the real one. In turns - the sharper the turn, the bigger is the error between the predicted and 'real' position - and since it depends on ping, it is slightly different for all players. What we are changing/tuning currently, is this extrapolation (prediction) algorithm, to make it more robust and, err, predictable (no pun intended) in the modern network conditions. So, the missile accuracy should actually improve a bit, not to get worse. If it has really become worse, something is not right in the missile code, not in netFM. We'll take a look.

please, post the client's log as well. thanks

you have Mods/tech/ns installed in the game folder - these require to be signed. Move the mod to Saved Games/DCS/Mods/tech and you'll be OK.

do a Repair

These logs are from the year 2015. Do you happen to have more recent ones?

Something on your side prevents HTTPS connection. You may put the attached file into the root folder of the DCS, where the autoupdate.cfg is. The file autoupdate_dev.cfg has this content: { "no_https": true } autoupdate_dev.cfg