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
With the introduction of helicopter loadouts the desynch between server and client is going to be much more noticeable as helicopters are much more readily watched and captured.
Describe the solution you'd like.
There should be a way to broadcast the pylon changes that we do, given that it's only done to active CAS, ASF, and attack helicopters it's likely an acceptable performance cost as it'll be ran half a dozen times at most during a short time period.
Alternative solutions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Work out whether setPylonLoadout has any built-in JIP support, or we have to fudge something awful.
Work out whether this statement in setPylonLoadout docs is true: This command also adds the corresponding weapon if the vehicle does not have one, but will not remove one that is no longer used.
Check the total cost of any solution in JIP queue messages. Given how badly designed the pylon system is, it might be disastrous to broadcast.
Is the requested change related to a problem?
With the introduction of helicopter loadouts the desynch between server and client is going to be much more noticeable as helicopters are much more readily watched and captured.
Describe the solution you'd like.
There should be a way to broadcast the pylon changes that we do, given that it's only done to active CAS, ASF, and attack helicopters it's likely an acceptable performance cost as it'll be ran half a dozen times at most during a short time period.
Alternative solutions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: