Valorant

Valorant Dev Tracker




30 Sep

Comment

Originally posted by CaptnKrksNippls

Having to force close the game through task manager because of freezing as others have stated.

If anyone else gets this issue, please help us out! We need a process dump from VALORANT while the issue is occurring. You can follow this guide to see how to get that - https://support.kaspersky.com/common/diagnostics/12401

If you hit the freeze again, please follow these steps to create a dump, then you can send it to me directly. Thanks!!!

Comment

Originally posted by LikeForKills

- Region: NA

- Type of Bug: Matchmaking

- Description: Game freezes after a round ends

- Video / Screenshot: None available (I couldn't open NVidia replay thing)

- Steps to reproduce: Both times it happened for me, I was holding tab when the round ended.

- Expected result: The round ends and the next one starts

- Observed result: The round does not end and freeze

- Reproduction rate: Hold tab when round is ending?

- System specs: i7-8700k, RTX 2070, 16gb ram

If anyone else gets this issue, please help us out! We need a process dump from VALORANT while the issue is occurring. You can follow this guide to see how to get that - https://support.kaspersky.com/common/diagnostics/12401

If you hit the freeze again, please follow these steps to create a dump, then you can send it to me directly. Thanks!!!

Comment

Originally posted by jbellas17

THE GAME JUST f**kING FROZE FOR ALL PLAYERS

If anyone else gets this issue, please help us out! We need a process dump from VALORANT while the issue is occurring. You can follow this guide to see how to get that - https://support.kaspersky.com/common/diagnostics/12401

If you hit the freeze again, please follow these steps to create a dump, then you can send it to me directly. Thanks!!!

Comment

Originally posted by LikeForKills

Oh I misread reproduction rate, it happened a couple times to me and a couple times to my teammates and opponents in the game that I played, I only got one game in because I didn’t have time for another

Thanks!

Comment

Originally posted by LikeForKills

For me, I’ve only been playing omen in ranked and it’s only been around when the round is ending, I’m not sure exactly when because the sound cuts out, but oddly enough I can still hear and talk to my teammates. I think it’s the screen freezing but not the game because my teammates said my agent was turning when I was moving my mouse

Thanks for the details!


29 Sep

Comment

Originally posted by LikeForKills

- Region: NA

- Type of Bug: Matchmaking

- Description: Game freezes after a round ends

- Video / Screenshot: None available (I couldn't open NVidia replay thing)

- Steps to reproduce: Both times it happened for me, I was holding tab when the round ended.

- Expected result: The round ends and the next one starts

- Observed result: The round does not end and freeze

- Reproduction rate: Hold tab when round is ending?

- System specs: i7-8700k, RTX 2070, 16gb ram

Thanks for the report! Any particular characters that you've been playing or observed a common thread with the freezes?

Are the freezes only occurring on round end?

Comment

Originally posted by jbellas17

THE GAME JUST f**kING FROZE FOR ALL PLAYERS

Thanks for the report! Got any additional details about when it happened and how it happened?

When you say frozen, you mean the screen was frozen but you still heard audio? Could you still hear voice?

Comment

Originally posted by Ash_Kiwi

Is there no downtime for patches anymore?

for non-Act change patches, they are now 0 downtime

Comment

Originally posted by cupidstoleyograndma

Ok, cupid here again, saw the knife. I love the pop out animation, although it was a flip, but it was “different”. I like it imo, however It would’ve been cool if the vfx had the circles around them instead of grey regular ones, but I still think this is my favorite knife lol. Woulda also been happy about a finisher of a ufo taking away someone, but the skins are already made and in the system. Have my money haha

Haha! A UFO finisher idea sounds amazing :)

Comment

Originally posted by InnocentBowlOfRamen

I cannot believe you actually answered a 5-day-old comment on a month-old thread “with 8 comments and one upvote”. You absolute legend thank you

Ey, what can I say? I lurk in the shadows waiting to answer responses lol.

Comment

Originally posted by RiotRectifyer

To follow up, we identified and fixed the issue, but were unable to get it into the patch. It should be fixed next patch :)

And as an added bonus along with fixing this we added the lil halfway tickmarks to the progress bar when defusing the bomb in this defuse module, it's literally unplayable in its current state without them. Sorry, will be fixed next patch!!

Comment

Originally posted by [deleted]

Thank you!

To follow up, we identified and fixed the issue, but were unable to get it into the patch. It should be fixed next patch :)

Comment

Hey! Thank you for the info! We made a bunch of small bug fixes in range and this may have been a regression due to the changes in the space. I've brought it to the attention of the team. Sorry about that!

Comment

Originally posted by BobTheJoeBob

Sure you can. This isn't a hit reg thing; it's a latency thing. He was dead before be shot his bullet but because of latency it takes a while for his client to get that information.

This is the most likely answer.

Omen's single headshot was registered on the server before OP's shots were registered.

Something that makes this a bit more clear is that you can see the small yellow client-predicted hit-impact sparks that we added recently, but you don't see the accompanying large server-authoritative hit impact effects that indicate the shot also landed on the server.

Comment

There's a reason this is one of the first things the Tutorial tells players!

The Operator is experiencing it’s coming-of-age movie. But before you get all “look how they massacred my boy” on us, let one of our lead designers walk you through our analysis. There’s also some systemic weapon updates to change your accuracy after landing from a jump.

Five Agents get the squeeze, including ongoing updates to make Viper a more flexible threat, and some parity across the fire rate buffs from Brimstone and Reyna.

What’s in a name? Reported players caught with an offensive name are now forced to change their Riot ID.

...
Read more
Comment

Originally posted by sabocano

hey, great news thanks for updating us

so I don't think you went through all the corners/walls of the maps and fixed them right? Something basic was broken about it and you fixed that and everything aligned ?

tldr; a bit of both

the vision cones were an old prototype feature that just ended up shipping in the same way as it was made in prototype years ago. each map has a separate vision cones mesh for perf

but the versions of the maps they were authored for are slightly older in some places and out of sync. it was a bit tedious and annoying to do these small updates, so we also made some changes to make these adjustments easier. we're also having QA help us spot issues where they dont match up with sight lines

thanks for calling this out!

Comment

Originally posted by sabocano

Hey thank you for informing me. Since I'll be the only one seeing your reply =)

i missed the patch notes cutoff, but Ascent's vision cones should be fixed in 1.09 and Bind (and maybe more) in 1.10. the other maps shouldn't be too far behind those :)