enemy players should never show as carrying the spike on the minimap, even if they are carrying it.
Disagree. Hope you reconsider.
edit: or maybe other ways to see the spike carrier while alive, such as if Sova's recon dart reveals the agent carrying the spike, he/his team could see that.
Justification above; sorry for not including it in the original reply.
(like agents automatically calling out when they see enemies with the spike
That line is in the same post, are you sure it's not intended for us to see which enemy has the spike? I'm confused cause that really seems like it was an intended mechanic, and personally I think having to hide the player with the spike or the spike itself adds more depth to the game. It also allows for more mindgames by intentionally revealing the spike at one site and then immediately rotating after you've tricked them into thinking you're committing to that first site.
Unfortunately, the post is slightly incorrect. Your character automatically calls out when they see the dropped spike, but not the spike carrier. There's also an announcement that plays for both teams when the spike carrier is killed.
Edit to address your notes about depth and spotting the spike carrier:
Goes without saying, but when defenders know the location of the spike it usually tips the balance of the round in their favor, enabling more confident rotates, stacking, and more focused defensive setups.
We used to have an announcement that played when a defender spotted the spike carrier, but it had a few problems:
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!
TLDR; Riot hasn't made any changes to deal with the sexism/toxicity, they're just saying that they're aware of the issue and are planning to do something about it in the future
As well as:
- actively investigating for fixes on performance dips
- fixing a bug where the Spike UI will sometimes overlap with the HUD
- fixing a bug where enemy players will sometimes show up as having the Spike on the minimap, even though they didn’t
- making sure players are being matched well with other local players, so they’re not being routed from L.A. to Chicago
fixing a bug where enemy players will sometimes show up as having the Spike on the minimap, even though they didn’t
To be clear on this issue, enemy players should never show as carrying the spike on the minimap, even if they are carrying it. It's desired that the spike carrier information remain hidden to defenders until they kill the spike carrier (or the spike gets dropped/planted).
I think this typically means your account's country/region is set to one that is not supported by VALORANT. You can check your account's country here: https://account.riotgames.com/account. If the value is incorrect, you can reach out to player support to have them change it. It will likely take a few days since player support is receiving a very large volume of requests.
Note: Currently North America, Europe, South America, and Korea are supported.
well i cant complain:
https://i.imgur.com/7LNkRm3.jpg
https://i.imgur.com/nPCu0qm.png
its goes to around max 4-5 pretty solid.
holy crap I think that's the highest non-bugged FPS/frametime I've seen
Okay, that's unfortunate. Between that and the freezes it may very well just be a faulty build. Very appreciative of your time and help though! I'll try contacting the laptop's manufacturer again with the added information & troubleshooting you've explained so far. I really didn't expect this level of communication at all though, so really thank you :)
Happy to help! My first gaming laptop I got in college, and it ended up being a lemon :(
I feel your pain, and I hope it gets resolved!
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.
Has it been fixed? Or is the quick fix still my only option
Fix is still being validated and has not been patched out yet. The workaround above is still the only option available.
Not the person you're asking, but yes it still doesn't work.
Thank you for replying, what region are you in (EU, NA, BR, LATAM, KR) ? We have different installers per region. Trying to determine if the issue is with one of the specific regional installers.
Nothing because like iCue and Logitech GHub to mess with keybinds and my DPI? It’s blocking all that.
And the drivers for those are up to date?
The complaints are under investigation at the moment, unfortunately I don't have a lot to go on yet, but hopefully we'll be able to have your experience sorted out soon.
Hey mate, please bear with us as we roll out our infrastructure and fine tune it. We're keeping a close eye on latency and are aware that pings in Northern South America aren't great right now... One of our engineers is from Colombia and is talking to his friends there about their experience. We'll take steps if we don't believe we can deliver the right experience.
It’s happening to A LOT of people after the latest Vanguard patch, or whatever the heck you guys did.
i7 6700k 1080Ti ASUS Z170 Motherboard 16GB RAM Corsair K95 Platinum Keyboard Logitech G502 Mouse
Also, just take a quick stroll on the sub....
https://reddit.com/r/VALORANT/comments/ge816a/vanguard_preventing_mouse_input/
https://reddit.com/r/VALORANT/comments/geaexp/can_we_revert_the_latest_hotfix/
https://reddit.com/r/VALORANT/comments/gea5l8/valorant_vanguard_issue/
https://reddit.com/r/VALORANT/comments/ge9phq/vanguard_not_initialized_error/
I know the team is reviewing this to see how widespread issues. Do you run any virtualization programs for keyboard and mouse?
Restarting the game? Because I restarted manytime and I get same thing.
Restarting your computer.
What about the damn vanguard update that is blocking mouse and keyboard usage for a lot of us??? Why are you all silent about that.
I'm not familiar with that issue. What's your set up look like? Is there an error that you're getting when it happens?
Hello I have raised this issue to the appropriate team. In the meantime I have heard that restarting fixes the issue.
Restarting the pc should fix this. It's possible there's an old vanguard version that's not updating properly for some reason. if the restart alone isn't working, can try uninstalling vanguard from the system tray and then patching/rebooting.
We're still investigating other potential causes, but that's our best guess at the moment
Restarting the pc should fix this. It's possible there's an old vanguard version that's not patching properly. if the restart alone isn't working, can try uninstalling vanguard from the system tray and then patching/rebooting.
devtrackers.gg
