LAG, INFANTRY LAG, INFANTRY DEATH LAG, CRS WTF PREDICTOR CODE GRR!!! - MEGATHREAD

[waver25]

Quote

 

UDP PACKET COMMUNICATION FOR INFANTRY

Our dev team is currently working to bring you the best possible infantry experience we can. While we improved close quarters combat through our "Infantry Predictor" updates (1&2), we're still not satisfied. UDP is replacing our current TCP method of communication. This will improve responsiveness and decrease latency across the board. Infantry is the core of all battles ever fought in any conflict, our game is no different and we must have outstanding performance.

This is intended to be released prior to Steam, as it is a heavy requirement for us deploying onto Steam successfully.

 

In an attempt to get all the threads regarding infantry lag , be it death lag , or warping , into a single place. The QA team will be merging some discussions into this mega-thread for use going forward. If you haven't already had a chance to read it yourself , go check out the 2017 Development Roadmap [right hurrr]. I think the part below is really one of the most exciting personally.

Check out the megathread by clicking [right hurrrr] or from the snippet below

 

[waver25]

 

[waver25]

Alright. So ... netcode3 is out with the release of 1.35.8...

but wait CRS, you haven't turned it on...wtf?!

We'll be releasing a 1.35.8.1 hotfix this week and be taking our time again with enabling netcode3. Once the patch is out we'll probably enable netcode3 some 24 hours or so after the patch and after we're confident things are stable. This will help us isolate any server issues if things go wrong once we turn it on.

The DEV team was able to nail down the issue that cropped up during last Tuesdays test on the live server. We've already gotten some very positive feedback from our Closed Beta Testers who shall remain anonymous (although some post quite frequently in this very forum and are ermmm..rather vocal).

It's coming!