consecutive-dash-cooldown-trigger-is-08s

KQM | Genshin Impact

19 messages

TiBotSun, December 11, 2022 at 02:42 PM

@kourinn - As an author, it is your responsibility to complete the ticket

Guidelines
- You can rename your ticket with /rename <ticket name> or with the button below
- If this ticket was created by accident or it can be deleted, you can use /delete within the first 5 minutes, otherwise ask a Scholar.
- When you are ready to submit the ticket, compile everything into one message following the format below and pin it. Then type /close or click the button below; the ticket will automatically be moved to be reviewed.
- To add contributors to your ticket you can use /contributor add <user>.
- The ticket will be scrapped if: no activity >1 week or open for >1 month.

Write-up Format

Theory/Finding/Bug: Title of your submission

Evidence: Explanations with calculations and/or YouTube/Imgur proofs

Significance: Conclusion

kourinnSun, December 11, 2022 at 02:47 PM

Finding: Consecutive Dash Cooldown Trigger is 0.8000s. This can be extended by hitlag.
Evidence:
https://youtu.be/dKiHbJZZA2E

This shows the interval for which consecutive dashes will trigger the dash cooldown. The footage is 120 fps gameplay converted to 50% speed 60 fps video.
Consecutive dashes starting at frames 100 and 196, trigger the dash cooldown. Converting to real time, 96 / 120 is 0.8000 seconds.
Consecutive dashes starting at frames 541 and 638, does NOT trigger the dash cooldown. Converting to real time, 97 / 120 is 0.8083 seconds.
For further samples not shown here, all consecutive dashes with 94 frame interval or smaller triggered the cooldown. Meanwhile no consecutive dashes with 98 frame interval or larger triggered the cooldown. Intermittent results between 95 and 97 frame interval are caused by input variance within starting and ending frametimes.

https://youtu.be/tmIyJPkDFKk

This shows the interval for which consecutive dashes will trigger the dash cooldown. The footage is 120 fps gameplay converted to 50% speed 60 fps video.
The 0.8s consecutive dash cooldown trigger is extended by hitlag.
Consecutive dashes starting at frames 46 and 158 still trigger the dash cooldown due to 18 frames of hitlag. Converting to real time, (112 - 18) / 120 is 0.7833 seconds.
Consecutive dashes starting at frames 464 and 578 do not trigger the dash cooldown. Converting to real time, (114- 18) / 120 is 0.8000 seconds.

Significance: Good to know for dash canceling combos (i.e. C1 Hu Tao) and open world traversal.

Consecutive Dash Cooldown Trigger is 0.8000s

This shows the interval for which consecutive dashes will trigger the dash cooldown. The footage is 120 fps gameplay converted to 50% speed 60 fps video.

Consecutive dashes starting at frames 100 and 196, trigger the dash cooldown. Converting to real time, 96 / 120 is 0.8000 seconds.

Consecutive dashes starting at frames 541 and 638, does NOT ...

Consecutive Dash Cooldown Trigger Hitlag Extension

This shows the interval for which consecutive dashes will trigger the dash cooldown. The footage is 120 fps gameplay converted to 50% speed 60 fps video.

The 0.8s consecutive dash cooldown trigger is extended by hitlag.The 0.8s consecutive dash cooldown trigger is extended by hitlag.

Consecutive dashes starting at frames 46 and 158 still trigg...

Hopefully nobody complains about the frame rate. Did so to reduce input variance within +/- 1 frametime of the cooldown trigger. 120 fps is technically not allowed on PC (only allowed on new iPhones iirc).

OBS may have dropped a frame every now and then, leading to duplicate frames, but the frametime overlay at the bottom shows no variance in-game. So the findings should remain accurate within +/- 1 frametime.

TiBotSun, December 11, 2022 at 02:55 PM

Ticket closed by @kourinn. If there are any issues with it - it can be reopened by the owner or staff by using the buttons below or /open.

Ticket re-opened by @kourinn

Ticket closed by @kourinn. If there are any issues with it - it can be reopened by the owner or staff by using the buttons below or /open.

kolibri._.Sun, December 11, 2022 at 05:57 PM

I think this interval is affected by hitlag btw. See this vid by BowTae which is at 30 fps: https://youtu.be/sswkQCaTqzY?t=15
~15.2s dash 1 starts
~16.2s dash 2 starts
-> 1s between dashes but dash cooldown was still triggered
The amount of hitlag in that interval was 3f + 3f = 6f in total which is 6/30 = 0.2s at 30 fps.
1s - 0.2s = 0.8s

TiBotSun, December 11, 2022 at 09:16 PM

Ticket re-opened by @kourinn

Reply to

kolibri._.: I think this interval is affected by hitlag btw. See this vid by BowTae which is at 30 fps: https://youtu.be/sswkQCaTqzY?t=15

kourinnSun, December 11, 2022 at 09:30 PM

Thanks for the follow up. I hadn't considered hitlag extension. I tested this and can confirm your observation with BowTae's clip.
I uploaded my 120 fps test for hitlag extension here: https://youtu.be/tmIyJPkDFKk

second:frame
00:46    dash
01:50    N1 HL start
01:59    N1 HL ended
02:20    N2 HL start
02:29    N2 HL ended
02:38    dash
cooldown    (112-9-9)/120 = 94/120 = 0.7833s

07:44    dash
08:50    N1 HL start
08:59    N1 HL ended
09:20    N2 HL start
09:29    N2 HL ended
09:38    dash
no cooldown    (114-9-9)/120 = 96/120 = 0.8000s

Consecutive Dash Cooldown Trigger Hitlag Extension