Fix setPedControlState is aborted when ped created

[FileEX]

Fix #1201 and probably #3867

The bug is caused by m_sScriptedStates being static, which led to the variable being reset by the CClientPad constructor after creating a ped

mtasa-blue/Client/mods/deathmatch/logic/CClientPad.cpp

Lines 120 to 125 in e831f62

	// Initialise our analog control states
	for (unsigned int i = 0; i < MAX_GTA_ANALOG_CONTROLS; i++)
	{
	m_sScriptedStates[i] = CS_NAN;
	m_bScriptedStatesNextFrameOverride[i] = false;
	}

[botder]

And why did you de-static these values intead of moving the reset out of that constructor or doing that once?

[FileEX]

And why did you de-static these values intead of moving the reset out of that constructor or doing that once?

Don't other peds need their own 'scriptedStates'? Does this only apply to the local player?

[botder]

We have two functions setPedAnalogControlState and setAnalogControlState. I don't know how these functions differ right now.

Every CClientPed has an instance of CClientPad m_Pad. And the default constructor of CClientPad initializes the static variables everytime. The simplest solution would be to move the initialization out of the default constructor and offer a static function that gets called whenever we create the local player's ped.

[FileEX]

We have two functions setPedAnalogControlState and setAnalogControlState. I don't know how these functions differ right now.

Every CClientPed has an instance of CClientPad m_Pad. And the default constructor of CClientPad initializes the static variables everytime. The simplest solution would be to move the initialization out of the default constructor and offer a static function that gets called whenever we create the local player's ped.

Done