devtrackers.gg → Valorant
Valorant

Valorant Dev Tracker




All Patch Notes Twitter YouTube News Twitch Reddit
View
View: List Card

28 Apr

02: On Vanguard errors/solutions, gun skins, and agent progression

Post

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.

...

Read more

27 Apr

Upcoming Vanguard changes

Comment

Originally posted by OWPD

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.

Upcoming Vanguard changes

Comment

Originally posted by otherchedcaisimpostr

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.

I feel like this game needs some CPU optimization.

Comment

Originally posted by Devilishola

Hey 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...

Read more

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.

Upcoming Vanguard changes

Comment

Originally posted by bloodkp

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.

I feel like this game needs some CPU optimization.

Comment

Originally posted by Yomafacio

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!

Upcoming Vanguard changes

Comment

Originally posted by Bloodnoskie

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).

Upcoming Vanguard changes

Comment

Originally posted by robinlol

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:

  • a lot of disruption due to COVID-19, reducing QA availability
  • a focus on our 0.49 patch rather than the 0.47+ hotfix
  • not enough playtesting on our dev branch because we were testing the closed beta release candidate
  • the problem wasn't obvious on our work computers

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

Upcoming Vanguard changes

Comment

Originally posted by Rakinare

Vanguard is blocking VMWare Virtual Machines from starting. This has impacted a lot of people's workspaces and by now, is already known to VMWare. Is this issue already known to you guys? Will something be done about this?

We've addressed this a few times already. We're aware that some folks are having issues, but we haven't been able to repro it on our ends. We'll continue testing, though.

A Message About Vanguard From Our Security & Privacy Teams

Comment

Originally posted by raulgbcr

I don't really wanna push or throw any shit over this, but could you give us an aproximate ETA of when this feature will be added?

Also, I know its probably out of question, but any plan on supporting linux players with vanguard? Currently wine does not support most of the kernel driver features, so probably will need some kind of reimplementation or native support for linux in any way, I know linux players would probably represent 1% or less of your player base, but we do still exist...

Update is live check out Nemi's post for more information. https://www.reddit.com/r/VALORANT/comments/g9aoap/upcoming_vanguard_changes/

Upcoming Vanguard changes

Comment

Originally posted by Jefneri

Heya, is there a fix coming for the "Vanguard requiring reboot" -bug? Kinda annoying to safeboot and manually overwrite the files everytime I wanna play. Great game otherwise, and I've been enjoying it a lot.

