-
Notifications
You must be signed in to change notification settings - Fork 740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cookoff - Fix shell detonation #6979
Cookoff - Fix shell detonation #6979
Conversation
This reverts commit bcb4214.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Great this must be it ! |
@@ -87,7 +87,7 @@ if (_amountOfMagazines > 0) exitWith { | |||
playSound3D [_sound, objNull, false, (getPosASL _vehicle), 2, 1, 1300]; | |||
|
|||
if (random 1 < 0.15) then { | |||
[_vehicle, _ammo, _speed, random 1 < 0.15] call _spawnProjectile; | |||
[_vehicle, _ammo, _speed, true] call _spawnProjectile; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't need the _flyAway parameter in _spawnProjectile if we always set it to true.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For shotgrenade
and a few others it is still randomized. See L97ff
Only thing missing here is I would have added a comment above this line explaining as much for future reference |
* abc * Revert "abc" This reverts commit bcb4214. * Update to current commit * ShotShell requires velocity to simulate itself, so always spawn it with velocity
When merged this pull request will:
ShotShell requires velocity to properly simulate itself, so when detonating ammo always give it velocity. The RHS vehicle example in the issue is just a ShotShell that looks like a missile
Example:
https://youtu.be/GinftkYl5Mo