-
Notifications
You must be signed in to change notification settings - Fork 12
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
Can't see other players' lightsaber blades sometimes #38
Comments
Seems to be happening less. Anyone still reporting seeing this issue? |
I saw it happen yesterday when you were testing out the saber system. |
Happened today is well, definitely still a problem. Seems to only happen once per connect though. |
It was never dealt with, it doesn't need re-reporting kthx Sent from my Windows Phone From: Darth Futuzamailto:notifications@github.com Happened today is well, definitely still a problem. Seems to only happen once per connect though. Reply to this email directly or view it on GitHub: |
Just some more info with this bug: Occurs the first time a saber is activated by a player. On the player's client appears to be functioning, but to all other clients the saber will appear either invisible or as the last used weapon before the saber. It will still make saber sounds though and does saber damage. It will be temporary fixed for the remainder of the match, if the player switches to a different weapon and then back to the saber. If a new saber is purchased, it will also have the problem until the weapon is switched. |
It seems that it only fixes for clients that can see the switch (unknown if it fixes for everyone globally on the server or only those who actually within some sort of range/vision), it definitely doesn't work for clients that have recently connected to the server after the weapon swap workaround has occurred. |
Encountered this on Stoiss' server. Sometimes you can't see other players' lightsaber blades. Don't really have any explanation for reproducing the problem, or under what cases it happens unfortunately.
The text was updated successfully, but these errors were encountered: