C++ is m_flPlaybackRate usable to resolve byaw in CS:GO 2023?

[iliiakalamec]

heard that playbackrate is most accurate thing in resolving byaw, is it and how do i work with it? currently im using feetyaw eyeyaw diff method with clamping through m_fFlags and vecvelocity. I already tried to make resolver with pbr, but i give 0 goshs how should i use it and i think @potroshitel is bipolar

 

[eonex]

heard that playbackrate is most accurate thing in resolving byaw, is it and how do i work with it? currently im using feetyaw eyeyaw diff method with clamping through m_fFlags and vecvelocity. I already tried to make resolver with pbr, but i give 0 goshs how should i use it and i think @potroshitel is bipolar

xd

 

[iliiakalamec]

xd

persona im serious im a bit new in making resolvers that arent diff eye feet

 

[eonex]

persona im serious im a bit new in making resolvers that arent diff eye feet

hmm

 

[calloc0x75]

heard that playbackrate is most accurate thing in resolving byaw, is it and how do i work with it? currently im using feetyaw eyeyaw diff method with clamping through m_fFlags and vecvelocity. I already tried to make resolver with pbr, but i give 0 goshs how should i use it and i think @potroshitel is bipolar

Yes and No, Playback rate is reliable for resolving BYaw because the engine ties m_flAnimationPlaybackRate to the relation between velocity direction and feet yaw, this means even if you see the fake yaw it will free which side the desync is actually happening on.

So what you wanna do is compute the expected playback rate for L/R yaws and compare them against the captured networked value, and from there which ever sides prediction is the closest wins. This will only really work reliably when the player is moving id say faster than 30u +/- but yea you should use it alongside eye/feet yaw diff rather than it being your standalone main resolving method.

writing ts drunk ash btw so excuse bad writing thanks.