devtrackers.gg
bruh I've been playing with 30 fps since the first day i see no difference between patches for me
If you're playing at 30FPS, you aren't going to notice FPS swings like this because you are likely GPU bound, and the swings are happening on CPU.
bruh I've been playing with 30 fps since the first day i see no difference between patches for me
If you're playing at 30FPS, you aren't going to notice FPS swings like this because you are likely GPU bound, and the swings are happening on CPU.
I have a GTX 2060 and an i7-7700k that should in no way be bottlenecking my performance. I should be performing higher than 60 FPS. My framerate is not locked. Anybody have any solutions for this?
You definitely should be getting more than 60FPS, even after these recent issues. Generally these are some steps I'd recommend trying:
-Install latest drivers
-Reboot your machine
-If you only have one stick of ram, getting two helps (for dual channel ram speed)
-Update windows
-reinstall windows
I have massive drops(80-100) everytime I open the buy menu, I don't know if that is indended though. (No, I don't limit the FPS in menus or everywhere else from the settings)
You'll also get massive FPS drops when you open the options menu! We have fixes for this coming in the next patch as well.
The frame rate junkie in me would love to have the option for an exact frame-by-frame graph of frame times so that even single missed frames can be seen, such as what Afterburner has (Afterburner is now blocked by Vanguard so a substitute built into the game would go a long way).
We've been talking a bit about whether this is something we should do. The same people that would build that are the people who fix the perf issues though... :sweatguy:
Whisper more of your sweet sweet dev communication in my ear.
Strange response, but I'm here for it
Im pretty sure me getting 120fps average outside of fight in game on a 3800x, 2080ti is not just "fps being worse this patch", its been like this for a week or so now
For AMD specifically, I've mentioned this elsewhere, but we're investigating why AMD hardware is getting worse performance than Intel/Nvidia. You're correct that these parts have been underperforming on the game since the start of beta (we had actually already discovered this in testing prior to beta, but weren't able to identify a fix).
Thanks for the post! I work on performance testing on VALORANT, so I can provide some insight. Couple of things I'd like to clarify:
Read moreI think the default binds for the comm wheel need to be changed. Of all of my 8 IRL friends and I who got the beta, I was the only one who knew about the comm wheel after over a week of playing with them.
No one is going to randomly try pressing period or comma in an FPS game, it just doesn't seem like a key that would ever be bound to anything.
Most people I know do not check the keybind menu to learn the controls, they just figure out the controls by playing. Without any kind of on-screen prompt, I feel like the chat wheel goes entirely unnoticed.
Like don't get me wrong the addition of a chat wheel for calling to teammates is amazing and I had been wanting something like this in CSGO for ages. I just think its use could be encouraged a bit more so that new players actually know its there.
EDIT: Also an end of game teammate review would be nice. Similar to the commendation system in CSGO. As in it would be cool to commend your teammates for excepti...
The plan is to add a small module to the starting tutorial that makes people aware of the features, and then prompt them to rebind to something more convenient if they want to use them.
Unfortunately, we don't have enough easily accessible keys to place everything within reach by default.
Had no idea this was a thing until recently, y'all should consider putting it in the tutorial and changing the default bind, because with your left hand on wasd and your right hand on your mouse, who is really going to want to take their hands off of one of those things? No one.
We have plans to add these to the onboarding - just didn't have time for the beta. I agree that it's important to ensure everyone knows they exist.
Candidly, we have more features than conveniently available keys. Our strategy was to add these features knowing that some people would want to use them, and some would not. The ones that want to use them can rebind to suit their needs, and the ones that do not aren't burdened with a feature they have no intention of using taking up a valuable key bind slot.
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.
Any update on the fix? I've had the same issue for a while and submitted a ticket as well.
Sadly the fix on the game side isn't going to land before the next big patch.
There's a workaround up above that you can try. Setting an environment variable OPENSSL_ia32cap to ~0x20000000 should mitigate the issue if this is the one you're hitting.
A good communication wheel would do wonders. But also some people don't like speaking.
Comm wheel is available to bind to your favorite key. Same with a CS/Tribes radio tree.
They are on comma and period by default (so you can check them out), but should be rebound if you want to use them regularly.
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.
Pretty harmless thing to add, I'll look into it. Appreciate the other folks sharing the extended info feature (left alt) too. It's really handy for spot checking ability charges for teammates (like availability of Sage heal). And it does indeed include armor status.
I'm having the same issue with the comms wheel. My default setting for the comms wheel is Thumb Mouse Button 2. When I open the wheel, it shows mouse wheel up and mouse wheel down to get to the social and strategy wheels. I bind jump to Mouse Wheel Down, so I can't get to the other comms menus. Even after changing jump back to spacebar for default, it still doesn't work. Nothing happens when I open up the comms wheel and scroll up or down. Unfortunately, I can't always use a mic, so being able to easily access all of the comms menus would be great.
Let me look at the way the controls are set up for the wheel.
Just so I'm clear on the issue: You all are binding mwheelup and down to other things, but you still want to use the wheel to select the other comm wheels? Or would you prefer to use other keys to select the other wheels?
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.
TY for passing along. Sorry for getting to this late. We've taken appropriate actions.
Unfortunately it's a bug. Fix in progress.