It would be mainly custom training, sometimes I would even sit there idle and the game would eventually crash. But mainly when joining matches.
Thanks!
We're going to try and reproduce this issue so we can get all of the necessary information to fix it.
Sorry about the issues!
I have so many questions about your monitor and how it's standing... I don't know where to begin...
Awesome! Glad you found a few.
So to verify, you're saying that the speed of the impact point matters, and thus longer cars do hit harder, but the difference is only minor due to the way physics are handled uniquely in the game, correct?
Yes, very minor. We basically just use the physics engine for resolving intersections. Restitution is mostly disabled (between the car and ball).
then why is every other ping a multiple of 4
Ping for other players are still a multiple of 4 (to save bandwidth). Your own ping is uncompressed.
Very cool! Watched the GDC talk. So it doesn't reduce the input buffer below the standard amount (e.g., 16ms) but it increases it and speeds up the simulation when it sees there are connectivity issues/loss of input (before bringing it back down when issues subside). Would you say it's safe to use STS or CSTS even if you have a good connection? For when we do run across connection issues?
It's definitely safe to use, just not to the point yet of saying it's recommended for everyone.
I will have to check with /u/Psyonix_Cone on the standard buffer size as of this update.
Do the new STS and CSTS options add a little input delay ("input buffer") to help with connectivity issues? Kind of like how v-sync adds display lag when it has to wait for the frame to be fully rendered before displaying it? Is that why it's better to stick with Legacy if you don't have connectivity issues?
All models use an input buffer. The new options handle maintaining it differently, similar to how Overwatch does it. (See Tim Ford's GDC talk around ~25minutes in for more context on their approach)
The Overwatch approach involves very very subtly slowing down or speeding up the client's game simulation to maintain an input buffer size that can handle variation in network traffic.
They definitely make it sound like you want to stick to Legacy unless you have bad connection.
Not exactly. The new methods are just that - new - so we just didn't want to oversell them until people get some hours into testing them out in a variety of real world conditions.
The new stuff is closer to how Overwatch does latency mitigation, which has some advantages over the Legacy model in theory, but real world is always different.
Any chance of one of y'all giving a GDC talk about this? That last one from /u/Psyonix_Corey was eggcelent.
https://www.youtube.com/watch?v=ueEmiDM94IE
Also worth watching Tim Ford's talk on Overwatch architecture (Network stuff around 25 minutes in)
You are correct, the ends of longer cars have a higher velocity than shorter cars when dodging. However the bulk of the impact force between the ball and the car comes from the extra forces that we add after the collision response is calculated by the physics engine, and these extra forces depend entirely on the relative linear velocity between the car and the ball. Angular velocity does not factor into the extra forces.
Slick!
That's... incredible.
Thanks Corey! I copied the following from my edited comment, but just trying to throw the idea out there. I hate to complain about something without trying to think of a possible solution.
One of the suggestions that I had was to reset your casual MMR to whatever your highest MMR was in a competitive playlist at the end of the previous season. It'll get inflated again probably, but at least it would reset somewhat regularly.
Our tentative plan is to 'squish' the curve to maintain everyone's relative placement, but reduce how extreme the outliers are on the top end numerically so it plays nicer with Matchmaking.
It will probably be nonlinear so we can account for the extreme edges of the MMR curve without putting them right back into a situation where they have few valid opponents in queue.
Can you please do something to re-calibrate unranked MMR? I have over 2200 unranked MMR and my highest actual rank is C3. I can't find casual matches anymore without waiting at least 5 to 10 minutes.
Edit: one of the suggestions that I had was to reset your casual MMR to whatever your highest MMR was in a competitive playlist at the end of the previous season. It'll get inflated again probably, but at least it would reset somewhat regularly.
This is something we'd like to address soon. I don't have a firm timeline on it right now to give you yet.
Come together! Seriously, though, thanks for the kind words. :)
“wHy DoEs ThE oThEr TeAm AlWaYs GeT bEtTeR pOwEr-UpS, wHy DoN’t I eVeR gEt SpIkEs???”
Thanks. Someone already linked that to me elsewhere and for some reason I thought it was an older comment. Oops!
Still, my question extends beyond that response.
Will they be adding a "Party up?" quick chat? Will we have to just send them an invite and hope they respond? Does this special waiver apply to players across platforms who are in our club? Do these waivers apply to private matches where it would be implied that players communicated outside of the game in some way already?
This also seems to be indicative of the usefulness of a "stay as team" button that Psyonix did mention they would look into once RocketID matured a bit, in which case I'd be curious how that would work in a 3v3 where only one teammate agrees.
u/Psyonix_Corey I guess you'd be the guy to ask.
Lot to unpack here, here we go:
Pog
Solid work!
devtrackers.gg