fast fire glitch

[JUNESYNGOTOFLEX]

if you take sg552/aug and hold fire (with scope) you fire speed is slowly than usually, but if you flags ~FL_ONGROUND you fire speed faster than m249, fix please

[aleeperezz16]

Is this a bug or it's intended? Conditions are made to take priority on firing when a player isn't on ground.

ReGameDLL_CS/regamedll/dlls/wpn_shared/wpn_aug.cpp

Lines 81 to 96 in b979b5e

	if (!(m_pPlayer->pev->flags & FL_ONGROUND))
	{
	AUGFire(0.035 + (0.4 * m_flAccuracy), 0.0825, FALSE);
	}
	else if (m_pPlayer->pev->velocity.Length2D() > 140)
	{
	AUGFire(0.035 + (0.07 * m_flAccuracy), 0.0825, FALSE);
	}
	else if (m_pPlayer->pev->fov == DEFAULT_FOV)
	{
	AUGFire(0.02 * m_flAccuracy, 0.0825, FALSE);
	}
	else
	{
	AUGFire(0.02 * m_flAccuracy, 0.135, FALSE);
	}

ReGameDLL_CS/regamedll/dlls/wpn_shared/wpn_sg552.cpp

Lines 80 to 95 in b979b5e

	if (!(m_pPlayer->pev->flags & FL_ONGROUND))
	{
	SG552Fire(0.035 + (0.45 * m_flAccuracy), 0.0825, FALSE);
	}
	else if (m_pPlayer->pev->velocity.Length2D() > 140)
	{
	SG552Fire(0.035 + (0.075 * m_flAccuracy), 0.0825, FALSE);
	}
	else if (m_pPlayer->pev->fov == DEFAULT_FOV)
	{
	SG552Fire(0.02 * m_flAccuracy, 0.0825, FALSE);
	}
	else
	{
	SG552Fire(0.02 * m_flAccuracy, 0.135, FALSE);
	}

[RauliTop]

It seems to be a bug because they forgot about check FOV for change Fire Speed (CycleTime) at that conditions.
You can verify the bug in a ladder with AUG or SG552 shooting with scope active.

Fixed by this (only on AUG, but you get the idea):
Or can move the FOV check inside AUGFire/SG552Fire and change CycleTime there

if (!(m_pPlayer->pev->flags & FL_ONGROUND)) 
{ 
 	if (m_pPlayer->pev->fov == DEFAULT_FOV) 
 	{ 
 	 	AUGFire(0.035 + (0.4 * m_flAccuracy), 0.0825, FALSE); 
 	} 
 	else 
 	{ 
 	 	AUGFire(0.035 + (0.4 * m_flAccuracy), 0.135, FALSE); 
  	}
} 
else if (m_pPlayer->pev->velocity.Length2D() > 140) 
{ 
 	if (m_pPlayer->pev->fov == DEFAULT_FOV) 
 	{ 
 	 	AUGFire(0.035 + (0.07 * m_flAccuracy), 0.0825, FALSE); 
 	} 
 	else 
 	{ 
 	 	AUGFire(0.035 + (0.07 * m_flAccuracy), 0.135, FALSE); 
  	}
} 
else if (m_pPlayer->pev->fov == DEFAULT_FOV) 
{ 
 	AUGFire(0.02 * m_flAccuracy, 0.0825, FALSE); 
} 
else 
{ 
 	AUGFire(0.02 * m_flAccuracy, 0.135, FALSE); 
}

[RauliTop]

What do you think @wopox1337?

[wopox1337]

At this point, we can't say for sure if this behavior is a bug or if it's designed that way. We could be guided by CSS & CS:GO, but it still doesn't seem right to determine the truth.

At the same time, I do not see a logical explanation for this behavior. If we keep changing the shared code of weapons for the server side, at some point in time we will get more and more out of sync with the client side (prediction) and this will adversely affect the overall experience of the game for the average player.

I propose to leave this behavior "as is".

[RauliTop]

If we keep changing the shared code of weapons for the server side, at some point in time we will get more and more out of sync with the client side (prediction) and this will adversely affect the overall experience of the game for the average player.

I propose to leave this behavior "as is".

but #670 is merged...