Yo, do you have any ETAs about routing for Serbian ISP's?It keeps randomly connecting to NY,USA.
on your account.riotgames.com/account page, what country/region shows? That's strange that you would route that way, unless your account's region is set to a US location. If that's the case, player support should be able to help resolve.
As for the 300 and kick out, that was probably during a couple incidents over the last day...there was a third party maintenance on top of it that knocked a couple people out of game over night, too .
This is a display bug introduced with the patch. The number includes client frametime on top of ping. Your actual ping should be the same as before the patch.
Actually, some people should be seeing some improvements as we added some improved routing from some isp's this last week.
so no patch for EU ?
cuz there is no April 31?? xD
We converted the date to metric
Out of curiosity, why don't game companies have a team dedicated to going to Google and just typing in game name cheats. Hell if you do it for a game like siege you get stuff thats like "Our software hasn't been detected since x time." It seems like the easiest way.
Our anti-cheat ops team does a more sophisticated version of this to keep track of the cheats available on the market. We generally find that the cheats that you can find from Google are low quality or fake but we keep an eye on them anyway.
Ever think of adding 2 factor or verified phone number to accounts that want to play ranked? Seems like that would be a lot more annoying to setup for each account after they get banned
I would love more account verification and security options. We have people working on it but I'm not sure what the current ETA is.
Do the cheat developers sell these hacks? Surely immediate bans are always better since there will be less impact on genuine players and the cheat devs will not get enough money to justify continuing to write cheats. Got to battle the cheat devs first imo - cut the cheaters off from their source. But, then again, I’m no expert in this so I don’t really know the dynamic between the cheaters and the cheat devs.
Will you consider implementing a shadow ban system where you only match detected cheaters with other detected cheaters to effectively quarantine them to "cheater lobbies" until they are dealt with in the next ban wave? Other games do this and it's a good method for getting cheaters out of games while still slowing cheat development.
I haven't been a fan of "cheater island" in the past because I always figured that cheaters would quickly figure that they've been flagged (different matchmaking queue time, different quality of matches).
It might be worthwhile if the quarantine time is short enough, for example if banwaves were coming every 12 hours, then maybe flagging the accounts for some sort of soft ban immediately would reduce the damage they do but not give cheat developers much of a head start.
Maybe I'm letting the perfect be the enemy of the good but I'd rather try to get to a world where we were banning all cheaters immediately on detection (which is only partially true today).
Are there more optimization patches planned anytime soon? You can see by the threads people are still getting poor performance
We're looking into performance at the moment. My change improved performance for some players but there are some other performance issues that we're investigating.
I don't think we'll ever be "done" with looking for optimizations though! We're hoping to always be making the game perform better.
Hi, any reason Riot Vanguard must rust even when the game is closed? Seems kinda invasive considering it's appeared after an update..
Vanguard has always been running while the game has been closed but we thought it would be better to give you a tray icon so you can see that it's running and exit it/uninstall if you like.
Vanguard has a component that runs from system startup to ensure that when the game (and the rest of the anti-cheat) starts the system is in a known protected state. This makes it harder for cheats to be loaded into the system in a way that we couldn't detect.
It's probably just nvidia settings shenanigans, super low LOD level.
This used to work in csgo as well to remove smokes.
EDIT: Just so that we're clear, this is super easy to detect and WILL probably get you banned, don't bother.
Yeah, I'm working with nvidia to figure out the best way to stop this kind of thing.
Definitely don't recommend people do this, like /u/Tsanummy says it's not hard to detect.
You still work at Riot? Sorry, really basic question but last I saw you was like forum posts in 2013. What have you been doing between then and before Valorant?
VALORANT for most of it :) It's been a long road
Mentioned in the patch notes but worth repeating: we're doing at least one more pass on the art for the minimap icons before launch.
I always wanted to avoid wood because I feel wood is the meme rank. I don't wanna steal that meme. Wood is player-made, and devs taking it feels real fellow kids to me
Sounds like https://www.reddit.com/r/VALORANT/comments/gafm10/valorant_client_not_even_starting/
What CPU do you have?
If that’s true then at least they can find the issue quick
1065G7
We believe we have a fix but need to validate internally. What manufacturer and model laptop are y'all using?
Hi u/002-Rain,
We fixed the hard-spike perf dips from 0.47.
However, client performance has dropped a bit on the average with the 0.49 patch (mainly GPU). It's a priority for us on the dev team to optimize and hold the line for better performance targets, such that you as players don't need to deal with framerate drops. Expect improvements in subsequent patches.
Hang in there with us!
- David
They have a few hitbox/reg issues IMHO. One real problem is some issue when players crouch. Really f**ks shit up.
Happy to say the crouch desync will be fixed next patch (~2 weeks)
Thanks for the video report - it's currently possible in beta to have animation desyncs on the equip animation of agent abilities (as you see here - server-side, her head is still in the full upright pose). We'll get it fixed soon, thank you!
There's a temporary fix you can do while we work on a more permanent solution: https://software.intel.com/en-us/articles/openssl-sha-crash-bug-requires-application-update
Set the OPENSSL_ia32cap environment variable on your machine to this value ~0x20000000.
It's related to a weird bug with OpenSSL and specific CPUs.
devtrackers.gg