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

You can switch to metabolize regardless of legacy option #5

Open
GhoulofGSG9 opened this issue May 6, 2018 · 1 comment
Open

You can switch to metabolize regardless of legacy option #5

GhoulofGSG9 opened this issue May 6, 2018 · 1 comment
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@GhoulofGSG9
Copy link
Member

Issue by keatsandyeats
Saturday Apr 07, 2018 at 20:29 GMT
Originally opened as Mendasp#84


As of Mendasp@25ce33d:
With the legacy weapon switch option disabled, pressing the key for second weapon slot (2 by default) will switch to metabolize briefly, then return to your previous weapon. (With the legacy option enabled, it seems to work ok.)

@GhoulofGSG9
Copy link
Member Author

Comment by GhoulofGSG9
Sunday Apr 08, 2018 at 10:20 GMT


You can't switch to metabolize. The client prediction just thinks you can do, so if you press 2 the HUD will show for a few frames that you are switching to metabolize while you are not really switching to it at all. To fully fix this visual glitch I still need to figure out a way to propagate the option's value to the predict world.

I tried a client -> server -> predict network message pipeline but for whatever reason the network message hook doesn't trigger in predict.

Of course we could read the options.xml directly while running the prediction but that wouldn't detect any change of the option's value without an unreasonable amount of file sampling.

@GhoulofGSG9 GhoulofGSG9 added bug Something isn't working wontfix This will not be worked on labels Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant