What are the best angles to resolve?

Ascended · 6 Авг 2020

+ - 3 : roflanBuldiga:

slashslashdel · 6 Авг 2020

//del

Memoriespt11 · 6 Авг 2020

[QUOTE = "KennySpag, post: 1627570, member: 214808"]
If Standing: + - 120 + - 58
If Moving: Low Velocity: + - 58
High Velocity: + - 28 (I Think)
In Air: + - 15 (I Think)
[/ QUOTE]
or you can just use what sharklazers uses a correct getmaxdesync and use the same switch case he used for max desync so like if max desync is over 35 say its 60 then brute 60 and if its below 35 then they are using sidemove and u can bruteforce 35 its pretty simple just look at his source its all there

HDTRPlayzZ · 6 Авг 2020

just use reverse setup velocity to get max desync angle so when enemy moves the desync angle gets clamped so you wont be trying to resolve someone using 58 when their max desync angle is smth like 29 at max velocity (i think 29 is max desync value for when moving at full speed on ground feel free to correct me) so you should try doing something like this when getting angles to resolve
float resolver_yaw = std :: clamp(58, 0, flMaxBodyYaw);
and bruteforce + - that angle and if you miss that just / 2 for a basic resolver if you wanna try make it hit more try doing smth to guess the enemy desync side it should help you hit more often

HDTRPlayzZ · 6 Авг 2020

[QUOTE = "Syznapse, post: 1627551, member: 273066"]
+ - 3: roflanBuldiga:
[/ QUOTE]
yes use this you will hit p all the time

Memoriespt11 · 6 Авг 2020

[QUOTE = "HDTRPlayzZ, post: 1627651, member: 211731"]
just use reverse setup velocity to get max desync angle so when enemy moves the desync angle gets clamped so you wont be trying to resolve someone using 58 when their max desync angle is smth like 29 at max velocity (i think 29 is max desync value for when moving at full speed on ground feel free to correct me) so you should try doing something like this when getting angles to resolve
float resolver_yaw = std :: clamp (58, 0, flMaxBodyYaw);
and bruteforce + - that angle and if you miss that just / 2 for a basic resolver if you wanna try make it hit more try doing smth to guess the enemy desync side it should help you hit more often
[/ QUOTE]
just to clarify for future reference max desync angle at full speed tested with scout 15 with auto 23 according to onetaps desync output values i did some testing and i wouldnt do that i'd still stick to updating the bruteforced angle per tick so that you never have ainvalid angle idk how to explain u can dm me on discord if you want more details and shit Memories#8221

HDTRPlayzZ · 6 Авг 2020

[QUOTE = "Memoriespt11, post: 1627656, member: 208317"]
[QUOTE = "HDTRPlayzZ, post: 1627651, member: 211731"]
just use reverse setup velocity to get max desync angle so when enemy moves the desync angle gets clamped so you wont be trying to resolve someone using 58 when their max desync angle is smth like 29 at max velocity (i think 29 is max desync value for when moving at full speed on ground feel free to correct me) so you should try doing something like this when getting angles to resolve
float resolver_yaw = std :: clamp (58, 0, flMaxBodyYaw);
and bruteforce + - that angle and if you miss that just / 2 for a basic resolver if you wanna try make it hit more try doing smth to guess the enemy desync side it should help you hit more often
[/ QUOTE]
just to clarify for future reference max desync angle at full speed tested with scout 15 with auto 23 according to onetaps desync output values i did some testing and i wouldnt do that i'd still stick to updating the bruteforced angle per tick so that you never have ainvalid angle idk how to explain u can dm me on discord if you want more details and shit Memories # 8221
[/ QUOTE]
its using maxbodyyaw tho from reversed setup velocity so dif values with dif guns shouldnt be an issue as it changes with the guns aswell as the speed so it will be settings itself to when an enemy is max speed with a gun to their max desync value shouldnt it?

dabbyso85 · 6 Авг 2020

Thanks for everyone leaving a comment, but I cant really understand what you are saying guys :D. My brain is too smol, but im very thankful for the time you spent on commenting.

dabbyso85 · 6 Авг 2020

prismA написал(а):
Stop being a idiot and doing things that you don't know how to do. It is simple. You are a begginer, doing a resolver that is really decent isn't something easy.You need to understand the game and his respective engine, to really know what the hell you are doing. If you plan to use randombruteforce, you should just don't do a resolver and focus on safepoint. You can easily achieve it by +60 and -60 in the player original (non-resolved) animation). After that you see the points that they got in common and give preference to them. Really simple and more useful that this shit that you call "resolver".

k

dabbyso85 · 6 Авг 2020

HDTRPlayzZ написал(а):
just use reverse setup velocity to get max desync angle so when enemy moves the desync angle gets clamped so you wont be trying to resolve someone using 58 when their max desync angle is smth like 29 at max velocity (i think 29 is max desync value for when moving at full speed on ground feel free to correct me) so you should try doing something like this when getting angles to resolve
float resolver_yaw = std :: clamp(58, 0, flMaxBodyYaw);
and bruteforce + - that angle and if you miss that just / 2 for a basic resolver if you wanna try make it hit more try doing smth to guess the enemy desync side it should help you hit more often

i think i have done something similar.

C++:

if (data->m_extending) {
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 58.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 58.f)));
        return flLeftFireYawDelta > flRightFireYawDelta ? -58.f : 58.f;
}
else
{
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 29.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 29.f)));
   
        return flLeftFireYawDelta > flRightFireYawDelta ? -29.f : 29.f;
}

Is that the right one?

deliorix · 6 Авг 2020

dabbyso85 написал(а):

i think i have done something similar.

C++:

if (data->m_extending) {
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 58.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 58.f)));
        return flLeftFireYawDelta > flRightFireYawDelta ? -58.f : 58.f;
}
else
{
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 29.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 29.f)));
 
        return flLeftFireYawDelta > flRightFireYawDelta ? -29.f : 29.f;
}

Is that the right one?

its pandora resolver... not yours

dabbyso85 · 6 Авг 2020

KennySpag написал(а):
If Standing: + - 120 + - 58
If Moving: Low Velocity: + - 58
High Velocity: + - 28 (I Think)
In Air: + - 15 (I Think)

Done, thanks for your reply!

C++:

    if (g_cl.m_speed < 3.5f) {
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 58.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 58.f)));
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 120.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 120.f)));

        return flLeftFireYawDelta > flRightFireYawDelta ? -58.f : 58.f;
        return flLeftFireYawDelta > flRightFireYawDelta ? -120.f : 120.f;
    }
    if (g_cl.m_speed > 3.5f && !g_movement.m_slow_motion) {
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 28.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 28.f)));
        
        return flLeftFireYawDelta > flRightFireYawDelta ? -28.f : 28.f;
    }
    if (!record->m_fFlags & FL_ONGROUND) {
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 15.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 15.f)));

        return flLeftFireYawDelta > flRightFireYawDelta ? -15.f : 15.f;
    }

dabbyso85 · 6 Авг 2020

deliorix написал(а):
its pandora resolver... not yours

yea

dabbyso85 · 6 Авг 2020

now im depressed

deliorix · 6 Авг 2020

dabbyso85 написал(а):

Done, thanks for your reply!

C++:

    if (g_cl.m_speed < 3.5f) {
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 58.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 58.f)));
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 120.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 120.f)));

        return flLeftFireYawDelta > flRightFireYawDelta ? -58.f : 58.f;
        return flLeftFireYawDelta > flRightFireYawDelta ? -120.f : 120.f;
    }
    if (g_cl.m_speed > 3.5f && !g_movement.m_slow_motion) {
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 28.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 28.f)));
       
        return flLeftFireYawDelta > flRightFireYawDelta ? -28.f : 28.f;
    }
    if (!record->m_fFlags & FL_ONGROUND) {
        float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 15.f)));
        float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 15.f)));

        return flLeftFireYawDelta > flRightFireYawDelta ? -15.f : 15.f;
    }

max desync angle = 60. why you using 120?

C++:

float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 120.f)));
float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 120.f)));

dabbyso85 · 6 Авг 2020

deliorix написал(а):
max desync angle = 60. why you using 120?

C++:

float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 120.f))); float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 120.f)));

wooops my bad

choca · 6 Авг 2020

Disorder написал(а):
-380 +180 p neverlose resolver

HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAH
@Soufiw
Here's a meme.

choca · 6 Авг 2020

Disorder написал(а):
y

Yeah neverlose obviously bruteforces the angles 180 and 360.

choca · 6 Авг 2020

deliorix написал(а):
max desync angle = 60. why you using 120?

C++:

float flLeftFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y + 120.f))); float flRightFireYawDelta = fabsf(math::NormalizedAngle(flPseudoFireYaw - (record->m_angEyeAngles.y - 120.f)));

wdym MaxBodydelta = 58

Gambino · 6 Авг 2020

choca написал(а):
wdym MaxBodydelta = 58

It gets clamped anyways.

What are the best angles to resolve?

Похожие темы