-
Notifications
You must be signed in to change notification settings - Fork 631
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
[HL25] TFC Update - Client crashes with no warnings #3843
Comments
Hello @DarthMan, it's not clear if you're referring to Team Fortress Classic or Half-Life here. Also, a quick search for bm_consequences_b3 didn't give a strong result. Can you provide a convenience link for a goldsrc dev to use? |
I am referring to Team Fortress Classic. The map is not available on the internet, as it's only playable on the Feckin Mad FM FUN server. |
Another thing to note here, it turns out that if you run the map on the latest TFC build and 25th anniversary build, all of the entities are invisible. Only the worldspawn is visible, and effects such as lasers etc. But doors that can be opened, glasses that can be damaged etc are not visible. No such issues are present on the old build. |
I think the problem is this map. I tried it on rehlds but it never worked. it gives segmentation fault... tested on |
The map runs just fine on my side under ReHLDS, the only issue is with players using the new TFC build. I only tested under Windows, so unsure about Linux. But I can say that there are no issues with stock HLDS under Linux. |
just a little heads up. we sorta found out the issue, and the map author "fixed" it.
i would love, if someone from Valve would have any idea what changed in that department. |
|
Hello,
After the new TFC update, there are some custom-made maps by the TFC community where users will crash in certaion sections.
One example that I can think of is the escape TFC map, bm_consequences_b3, in the vent section.
Hopefully more updates will be released in the future that will fix bugs, including this one.
Thanks :)
The text was updated successfully, but these errors were encountered: