Skip to content
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

[Change Request]: Broadcast the pylon changes for aircarft #3467

Open
ante185 opened this issue Dec 12, 2024 · 1 comment
Open

[Change Request]: Broadcast the pylon changes for aircarft #3467

ante185 opened this issue Dec 12, 2024 · 1 comment
Labels
Change A change to existing functionality

Comments

@ante185
Copy link

ante185 commented Dec 12, 2024

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

@ante185 ante185 added the Change A change to existing functionality label Dec 12, 2024
@jaj22
Copy link

jaj22 commented Dec 12, 2024

Research work required:

  1. Work out whether setPylonLoadout has any built-in JIP support, or we have to fudge something awful.
  2. 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.
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Change A change to existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants