Good morning, any unity experts at hand? (and Arcore)
(Also, no I cannot write specific questions that I have on the mainsite; I don't have specific questions, I'd more like to discuss and further my understanding of the subjectmatter if anyone has some time)
@person27 in general: UDP is faster than TCP, because TCP does need to guarantee packet delivery. That means each sent packet has an overhead to make sure it arrived, or it's resent - IN ORDER. Thus your network traffic will stall (okay for websites, not okay for games with miniscule updates in nanosecond ranges)
actually that's the whole point. You usually don't want TCP features for gaming network traffic. Or at least not for every packet.
E.g. a general usecase is that the game for each player sends a packet with every action a player takes to the server. The local computer will calculate your own action's result; the server will calculate and verify the actions it received and send them out to everyone. You won't want anything remotely like TCP for this - imagine having a complete signalroundtrip for every single one of these packets(?)
Where you want TCP is somewhere once every 100ms or even once a second (really depends on your game, etc..) where you send out the whole seralized gamestate to all clients so they can update and make up for lost packets
Why does Unity hate my vector icons so much? I solved the issue with antialiasing, and now a panel with only 10 icons lags when one of them changes scale (lags increase as number of icons increases)
I don't know enough about how unity decides what to render together, but to me it sounds like they are all part of the same texture(atlas) or something
@dot_Sp0T Mmhmm, I did lots of research. TCP and UDP seems okay if not being used at the same time as TCP will cause UDP to drop packets due to its increase-decrease latency correction thing. I'm failing or sending redundant packets if correcting every second. Actually I queue per-client so I won't send a message to all clients normally, except in e.g. matchmaking.
@trollingchar again, these are different use-cases. Although I wouldn't even then really use a mechanism that ensures packet-delivery. I'd rather implement a mechanism that polls the user-state from the server and either A) overwrites local state ; or B) highlights discrepancies and automagically resends the requests to the server
Assuming that the client is the only actor and the server is mostly a data-repository, a simple rule of thumb might be:
Client sends data to server (any actions/interactions) -> UDP Client requests data from server (gamestate, ...) -> TCP
Regarding the skillpoints example: Naturally this scenario lends itself to the use of TCP connections. It's something that takes time and needs to be correct. Similar goes for monetary transactions.
What you send per UDP is stuff like movement information in the big 3D world, etc
