Beta launcher will work
We're currently investigating. We saw a large network drop and there maybe be connection issues to the vanguard service. The issue is showing up as a vanguard error, but it's a larger networking issue. We have engineers actively reviewing now.
It’s happening to A LOT of people after the latest Vanguard patch, or whatever the heck you guys did.
i7 6700k 1080Ti ASUS Z170 Motherboard 16GB RAM Corsair K95 Platinum Keyboard Logitech G502 Mouse
Also, just take a quick stroll on the sub....
https://reddit.com/r/VALORANT/comments/ge816a/vanguard_preventing_mouse_input/
https://reddit.com/r/VALORANT/comments/geaexp/can_we_revert_the_latest_hotfix/
https://reddit.com/r/VALORANT/comments/gea5l8/valorant_vanguard_issue/
https://reddit.com/r/VALORANT/comments/ge9phq/vanguard_not_initialized_error/
I know the team is reviewing this to see how widespread issues. Do you run any virtualization programs for keyboard and mouse?
Nothing because like iCue and Logitech GHub to mess with keybinds and my DPI? It’s blocking all that.
And the drivers for those are up to date?
The complaints are under investigation at the moment, unfortunately I don't have a lot to go on yet, but hopefully we'll be able to have your experience sorted out soon.
What about the damn vanguard update that is blocking mouse and keyboard usage for a lot of us??? Why are you all silent about that.
I'm not familiar with that issue. What's your set up look like? Is there an error that you're getting when it happens?
Restarting the pc should fix this. It's possible there's an old vanguard version that's not patching properly. if the restart alone isn't working, can try uninstalling vanguard from the system tray and then patching/rebooting.
Restarting the pc should fix this. It's possible there's an old vanguard version that's not updating properly for some reason. if the restart alone isn't working, can try uninstalling vanguard from the system tray and then patching/rebooting.
We're still investigating other potential causes, but that's our best guess at the moment
Looking into this
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.
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 .
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.
so no patch for EU ?
cuz there is no April 31?? xD
We converted the date to metric
Thanks for keeping us posted.That means people will be able to get past loading in the next little bit?
I believe so. If it's still ongoing, that's of more concern.
friends in game say i'm in range when i'm trying to login the game and stuck on loading screen?
These should clear over time. We are still reviewing this incident for lingering impacts.
Now its letting me Log in, but im stuck on the Loading Screen.
resurgence of people logging in may have briefly locked up one of the services. We've scaled it up to deal with the volume.
Working on this. Should be fixed momentarily.
Fixed now...sorry about that! A normally safe configuration change had an unexpected result.
Thanks for letting us know! People were spreading you guys had to kick people from beta for server stability... so I and I'm sure many others were very worried! haha
We are not removing players due to stability stuff...we're fixing the stability issues. Only players getting removed are cheaters and excessively toxic players.
Working on this. Should be fixed momentarily.
Should be opening up now. We identified some potential scaling concerns while validating the patch that we didn't feel safe until we had them solved. Those unfortunately added unplanned for time to the deploy.
We believe this should be resolved now. Thank you for your patience!