devtrackers.gg
Wow that was quick, thanks for letting me know! Seems to be working pretty fine, thanks for that <3
<3
Wow that was quick, thanks for letting me know! Seems to be working pretty fine, thanks for that <3
<3
How is the anti-cheat team dealing with all this feedback about vanguard?
Is this something they thought the playerbase would have such a strong opinion on or it caught them by surprise?
Since kernel level anticheat is nothing new in the gamming industry, do they feel that there's some sort of propaganda against their system in particular?
It has been an interesting ride. We knew that people were going to have concerns with a boot driver but frankly there has been more concern than I expected. I thought closed beta will give us some time to measure perception concerns and build solutions. This on is definitely on me for not being better prepared. I don't think I would have change the priority of the work but should have provided more messaging. On the positive side the team is very motivated to show the effectiveness of this approach.
Since you're adding functionality to turn off Vanguard via a system tray icon, will there eventually be functionality added to turn it back on via the same system tray, or is that not possible?
We needed to get this out the door for Players but as time goes on we hope to improve functionality. However, as Ryeguy said we will most likely require a reboot to turn the service back on.
I was excited for the update to help me troubleshoot, but still no luck. vgtray.exe seems to run fine, but the vgc service still will not start (even after vanguard reinstall). Manually trying to start the service gives the following error:
Windows could not start the vgc service on the Local Computer.
Error 1: Incorrect function.
Trying to manually start vgc.exe gives the following error:
Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.
Please god help me. I also have ticket ID #47827789 open if you need logs.
Edit:
Thanks to Riot's K3o for the fix. One of the earlier fixes I tried was related to those bcdedit commands. I must have fixed the driver issue and forgotten to turn it back off.
If anyone else is having this issue after fixing all driver issues, make sure to run cmd prompt command bcdedit /set NOINTEGRITYCHECK...
DMing a fix to your issue
by reviewing the product both internally and with external security reviews by industry experts.
Are you guys able to release anything regarding the external audits of your software? Even just the companies?
I don't think Riot will and as the AC product owner I hope we never do. I want Players to trust us based on our actions and security standards, not for the brand of the companies we work with. We do work with excellent companies but in my experience it is the individuals that make the difference.
Can false positives be reported somewhere?
If you submit a player support ticket we can review any bans for false positives.
I was excited for the update to help me troubleshoot, but still no luck. vgtray.exe seems to run fine, but the vgc service still will not start (even after vanguard reinstall). Manually trying to start the service gives the following error:
Windows could not start the vgc service on the Local Computer.
Error 1: Incorrect function.
Trying to manually start vgc.exe gives the following error:
Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.
Please god help me. I also have ticket ID #47827789 open if you need logs.
Edit:
Thanks to Riot's K3o for the fix. One of the earlier fixes I tried was related to those bcdedit commands. I must have fixed the driver issue and forgotten to turn it back off.
If anyone else is having this issue after fixing all driver issues, make sure to run cmd prompt command bcdedit /set NOINTEGRITYCHECK...
The service isn't designed to be manually started, that error is expected.
If you add your Vanguard logs to the ticket (from "C:\Program Files\Riot Vanguard\Logs") we'll be able to take a look at it.
I’m sure this has been answered somewhere else but I can’t find it (If any other redditors can point me to it that would be appreciated). Do you guys have an official fix for when a system reboot doesn’t get rid of the “reboot required” message?
This update will help with that by at least notifying you when a component isn't compatible with Vanguard.
It seems lot of people reporting the issue here are using Ryzen CPU. What do you have on your test machine ?
Mostly Intel chips, a lot of Xeons and some i5 / i7 / i9s. Normally we have a compatibility lab with machines of all different configurations (across vendors and performance levels) but we've got limited access to it right now.
When is the next patch coming out?
Early this week hopefully
Is there any way to have vanguard off all of the time besides ingame without uninstalling
The two options right now are either uninstalling (you can do that from the system tray) or exiting Vanguard as soon as your system starts (also from the system tray icon).
Another week of VALORANT Closed Beta in the books, and it looks like we’re getting (somewhat) into the rhythm of things. Over the past two weeks, we’ve been able to patch multiple times to address emergent exploits, fix many bugs (including a revolver-wielding camera that we thought was hilarious), and make our first (but definitely not last) balance change of the closed beta.
But a community at play is also one that never sleeps, and we’re already seeing new things to tackle. So without further ado, let’s get to some emergent topics.
We saw how much you all loved Paul Chamberlain, VALORANT’s anti-cheat lead, the first time around, so we brought him back to quickly chat about some additional Vanguard bugs he’s seeing in the wild, and some adjustments we’ve made from your feedback.
...
Can you believe we’re three weeks into the VALORANT Closed Beta? We wish it were four weeks so we can celebrate our one month anniversary, but we also don't want to seem clingy. Rejoice with a slew of patch notes full of quality of life updates.
Phoenix mains can look forward to the removal of two Run it Back bugs, you can now actually exit custom games with the click of a button, the rare cases where the Spike would get stuck in the map should be history, and Observer mode benefits from a few improvements (more on the way!).
You’ll see the addition of “Competitive mode” here and you’re gonna have to wait a little before it goes live. Yes, we’re excited too.
Read all the changes below.
Omen
Awesome write up hopefully, this shutdown all the AHK meme aimbots that people think will be the end of this game lmfao
/u/riotarkem is conjuring something for that one. SoonTM.
any plans to involve third party development for AI anti cheat systems? any in house systems being built? please update us!
We've got our data science team experimenting with machine learning techniques for aimbot detection, right now it's not production ready but initial results are promising.
Read moreHey dude, good to hear from you again.
When I've been saying "single threaded" I mean it's just using the few threads it does (as you explained in your lengthy post before) and I have linked back to the thread so people can read it themselves. I've checked threads in use on HWID during games and I can see it's not strictly on 1 thread, somebody else posted something similar a couple days ago too.
I think when most people talk about "multithread" in this context, we're generally talking about using way more than it does right now, given that there's CPU's with 16 threads out there today. It just feels like a bummer knowing that this game was marketed as being well optimized (and it is for lower end PC's) but everybody else with more modern machines are found wanting.
My post was to clarify that on higher end systems the best way to improve framerate is to increase core-clock of the CPU and to let people know upgrading their GPU wasn't go...
Ahh yeah that's cool. I don't think you're trying to push a false agenda or anything. Just trying to stay accurate.
I can already see some people parroting "single-threaded" around so I wanted to make sure people understand that a quad+ core CPU is still a really good idea for VALORANT since you can think of it as a 3x threaded game which is a big difference from a 1x threaded game.
If we want to be super pedantic I VALORANT allocates ~1 worker thread per virtual core on your system. However, those threads don't always have work to do and can spend a lot of their time idle.
will the patch tomorrow include the addition of ranked matchmaking?
If the next patch goes well we will turn on ranked matchmaking. It won't be immediate because we'll want to make sure the patch is stable and no major issues are discovered.
What do you mean it's not just pthread_create? Just mutex everything and you'll be using more cores in no time! Sure, all the extra utilization is going towards context swaps and shit, but it's now multithreaded! /s
Genius!
when will there be fps fixes? i get microstutters every time i try retake a site and everyone is shooting and fps is broke in other games :(
Most of these issues should already be fixed by now, however, there'll be more optimizations in the new VALORANT build coming out soon (hopefully this week).
In the latest patch that you pushed everyones FPS was dropped by huge amounts. What exactly in that update made us lose so much? For example when I look into a wall I have around 4-600 fps. Spraying with with the vandal or phantom lowers me to 200 and sometimes even below. In the real world I have around 200~ fps, but spraying guns makes me go even lower causing stutter and extreme screen tearing.
Before the patch was pushed I were above 300 fps in 99% of the times resulting in an extremely smooth gameplay with almost none visible screen tearing.
Why did this happen and why is the next patch going to solve the problems as stated by other people on Riot?
Well you've come to the right place!
About a month ago I changed a build setting for how VALORANT-Win64-Shipping.exe is compiled. It's a security related setting but not related to Vanguard.
Due to a bunch of factors this change didn't get tested as well as usual, some of those factors were:
This meant that despite the large performance degradation the change made it into the patch and to players. Once our stats showed that FPS for players had decreased an investigation started. Since the 0.47+ patch was a small one it was relatively fast to narrow down the suspect changes and to my security change in particular.
Once my change was suspected ...
Read more