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

Playable units without a player never seem to clear #52

Open
pridit opened this issue Feb 13, 2022 · 7 comments
Open

Playable units without a player never seem to clear #52

pridit opened this issue Feb 13, 2022 · 7 comments
Assignees
Labels
bug Unexpected unintended behaviour

Comments

@pridit
Copy link
Member

pridit commented Feb 13, 2022

Gone back and forth through various functions, hiding, deleting, but they always seem to linger. I can't even figure out how to reproduce it as usually when players disconnect they automatically get cleared which happens for the majority, but just a few instances a day the unit remains in the world. Might not ever be able to get to the bottom of it until I can reproduce it.

Could be something to do with group, doesn't seem to reproduce when the player loses connection as I have tried doing that without this ever happening the unit always clears gracefully. Given they always seem to originate at spawn maybe it's related to disconnecting/going back to the lobby when loading in or something.

@pridit pridit added the bug Unexpected unintended behaviour label Feb 13, 2022
@pridit pridit self-assigned this Feb 13, 2022
@pridit
Copy link
Member Author

pridit commented Mar 27, 2022

This happens both dead and alive, I can't find a way to reproduce but people consistently seem to manage doing something that causes these units to stick around. In the most recent case someone is actively occupying the slot, but there is another unit sitting at spawn which is not controlled. This means the script to scan them won't find this unit, as the playable unit is assigned to an active player.

20220327152819_1

@pridit
Copy link
Member Author

pridit commented Mar 30, 2022

This may possibly be fixed as a result of a refactor to use onPlayerDisconnected - if these rogue units can be captured by that, then this will be fixable.

@pridit
Copy link
Member Author

pridit commented Apr 3, 2022

Still happens, though the unit was dead and the body could not be hidden. Seems to have been significantly curtailed but can't really know, and at the least this is a new symptom.

@pridit pridit closed this as completed May 4, 2022
@pridit
Copy link
Member Author

pridit commented May 4, 2022

Cause of this is respawning while the handlers are loading, so still probably possible to trigger by being killed but it's unlikely enough, with disabling the option from the menu, for me to not care.

@pridit pridit reopened this Nov 10, 2022
@pridit pridit closed this as completed Jan 2, 2023
@pridit pridit added the wontfix Not relevant / beyond scope / misaligns with vision label Jan 4, 2023
@pridit pridit reopened this Jan 29, 2023
@pridit pridit removed the wontfix Not relevant / beyond scope / misaligns with vision label Jan 29, 2023
@pridit
Copy link
Member Author

pridit commented Jan 29, 2023

This has been observed on a unit not in the spawn position, so there's a different issue happening that must be possible to fix.

@pridit
Copy link
Member Author

pridit commented Aug 5, 2023

Arma.2.Operation.Arrowhead.2023.08.05.-.17.03.09.03.mp4

Reproducible by gesturing then disconnecting, which causes the unit to linger and repeat their animation.

@pridit
Copy link
Member Author

pridit commented Aug 5, 2023

Fixed the above case on local dedi but didn't work on local mp. Will await to see this case actually resolved on server or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected unintended behaviour
Projects
None yet
Development

No branches or pull requests

1 participant