About netcode
For those that don't know already, Battle(non)sense gives pretty good explanations regarding netcode: an older but well detailed article: https://www.pcgamer.com/netcode-explained/ video channel: ...
Forum Discussion
@Fr3dY2 These things are rarely a choice. Compatibility between the engines and systems used for big projects such as a triple A game is a huge issue, devs are usually stuck with what works. Switching to other engines or systems or writing code from scratch can take many years and is not viable.
But does TitanFall 2 suffer the same issues then?
It hurts seeing Apex at the top of the delay comparison screen 😢
- @Fr3dY2 I think Apex is using pretty much the same servers Titanfall 2 used. For Titanfall 2 they were good enough, as there were way less players in a certain match, also less stuff to track, much smaller maps, less sounds, etc..
The comparison is also not very balanced. Overwatch for example has only 12 people on a map, it doesn't have inventory to pick items, most of the weapons are hitscan and have a low firerate, movement is a bit slower, maps are smaller, there is less detail on the 3d models. A 60-player BR in Overwatch, on a larger map, would probably get much closer to Apex's and Blackout's values.Let them hire someone at Epic to implement Fornite's netcode then... there are 100 players per match ☹️
Damn...so even gibraltars coding is thicc? 😢
