-
Notifications
You must be signed in to change notification settings - Fork 639
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
[HL1 Client] room_type stuck and stopsound needed applied #1144
Comments
Got a way to reproduce this? |
#299
If I get it right, room_type variable changes only when it's defined in a map. |
I see the issue, when you connect to a map we don't tell the client what the current room type is, I'll fix that. |
Thanks a lot Alfred, that means a lot. And I'll keep in touch for any rare/hidden bugs from my Linux HLDS SteamPipe server. |
Was this actually fixed? I tested this with a dedicated server (vanilla HL and CS) and the There is this line: Line 491 in c7240b9
But that's always been there. It resets the setting in singleplayer as expected. It does not work when connected to a dedicated server. |
…t, reset room_type to 0 on map change, save room_type and restore it when loading same map Resolves ValveSoftware/halflife#1144 Resolves ValveSoftware/halflife#2936
…lt, reset room_type to 0 on map change, save room_type and restore it when loading same map Resolves ValveSoftware/halflife#1144 Resolves ValveSoftware/halflife#2936
Hello when I play any HL1 mod with a echo Sound environment where the map goes to room_type 1 or 9 it stays like that where the sounds echo a bit but won't go back to the default room_type 0 for some reason, when I load nextmap on my HLDM SteamCMD server when datacore map gave me that room_type 9. Now I vaguely remember this occurs on some of the CS 1.6 and TFC like that shutdown2 train sound where I had to stop the annoy train noise repeating by typing "stopsound" in console.
Is there a way of execing the cfg automatically like autoexec.cfg "stopsound" or "room_type 0" used when loading nextmap?
The text was updated successfully, but these errors were encountered: