Fix throwable weapon throw distance on high FPS

[MohabCodeX]

Problem

1. Throw Force: On high FPS, throwing animations reach the release keyframe faster in real time (355ms for satchels, 441ms for grenades) before m_ButtonCounter reaches its native ceiling (433ms/533ms), resulting in lower launch velocity.
2. Landing Distance: Discrete 30 FPS Euler integration moves the projectile ~26cm forward in its final landing frame before collision is registered. High FPS samples contact continuously, eliminating this step overshoot.

Solution

Instead of hooking CObject::ProcessControl (which affects all world objects and only accounts for ~4cm of slide), we hook CTaskSimpleThrowProjectile::ProcessPed at 0x62B01E:

• Normalizes full-charge throws to the native ceiling when held until release.
• Enforces 160ms floor for quick-taps and rescales partial holds linearly.
• Applies timeStep-based compensation for satchels to ensure identical landing distance (~6.33m) across 30, 60, and 240+ FPS.

Testing

Before/After: https://streamable.com/mh6eue

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.