Riot_Sobey

Riot_Sobey



27 Apr

Comment

Originally posted by Left-Entertainment45

• Region: EU

• Type of Bug: Hitreg / correctness / whatevs.

• Description: Visual hit but not registred

https://medal.tv/games/valorant/clips/j81lhwf8y6Vw-/d1337gDxHL7X?invite=cr-MSxWaFMsMTIwMzkwMzAs

• Reproduction rate: I feel it happens quite often, although not often I wanna take the time to make a clip/posting about it.

• Steps to reproduce: Just play the game and think your bullets are made of other material than air

• Expected result: Hitting shots

• Observed result: Getting jebaited

• System Specs: yEs CaUsE itS WhAT iS tHE prOBleM xdDXdddd

Looks like it was your ally that hit the shot at 3 seconds in your clip, then you landed two shots (one mid jump at 6 seconds and another one after they landed)

The sparks that show up there are server-side hit confirms, which means a shot was registered and damage was dealt


01 Sep

Comment

Originally posted by Rojo424

Shots 1-5: Clearly missed.

Shots 6-9: Missed due to recoil (bad spray control).

Shots 10-11: Very close, but recoil and inaccuracy make these reasonable misses.

Shot 12: Likely didn't actually fire because Hiko was already dead.

^ this

...actually some new tech got turned on this patch, which allowed the temporary invulnerability on Omen's ult to carry over on respawn. This has been fixed! Your games should be safe from Invulmen


24 Aug


20 Jul

Comment

Originally posted by AchievingAtaraxia

u/Riot_Sobey

Address this ASAP, it's been plaguing the game since release and makes the competitive integrity of the game a pipe dream for now.

Also, I can confirm that I have had this exact situation have multiple times WITHOUT packet loss, WITH 19 stable ping and against players with normal ping.

This is the biggest problem with the game right now.

We are aware of this issue and are looking into it!


14 Jul

Comment

Originally posted by vecter

woah WHAT

I wish you had the network indicator up then to see if you had any packet loss. unlikely though ...

/u/Riot_Sobey

I think the bots use different tech than players do for rewinding- looks like there's possibly an issue with the bot hitbox getting desynced. Thanks for the report and video!


06 Jul

Comment

Originally posted by vecter

Ty, looking into it. From these gifs here it looks like there isn't a hitreg bug- but it IS super confusing that the hit impacts and tracers (which are delayed) can appear over the head when a player crouches, making it look like it should have been a head shot when it was actually a body shot. No bug here that I can see, but definitely a good candidate for some QoL changes to make this less confusing

Comment

Originally posted by xlmaelstrom

is there a point with tagging them? They don't care it seems, no statement after hundreds of posts..

Tagging is helpful- I check each of these posts! Definitely not ignoring you guys, I was just on vacation.


18 Jun

Comment

Originally posted by nicologameurfrancais

oh lord , i feel bad for you ! Everybody talks about it except RIOT.

But at the same time 90% of the player base cant see an issue on hitreg so i think riot ignores it thinking the problem will disapear by magic!

That is absolutely not true. I'm looking for hitreg issues (and talking about hitreg issues) all the time. We care a lot about this- but text anecdotes are a terrible way to go about narrowing down the problem. There are lots of connected systems that are a part of hitreg, investigating off an anecdote is not particularly helpful.

That being said, this video is excellent! Really well done here- just enough footage before the bug, slow-mo during the bug, and just enough time after the bug. You've also got your FPS and packet loss in the clip and ping in the comments! This makes it a lot easier to follow up on- video of the incident and the conditions in which it occurred are really helpful. Given your conditions (18 ping, 180fps, 0% packet loss) hitboxes should be almost perfectly synced, but it looks like they're not. There's probably a bug here.


09 Jun

Comment

Thanks for the video! This video is an excellent example of what we look for in a video about a bug- there's just enough context for before and after the bug occurred, which helps narrow things down. Lovely.

I found a repro for this bug- it looks like it's possible to fire the OP on the server while the client is still readying the OP if you attempt to fire it within a small window while equipping after using Omen ult. This puts the state machine of the gun out of sync on client and server. This causes other weird downstream effects like mentioned in the comments here- stuff like the reload not visually occurring on the client. Just found the bug so no ETA on a fix, but we have eyes on it now. Thanks again for the video!


29 May

Comment

Originally posted by Razur

Hey Blake, I've given you the Riot user flair for the subreddit. Hope you're doing well! :D

Yay! Thanks :)


28 May

Comment

Originally posted by vecter

Thanks for following up. It's a bit concerning that the hit representation on the smaller target is off, only insofar as it may be a symptom of another unknown hitreg issue. Just thought it was worth surfacing.

