Hopefully this was the main source that cause inconsistencies from game to game because it sucks to not know what was causing it. Hopefully, this problem can be replicated with many different configurations and not just an outlier.
I really hope so too! We're super concerned with this, and finally having a way to potentially find fixes for this problem is really exciting to me. I would love to finally fix this chapter of "weird netcode."
Also in general, is there any chance yall have fixed tickrate servers as opposed to variable tick(unless the changes in tickrate im seeing are artifacts of a faulty netgraph) ?
Our servers are trying to run at 128-tick (and we have some sub-systems that are forced to run at 128-tick, like physics and movement, no matter what the actual tick rate of the server is). However, if we're unoptimized or have issues, we can't force 128 tick if we hitched and dropped lower to a lower tickrate.
Hopefully this isn't fluctuating significantly in mid-round. We're aware of end-of-round and buy phase fluctuations and we're not too worried about them right now, since there's no combat.
Would this maybe help a bit?
Windows 10 (and up): Windowed Fullscreen should provide the same (or better) performance compared to exclusive Fullscreen.
I believe we were using an incorrect legacy call for Windowed Fullscreen that introduced input latency, and I'm not exactly sure if we've addressed it or not, but it is something we will be fixing at some point.
Congrats! That’s a great Sheriff skin. Probably my favorite one after the Omen one.
Wow, thanks for reporting this. We're currently investigating and trying to understand the general issues everyone's been feeling around inconsistency in game feel from game to game.
Alt-tab as a trigger is something that jogs a few gears in our brains in potential causes, including a couple that we were already going to investigate, but helps in attributing a direct cause, and is a potential explanation for how netcode feel can just simply vary game to game. We're still going to investigate other potential causes, but this has me a bit more hopeful in that we're going to be able to find the crux of the issue and address it more quickly, now that we have a way to potentially trigger it.
We're getting our QA to get some reps on this and help us understand what's going on with netcode when someone alt tabs, and were already getting diagnostics for the parts of the system we think are going wrong. We don't have anything concrete to share yet, but we are definitely taki...
Read moreThis is so cute! I love that little snowman!
Looks incredible <3
Is....that...cypher?
Call RIOT they have next lore clip here.
Write that down! Write that down!
very cool!
Read moreI appreciate you coming back to this post to provide more info!
Thank You, I didn't actually expect such detailed answer!I'm happy you're aware there's some kind of problem and decided to make it a priority to find it and fix it. It only confirms that Valorant would get better and better.
I'm praying you'd get enough of information about what's going on and manage to fix it as soon as possible, at best this year(praying!).
If I had to sum up my experience before patch 0.50 - Have you played Counter Strike Source? Models there 'die' pretty responsive way, right? I know it's also because of the engine, but forget about it for a second.
Or If you watch one of commercial videos about Valorant like the one about Yoru or Alpha state of 'Project A'(with known 'precise gunplay) - in both of those cases the registration and movement feels on 'point', which no longer felt this way after 0.50Idk how much of a 'hint' it is, I trust y'all abou...
We’ll plan to share back findings once we wrap up the investigation and/or have potential changes going out. For now, we’re heads down and focused on the work.
devtrackers.gg
