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

[Bug] sv_freezenonclients 1 seems broken #390

Closed
bstordeur opened this issue Nov 13, 2021 · 3 comments
Closed

[Bug] sv_freezenonclients 1 seems broken #390

bstordeur opened this issue Nov 13, 2021 · 3 comments
Labels

Comments

@bstordeur
Copy link

Using sv_freezenonclients 1 seems to also freeze the position of the client, until you unfreeze it, at which point it'll update your position if you moved while frozen.
In other engines you can continue to move around, it's very useful when testing new animations to check if stuff is working right, and just generally a nice debug tool to have.

@andrei-drexler
Copy link
Collaborator

It looks like this is a bug in the protocol extensions - same thing happens in QSS. As a workaround you can set cl_nopext 1, and then both QSS and vkQuake behave as expected with sv_freezenonclients 1.

@bstordeur
Copy link
Author

Ah, thanks for the work-around @andrei-drexler, hadn't noticed that was also an issue in newest QSS (previous versions didn't have the problem).
Not so clear to me what the consequences of leaving cl_nopext at 1 are though.

@Novum
Copy link
Owner

Novum commented Nov 14, 2021

cl_nopext approximately gives you vanilla QuakeSpasm behavior. Still think this is a bug.

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

No branches or pull requests

3 participants