Rocket League Dev Tracker

My friend uses the Nintendo Switch and I use PC, but for some reason we are unable to crossplay in a private match. We both have cross platform play enabled in game, so that isn't the problem. We've both tried to create a lobby and connect to them, but each attempt results in the "Unable to find server" dialog. Is this due to the recent hotfixes or has crossplay been broken between PC and Switch?

Oh but it is...

Inconceivable! https://www.youtube.com/watch?v=ZSSW3YNgzNQ

We now send the rotation as a quaternion using 18 bits per component instead of 16. Implementation learned from https://gafferongames.com/post/snapshot_compression/ "Optimizing Orientation" Here's snippets of the code for deserial...

We fixed this. Thanks for pointing it out!

That brain is so chill. 🕶⛱

Pro-te-YES! 🦑🦈🐡🐠🐟🐳🐬🦀🌊

Soon!

my b

You won't believe how he does it! (Step 7 will blow your mind!!!)

Thanks for playing! <3

Looks amazing! Nice one, OP :D

<3

Ooh nice concept, nature is neat!

If that is true, then does that mean the server accepts inputs from some players later than others? That doesn't sound too fair to me. Or does your statement mean, that the client simulates even further ahead to create a bigger buffer for the inputs?

What it means is, if a player is averaging packets arriving anywhere between 100 and 125 ms of latency (25 ms of jitter), they have (ideally) 25ms of input buffer to ensure they always have enough inputs in the buffer to last until they next packet comes in. This keeps the input buffer as small as possible so we aren't adding too much extra delay to processing their inputs.

If another player has very high jitter (packets taking anywhere between 100 and 150 ms), they need a 50ms input buffer to handle the 50ms of possible lull between incoming packets.

Great video as always! I wanted to clarify some things mentioned in the video:

• Input buffer size is not the same for everyone. It tries to grow or shrink depending on network jitter (variance in latency).
• We allow up to 10 frames of input history to be sent on every outgoing packet. We don't send inputs that the server has already confirmed. You were probably only seeing 4 inputs because you had a low ping and the server had already confirmed the older inputs. If you increase your ping, you will see the game sending more inputs per packet.
• The networking options currently don't work because we chose to disable them via the backend while we narrow down server issues stemming from the last update. The networking options will be re-enabled shortly after the next update goes out.
• A fix was just checked in to our dev build a few days ago that coincidentally fixes the scoreboard ping issue too. The issue you are seeing is not the actual ping going...

Hello! Thank you for this investigation. The heavy car issue is an elusive beast and we appreciate any community help in resolving this matter. Connecting to PsyNet with high latency should not have any effect on player input, but I'll try it out on Monday to see what happens. To aid in your investigation, here are some points regarding things mentioned in this post:

• PC has only been using websockets since April 24. Prior to that communication with PsyNet has been through stateless https requests. So unless your issues just started in the last few days, I wouldn't assume websockets are the culprit.

• ConnectionQualitySave just tracks your latency, packet loss, etc to the game servers over multiple matches. This information is used to display a pop-up linking to a support document if a user has recurring connection issues. It is not used to affect your connection settings.

• The PsyNet.ServiceCalls metric is just metrics we record that me...