P. S. Ive tried the method where you remove the drivers and ran as administrator etc. This is the only way I get my game to run. :(

This update will hopefully help. If you keep noticing problems though, please reach out to player support so that they can help with triage!

PSA: Having Vanguard installed/enabled will break your virtual machines!

Comment

Originally posted by SimplyFrankie

Hey there, thank you so much for your response! Just to clarify, which logs should I send? (So I can do so as soon as I can!)

Any files from "C:\Program Files\Riot Vanguard\Logs" would help and if you know of any VMWare logs that could have information those would be good too (but I don't know where they live).

Upcoming Vanguard changes

Comment

/u/0xnemi knows what he's talking about but I'm also happy to answer questions!

Upcoming Vanguard changes

Post

While we normally don't plan on documenting changes to Vanguard, our Anti-Cheat system for VALORANT, on a frequent basis, this new update to Vanguard adds a new visual component that will give you, the player, more visibility and control over it. This post serves to provide some context.

 

Starting today, Vanguard will start showing a system tray icon

(after a reboot) while it's running. From there, you'll be able to turn off Vanguard at any time. Turning off Vanguard puts your machine in an untrusted mode and will prevent you from playing VALORANT until you reboot. If you want to keep Vanguard off indefinitely until you play VALORANT (e.g. persisting across multiple reboot sessions), you'll be able to do so mor...

Read more External link →

PSA: Riot Vanguard updated today, and blocks players from playing the game with "SYSTEM REBOOT REQUIRED" error. Details below.

Comment

Originally posted by ShadonicX7543

Can I send you my support ticket number so you can help with my problem as well?

Sure!

I feel like this game needs some CPU optimization.

Comment

Originally posted by iDoomfistDVA

Any ETA for us Ryzen bois?

There's a patch this week with some improvements!

I feel like this game needs some CPU optimization.

Comment

Originally posted by mavericked

Gotcha, I appreciate the response. My friend just purchased another stick of ram to go run dual channel (just to test our theory of 1 stick vs 2) and he's seeing a 50-60 fps peak increase in fps. I actually saw a similar phenomena in Overwatch with RAM frequency, but I don't recall if I was single or dual channel. Just figured I'd share. Thanks again!

For sure! I considered adding dual channel memory to our min and recommended specs. We see the same thing internally where the game won't run well on one stick of RAM. It seems like it may be more popular to run just one stick of RAM than we originally thought. Dual channel RAM is going to speed a computer up a ton and not just for VALORANT.

I feel like this game needs some CPU optimization.

Comment

Originally posted by Rawzlekk

I have a Ryzen 7 2700x with a GTX 980 Ti. Haven’t had big fps issues. I can consistently get 150-200 depending on what’s happening on the screen. In fact I don’t even notice the drops so I can’t say I really know what I get during fights or anything like that.

This is for another thread but the bigger issue for me is this “Network Problem” icon that’s consistently popping up when I have 39-45 ping. The stuttering can get really bad, like unplayable bad at times. And it’s super frustrating when I seemingly have good ping. I turned on the ping chart and there are occasional spikes that the KDA board doesn’t show, but the spikes are up to 50-60 ping which doesn’t seem to justify major stuttering.

The ping chart averages over 1/10th of second. I think the scoreboard is 1/4th of a second. It's possible you're seeing really transient ping spikes that are actually much higher than the chart shows.

Could also be packet loss so you might try turning that chart on as well.

I feel like this game needs some CPU optimization.

Comment

Originally posted by Dnomes

Cmon Riot, it's so f**king SIMPLE!

.RunValorant(parallelize = true, threadCount = THREADS.MAX, coreCount = CORES.MAX) parameters, shit, how did the devs forget those options?

There are a lot of metrics that go into development, and it doesn't seem you really care about the performance bounds on either side of the userbase, plus visual fidelity isn't the only performance drain in the game, considering there's a lot of logic going on in the background. Cores and threads doesn't necessarily == FPS, as some tasks just don't benefit from being 'split' up like that.

From my anecdotal evidence, the game runs great in terms of frametime and framerate on low end and high end setups, that I have run the game on, which is really really commendable.

Cmon Riot, it's so f*cking SIMPLE!

.RunValorant(parallelize = true, threadCount = THREADS.MAX, coreCount = CORES.MAX) parameters, sh*t, how did the devs forget those options?

Ahh sh*t you're right I forgot.

On a more serious note though, we do hold ourselves to a high perf bar for the game. I'm glad players are giving us perf information from the more subjective side. We do have numbers but hearing from player's experiences directly as well is great, both when they're having a great performance and when they think we're missing the bar.

I feel like this game needs some CPU optimization.

Comment

Originally posted by Devilishola

It's definitely a problem when I get the same FPS on Apex Legends - a complete BR game with a map 100x the size of this to render. I made a thread a while ago and got replies from a Riot Dev (link below), it turns out the game is heavily single threaded with almost no bottleneck on any GPU that's past a few generations old.

It's still very strange they've chosen to go with singlethreading over multithreading with how the CPU market is right now. I hope they optimize the game well, I'm a bit disappointed seeing only 180fps average.

Link Here: https://www.reddit.com/r/VALORANT/comments/fxlcxu/riot_pls_valorant_doesnt_use_100_of_the_gpu_and/

I just want to jump in and clarify that our game is indeed multi-threaded. The game is using 3+ threads nearly 100% of the time. It varies based on the amount of work that can be multi-threaded at the time.

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 going to help as much if you already have a pretty modern GPU.

That being said we can always look at multi-threading more of the systems to get even better performance on systems that have a large number of cores. It's something we're aware of.




Subscribe to RSS
Get Discord notifications
Patch notes

When do they post?

(GMT +0)
Something missing? Let us know and we'll add it!