Dang it, uploaded the logs to my google drive instead.
https://drive.google.com/open?id=1VfN8Lx45OLUmXihnLJmIAqFYY2FJwEVt
Understood about the update. Had no problems last week pre and post vanguard update. Disconnect errors did not begin until 0.50 patch was installed. Hopefully the logs help!
Looks like a server error on our side, I'll escalate it to our infrastructure people.
There were about 5 files in the logs folder so I zipped them up and uploaded them. To further add to the report, I never had this bug before the 0.50 patch. Also tried uninstalling and reinstalling the game and vanguard but still got disconnected with the same error.
That link 404s for me :(
Vanguard didn't update along with 0.50 (it updated last week on its own) so it's probably not a 0.50 specific issue.
• Region: NA
• Type of Bug: Vanguard kicks me out for every 4 minutes
• Description: Vanguard Anti-cheat has encountered a connection error.
• Reproduction rate: 10/10 (happened 10 out of 10 times)
• Steps to reproduce: Try to reinstall Valorant and Vanguard
• Expected result: I won't be kicked out
• Observed result: Still got kicked out
• System Specs: Intel i9 Processor, Windows 10, Nvidia Graphics card (2080)
If you upload your Vanguard logs somewhere (they live in "C:\Program Files\Riot Vanguard\Logs") and message me a link I'll take a look.
My best guess is some sort of connection issue to our anti-cheat servers?
I have been kicked from games as well, same error, can confirm. Never got kicked a single time pre-patch
It's probably a coincidence since nothing Vanguard related changed in this game patch (Vanguard updates on its own schedule). Let me know if it keeps happening though.
Region: NA
Type of Bug: Vanguard kicks me out for every 20 minutes
Description: Vanguard Anti-cheat has encountered a connection error.
Reproduction rate: Happens every 20 minutes or so
Steps to reproduce: Kept trying to play
Expected result: I won't be disconnected
Observed result: Still got disconnected
System Specs: Intel i5 6600K Processor, Windows 10, Nvidia Graphics Card (980Ti)
Copy-pasted from the last person who reported this bug:
If you upload your Vanguard logs somewhere (they live in "C:\Program Files\Riot Vanguard\Logs") and message me a link I'll take a look.
My best guess is some sort of connection issue to our anti-cheat servers?
• Region: EU
• Type of Bug: Vanguard Anti Cheat Error
• Description: I started to play from first week of beta and i have this issue. I cannot play a match normally because i get error all the time randomly. I tried to reinstall the game and anti cheat multiple times. Not worked. Tested with newest optional and recommended AMD driver too and crashed too. I reinstalled my computer, hoping it would work, but no, and I just installed the game and still get this error. I tried everything from the reddit and riot support and nothing works. I think it's a compatibility issue with AMD CPU or with the APU (Integrated graphics card) just a tip. I saw who has AMD A10 5800K, AMD A series CPU they have this problem too. Now i have more error than before the patch 0.50 (update). I was in ranked so after the 5x error in 5 round i didn't rejoined because like this is unplayable and not fun. #angry
Read this many people replied this too: https://www.reddit.com/r/VALORANT/comments/ga5xp7/valorant_closed_beta_bug_megathread_patch_049/fpovslb?utm_source=share&utm_medium=web2x
• Screenshot: https://ibb.co/r5Xcmr2 (Sorry for bad quality, mobile camera)
• Reproduction rate: 10/10 (happened 10 out of 10 times)
• Steps to reproduce: Try to launch the game and just play.
• Expected result: Playing without this error.
• Observed result: Getting this error by vanguard every 2 minutes.
• System Specs: AMD A10 5800K, Windows 10 Pro, RX 560 Pulse
Another copy paste from above:
If you upload your Vanguard logs somewhere (they live in "C:\Program Files\Riot Vanguard\Logs") and message me a link I'll take a look.
My best guess is some sort of connection issue to our anti-cheat servers?
Region: BR
Type of Bug: Vanguard Anti-Cheat
Description: Restarted my laptop to install Vanguard and then my laptop keyboard stopped working (Vanguard blocking kbfiltr.sys, responsible for the operation of the keyboard). Uninstalled Vanguard and now its working again.
Video / Screenshot: https://prnt.sc/sdfo7x
Steps to reproduce: Just install Vanguard and restart the system.
Expected result: Keyboard working fine.
Observed result: Keyboard not working.
Reproduction rate: 100%
System specs: ASUS S46C - i5 3317U - 6gb RAM - GT 740M - Windows 10
Is this still happening? Vanguard shouldn't be blocking drivers since last week.
The game will probably remain CPU bound for the foreseeable future
Can you elaborate on why this game is so CPU reliant? I have a Ryzen 5 2600 and I have been getting a pretty consistent fps of around 144 to match my monitors refresh rate, but as others have pointed out that graphics heavy assets( Sages slows and walls, a lot of smokes in one area, gunshots from multiple players in one area) are what is causing the framerates to drop to sometimes lower than 60fps.
Is the issue due to textures not rendering fast enough and causing the drops if your CPU can't keep up? Or is it something more involving the "fog of war" trying to decide what to render? I'm not yelling at you to fix it, God knows you have enough of that, but the more info we have on our side makes it easier for people to try to optimize to the best of our ability. Any insight into how the game works would help us greatly into figuring out how to make it run smoother.
I love this game and I think most of the people who are screaming that the sky is falling love it too it they don't express it well or politely but we all just wanna play this amazing game you've created to its fullest potential.
The reason the game frame rate isn't heavily reliant on GPU performance is that we took some extreme measures during the development of the game to keep all the art performant (art style, polygon/texture/bone budgets, etc).
On the CPU side there are many contributing factors, there's no one thing that's the problem. That said, the biggest outlier right now is probably that our UI isn't very optimized (partly because it was one of the last things to get built). This is one area that we're spending a lot of time on at the moment looking for improvements.
Some of the other reasons include Unreal Engine being relatively single threaded unless you put a lot of work into it (so it only uses a couple of cores fully by default). Another factor that's more this game specific is the high tick rate of the servers which leads to a lot of processing of incoming and outgoing packets. Likewise there are several simplifying assumptions that some games can make that we don't due to gameplay fidelit...
Read moreIt's because of some internal issues with valorant. One of the devs made a security change to how an executable worked and it had a drastic impact to fps that hasn't been fully resolved yet. He said it was reverted and fps should return to normal, but clearly that's not the case because before I was getting 240-350avg and now I barely stay above 144.
The security change that was causing performance issues has been well and truly fixed... but there were several other changes that have slipped in causing performance to regress.
Right now we've increased the number of people working on performance issues and so we've got some improvements coming in the next patch. We're also identifying and planning out longer term work to improve performance, especially on high end computers.
It's hard to say for sure but I expect that performance after this next patch will be similar to the performance of the first beta version and then the patch after that should be overall better. (Your mileage may vary, this is just an estimate, etc, etc)
Read moreFor most players the limiting factor on your frame rate will be single threaded CPU performance. Unfortunately most of the settings in the game impact GPU utilization so don't end up making a lot of difference to game performance.
We're working on it though, next patch will see some improvements and the next couple of patches will make it better again. The game will probably remain CPU bound for the foreseeable future but we do want to remove frame drops and improve the frame rate on high end gaming PCs.
I've found a hacker and have video evidence of it, where am I meant to post it?
a support ticket is a good place!
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.
As a meta note about the timing of this article, I turned in my draft of this piece on April 23rd.
I probably would have worded it differently if I wrote it today!
We're working on ways to make the experience better. Our current notification pop-ups aren't as good as they could be and we're looking for ways to give you more control over how Vanguard works.
We're happy to do anything we can to make this smoother for everyone as long as it doesn't give an opening for cheaters.
TL;DR: Expect improvements before launch.
u/RiotArkem do you know what kind of ping you guys are shooting for, for the Midwest? I'm currently right outside the Chicago area with the best internet money can buy and I average 100 ping in my games of Valorant (LoL is 23-30). I'm using a VPN and the best I can find is Atlanta with 80. Thanks in advance, the game is just unplayable with current connectivity issues for me which really suck, so any advice would be amazing. (all 4 ranked games I had packet loss so that felt good lol, I uninstalled and am waiting to hear back from Riot currently.
I recommend submitting a support ticket because something is wrong here. Unless your MMR is very high (or very low) you should be playing on Chicago servers almost all of the time.
It's a good idea, I've gone ahead and swapped the word "Hacker" for "Cheater". It should be in the next patch. If I get some free time I'll think about better ways to write this screen.
Ironically this screen was meant to be a placeholder but I didn't get the chance to replace it before beta and now that it's out there it's kind of grown on me.
How werent account bans a thing from the start?
We had to choose between delaying the beta or starting without bans. It wasn't just bans though there have been a lot of areas where we weren't quite ready but I guess that's why it's a beta.
Yeah this sucked, we screwed up here.
The last 24 hours were rough for us because we've been in the process of migrating to a new ban system. Previously we had a temp-system that removed beta access (like revoking your beta drop) but as of today we have real bans.
During the migration some of our bans weren't sticking but now we should be good to go. These new real bans will also unlock some more sophisticated banning options for us (including expanding our use of hardware bans).
What risk is there from allowing the drivers to function, but stopping those users from playing until their systems meet your requirements?
You are under no obligation to improve the security of users systems, so it seems like disabling them opens up a can of worms should systems fail or be damaged because those drivers are disabled. (e.g. someone in this thread has had water-cooling issues)
If you exit Vanguard from the system tray you'll get this effect. The drivers will be able to load but Valorant won't be playable until a reboot. Alternatively you can uninstall Vanguard from the system tray and it will be gone completely until the next time you want to play Valorant.
Vanguard blocks drivers with known security vulnerabilities (usually privilege escalation via arbitrary memory writes) that allow cheat developers to load their cheats into the kernel without approval from Microsoft.
It's hard to know which hardware software monitoring tools will be blocked because many of them repackage other company's drivers. We don't block software packages specifically only the drivers they distribute.
If software that you use is blocked please check with the vendor to see if an update is available and if no update is available please contact them and ask them to fix their vulnerable drivers.
Read more