Appreciate it! Always happy to look into potential hitreg issues.

Comment

Originally posted by vecter

/u/Riot_Sobey is this intentional?

TL:DR Looks like there may be a bug here with the way we're representing the impacts on the smaller target, but otherwise things should be okay here.

There's a couple of things here to talk about:
1.) Hit impacts and the way they are being represented on the tiny target. The hit impacts for the weapons on the larger target should be accurate, but the ones on the smaller target are not- notice the real hit impacts are in the center of the crosshair, and the ones on the smaller target are off-center. This is most likely a bug with how those hit impacts are being represented on the tiny target, and not the shots themselves being fired too low.

2.) The headshot on the bot. The bots' models are a bit thinner than their actual hitboxes, if you shoot slightly around the bots you should see hit impacts and deal damage in most cases- this includes the top of the head. This is true for many of the agents as well- all agents share the same hitbox, but have slightly di...

Read more

19 May

Comment

Originally posted by Air3s

sh

Thanks for the update!

Is there an FPS range that this would apply? like is 200+ fps the area that the bug is least impactful?

I this bug affecting only certain servers and player?

Also, how desync'd can the server be to the player, are we talking about milliseconds or seconds? The reason I ask is, if an enemy player 'was' moving, but comes to a stand still, and a player hits them with no regs, would that be a fitting explanation to something like in this clip?

https://clips.twitch.tv/TallWimpyBorkFrankerZ

Thanks!

The bug affects players at all FPS ranges, but scales in severity the lower you go. At 30-15 FPS it gets pretty bad- not hugely bad but bad enough that the shots (as seen in your video) would miss a moving target if you were lined up directly on them. I believe that's what is going on in the video you linked here- you can see the player dips to about 70 fps while shooting- low enough for the hitreg desync to be large enough for the shots to miss.

Comment

Originally posted by MyCandyIsLegit

Will there eventually be more color options for player outlines? I feel yellow is much easier to see than red and I'm not colorblind, but also feel other options might benefit people more.

I'm not sure yet, I imagine more color options is not off the table.


18 May

Comment

Originally posted by jimoshitemoto

I know it's not your domain, nothing about hitreg and stuff.

But may you pass the word about "Headache" problem on valorant? "seem" to be a problem arround weapon sway/bob or even spray that shake the screen.

Apex Legend had a similar problem with headache, that was due to movement shake.

Would gladly appreciate :(

https://www.reddit.com/r/VALORANT/comments/fxb5v4/valorant_giving_headaches/

https://www.reddit.com/r/VALORANT/comments/gc09e6/how_to_get_screen_to_not_shake_when_shooting/

I can talk with some folks about it, yeah. As I understand it it's a competitive advantage question- do we allow a setting that helps alleviate the 'headache' problem if that setting is a must for competitive play? I'm sure there's more to it than that, but that's my simple understanding of the problem in adding that setting for now

Edit: Don't worry about shooting stuff my way that's not out of my domain- my domain is rather broad (most of the underlying game tech is done by my team, stuff like movement, HUD, UI, Hitreg, Wall Pen, etc etc). If it's something I don't have knowledge about I can direct you to the right folks to talk to

Comment

Originally posted by VacantMindz

Can you go work for Respawn part time and fix Apex hit reg please? Love the dedication you guys are showing to your game, thank you for all your hard work.

If only all the FPS games I loved had perfect hitreg!

Thank you, I very much appreciate the kind words :)

Comment

Originally posted by LittleLunia

Damn, nice find. This might be enough info for Riot to be able to pinpoint the underlying cause.

This is a great video. We're looking into it!

Thanks again to all you wonderful people out there reporting bugs with videos- it makes reporting and fixing these much smoother.

Comment

Originally posted by Air3s

Just wanted to say thank you for the excellent communication. Its very rare that developers in critical areas of a game communicate directly to their community about core game mechanics! Please continue to keep us updated on your progress <3

Really appreciate that, thank you :)

Comment

Originally posted by londongeeza123

hey, just wondering do you think this hit reg stuff will be in the next patch ? because for me the game is sort of unplayable , ive seen countless people post about it today also, however i would like to say the game is amazing and i understand its in beta so these problems are bound to occur, but just wondering if it will be sorted in a patch and when the patch will be roughly, Thanks for your time.

We're still digging to fully understand what's happening. I can't confirm that we'll have a fix by next patch once we confirm where the bug(s) are, but we're trying!

Comment

Originally posted by VictoriousX

hi, there a recent popular hitreg desync issues,maybe u can have a look thx https://www.reddit.com/r/VALORANT/comments/gl9mka/i_think_there_is_definitely_some_desync_issue_was/

Thanks for the link! Looking into this as well.