Development discussion. Logged to https://ddnet.tw/irclogs/ Connected with DDNet's IRC channel, Matrix room and GitHub repositories — IRC: #ddnet on Quakenet | Matrix: #ddnet-developer:matrix.org GitHub: https://github.com/ddnet
Between 2022-07-24 00:00:00Z and 2022-07-25 00:00:00Z
or maybe it did. Its way better with vpn the few short lags left are probably something else then
TsFreddie
and can we have server list subscription? like we can let people subscribe to a url of ours so they know we hosted the server on the list. like a customizable tab.
Has anyone seen a bug where Cur and Prev snapshots have the same m_Tick / are the same? (it results in GameIntraTick() being "inf" and then it goes downhill from there, with the game freezing in the end)(edited)
I guess it's been enough of a time for people to get used to it, should we poll around to see how much interest there is for a replacement for the old stars?
I still do not understand why the snowflakes could be used as freeze time indicator
19:12
Could not
Learath2
I guess it's been enough of a time for people to get used to it, should we poll around to see how much interest there is for a replacement for the old stars?
That's what I'll make, big snowflakes imitating old stars and the people that can't adapt at all can use a texture which replaces the snowflake with a star
If a duplicate snapshot is received (for the same tick), end up with the same snapshot as both Cur and Prev. This results in GameInfraTick returning "inf" and results in "NaN" downstream in a few places, getting the CollLine logic stuck.
Some debug info (tcpdump, gdb, perf): https://gist.github.com/Fireball-Teeworlds/ad0016d2551a2e4d4cb5691023493856
Apparently this doesn't really happen in the wild, unless you have a buggy network stack. In which case it happens frequently enough to pin...
If a duplicate snapshot is received (for the same tick), we add both to the SnapshotStorage and end up with the same snapshot as both Cur and Prev. This results in GameInfraTick returning "inf" and results in "NaN" downstream in a few places, getting the CollLine logic stuck.
Apparently this doesn't really happen in the wild, unless you have a buggy network stack. In which case it happens frequently enough to pinpoint the issue :D