Valorant

Valorant Dev Tracker




08 May

Comment

Originally posted by Dwyer0022

Sorry had a slight delay but the game loaded up without a problem. Will update my main post as well to let people know. I seriously appreciate it Nemi thank you! And I’ll cancel my ticket.

<3 thanks man. Appreciate your patience. Enjoy!

Comment

Originally posted by Dwyer0022

Thank you. I’m sorry if I seem bitter about this as I don’t intend to be. I will update this post if it fixes my problem.

Any luck with the update? If not, let me know. I'll DM you and we can figure it out together.

Comment

Originally posted by I_Fap_To_Witch_Mercy

This fixed the issue for me 😄

Thank you for the confirmation!

Comment

Originally posted by Dwyer0022

Anyone getting vanguard not initialized? I'm assuming it's got something to do with this release?

Update: Riot has fixed this issue today 5/8 for a majority of people. Thanks to the team for sorting it out.

Vanguard is in a closed beta state as much as VALORANT is. Building an entire Anti-Cheat product from the ground up isn't easy. It'll take some time to get everything completely right.

For this specific issue, we've deployed a fix. Please try to patch VALORANT and Vanguard will update. You will need to reboot your machine in order for the fix to fully take. This requires a system restart, not a shutdown. If this fixes your problem, please close any player support tickets you have open. Thank you!

Comment

Originally posted by [deleted]

I literally see vanguard on the taskbar running and its saying not initialized, man vanguard broke the f**king game

A fix was released just moments ago. Thank you for your patience.

Comment

Originally posted by AdamAk123

Thanks for the feedback and I was't trying to spread misinformation or anything like that. When watching the stream it looked like it legit worked. And Dafran wasn't joking, he legit thought it worked which is why he went and tested afterwards. Sorry for any inconvenience this may have caused

Haha yeah, no worries. Always good to try to escalate issues. Now there's a few news articles about it that are missing this context :(

Such is life

Comment

Originally posted by weju

Same problem but with MSI MEG Z390 MOBO

Going to DM you some questions.

Comment

Originally posted by N4zarus

Same issue here and I'm running Asus x570 crosshair VIII hero

Going to DM you some questions.

Comment

Originally posted by Nosyok_

Same issue but using ASUS Z370-e motherboard

Going to DM you some questions.

Comment

Originally posted by k1ngheezy

nope. same vanguard not initialized issue. msi mobo, logitech g pro mouse, 1080ti,
i7- 5930k, ducky keyboard.

I DM'd you with some questions. I'm confident that the fixes I'm working on will fix issues that folks on ASRock motherboards have, but not sure about other configurations.

Comment

Originally posted by king_manu14

Are we doing to see a reduction in Vanguards aggression before launch? I got a drop and would love to play but i DO NOT feel comfortable with a company owned by tencent having 100% access 24/7 upon startup

Yes, Vanguard's aggression was significantly decreased yesterday.

https://twitter.com/PlayVALORANT/status/1258493180510519296

Comment

Originally posted by Attackerby

This patch broke Vanguard for me. Was playing the last few weeks and now getting a Vanguard not initializing error. Edit: The later update corrected it for me. My game is working now.

Hey folks, we're looking into this one. We have a good lead. Is anyone here using ASRock motherboards?

EDIT: Reached out to a couple of folks. This issue is more widespread than just ASRock motherboards, but I've gotten confirmation that what I'm working should unblock most people. I'll update this when a fix is deployed. ETA is a few hours. Thank you for patience.

EDIT 2: A fix has been deployed. Please try to patch VALORANT and Vanguard will update. You will need to reboot your machine in order for the fix to fully take. This requires a system restart, not a shutdown. If this fixes your problem, please close any player support tickets you have open. Thank you!

Comment

Howdy,

That graph definitely isn't normal. Each graph point is 1/10th of a second. You can see in some cases you're losing ~19% of your packets in those periods. This would likely lead to enemies sometimes being in the wrong position or in more severe cases you might rubberband back to a previous position. Your shots are likely to be delayed as well.

Really you want to see the packet loss graph have 0 spikes in it if your internet is working properly (or maybe some smaller spikes every now and then, but really you should expect to see 0%).

If you're on Wifi you might try a wired connection. If not, you might need to restart your modem or router. If the problem persists you might try reaching out to player support or even your own ISP to troubleshoot the issue further.

I had a problem like this earlier today and was able to fix it by fixing some loose cables on my router.

Comment

We've got a lot of work in flight on the dev team right now to improve performance - 8 engineers working on a collection of different tasks - we hope to see some improvements come out in patch soon!

Thanks for hanging with us :)

Comment

Thank you u/Ksycht for sharing the video!

The timer logic is one of the oldest pieces of code in the game (4+ years even); it was alive back in prototype stages, and we never quite got around to giving it the love it deserves.

We have a ticket tracking the work on our dev team, and will hopefully have it running smooth as butter soon. Stay tuned!

- David

Comment

Originally posted by hypnomancy

Been hearing about a lot of people having similar problems. It's absurd.

As in people having this exact same problem where they see a lot of processes running called RiotClientServices.exe and RiotClientCrashHandler.exe? If so please tell them to contact me so I can get their logs and investigate. If I don't respond, please also tell them to contact player support since they will collect logs from them and then forward them to our department. I haven't seen any other reports besides this thread. Any help is appreciated.

Comment

Originally posted by Smorgos

And its called Vanguard

On first glance, this seems like it could be a bug with our login screen.

Comment

I have reached out to you for your logs. I haven't seen this one before, any help you can provide us triaging this issue would be greatly appreciated.

Comment
    /u/Pwyff on Reddit - Thread - Direct

Originally posted by freel0ad3r

What'd you expect? There's going to be kind and constructive feedback, and you're going to receive angry, unnecessary feedback. That's just the way it goes. Don't cry about it.

I for one have been experiencing my share of issues with vanguard and I generally don't support softwares that just starts on pc boot, however I'm hoping it will improve in time.

I'm not crying about it but I also don't accept lack of empathy as a standard of the internet. This is me establishing boundaries and communicating boundaries: don't be an asshole please, let's have a constructive conversation :)


07 May

Comment

Originally posted by MoonDawg2

Koal I haven't been able to get an answer from the latam people, but at the moment there is some heavy packet loss flactuation in the latam server for people in Chile. Around 0 to 50% every single second and seems to be an issue with pretty much every ISP

No idea who I can give this info to, but maybe you can pass it so they can fix it asap. Server was working fine before they did the routing fix for Argentina, so the issue seems to come somewhere from there

Thanks for the report! We've got some really great data where we track packet loss / latency to our servers and try to track which spots are having trouble. It's going to take a bit for us to get all of the routes ironed out to start, so I think this is likely expected.

We do already have all the data we need on the back-end, so no need to worry about reporting it.