-
-
Notifications
You must be signed in to change notification settings - Fork 79
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: Server crashes on changelevel after map vote (0.8.6) #241
Comments
Hey! Apologies for not replying earlier. As far as I know, the crash is not because of MatchZy, hence nothing can be done from the plugin side. Maybe you can try setting tv delay as 0 rather than disabling CSTV, as there were some findings that tv_delay can cause crashes on map change. Thanks! |
We tried setting This issue was created in CSS repo: roflmuffin/CounterStrikeSharp#646 Seems like the crash on changing the map while recording a demo returned. |
This issue has been fixed with the latest update for CounterStrikeSharp. |
Will test, thanks! |
I'm having this problem. Updating CSS to v291 did not help. Can anyone help? |
We are having a game on Wednesday. Will test again and post the result here. Maybe the latest CS2 update broke some signatures again. |
Disabling auto record with tv_autorecord 0 was a workaround here, if anyone's interested. |
Does the plugin still record parseable demos with this cvar? |
I don't think so. |
@batmacumba We played a full BO3 today using previous version of MatchZy and the current version of CS#. No crashes, demos recorded correctly. |
Since nobody replied to me in the first thread for this bug creating new issue. The problem is still the same as before. Still happening on
0.8.6.
I just updated everything to the latest version. If the map is changed before match, it will successfully change. However if it happens right after the match it will crash the server! Disabling HLTV (tv_enable 0
) overcomes it for now, but having HLTV is nice, so please have a look at it. Thanks!Here are the logs:
The text was updated successfully, but these errors were encountered: