You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fairly minor issue whereby getting in an aircraft as the pilot with a gunner seat will cause the weapons of said gunner to not be local, which makes sense. The result of this however is that it causes the weapon to stop firing by removing it as your active/selected until you cycle manual fire again (issue still present) or cycle the weapon (fixes the issue). No doubt some myriad of networking and vehicle loadout logic is causing the bug.
Workaround is simply to cycle weapons, but it's still slightly annoying as it will also reoccur on servicing. Annoying enough to raise but not to fix as of yet.
One potential solve will probably just be to strip and rearm based on the new locality, but this is a fair bit of processing for an issue like this (plus what happens when a gunner gets in) so it would be cleaner to somehow solve the locality however I'm not sure whether a solution exists there as you can't set locality of something that doesn't exist, and we already set the weapons over the network so their locality is fixed.
The text was updated successfully, but these errors were encountered:
Fairly minor issue whereby getting in an aircraft as the pilot with a gunner seat will cause the weapons of said gunner to not be local, which makes sense. The result of this however is that it causes the weapon to stop firing by removing it as your active/selected until you cycle manual fire again (issue still present) or cycle the weapon (fixes the issue). No doubt some myriad of networking and vehicle loadout logic is causing the bug.
Workaround is simply to cycle weapons, but it's still slightly annoying as it will also reoccur on servicing. Annoying enough to raise but not to fix as of yet.
One potential solve will probably just be to strip and rearm based on the new locality, but this is a fair bit of processing for an issue like this (plus what happens when a gunner gets in) so it would be cleaner to somehow solve the locality however I'm not sure whether a solution exists there as you can't set locality of something that doesn't exist, and we already set the weapons over the network so their locality is fixed.
The text was updated successfully, but these errors were encountered: