-
Notifications
You must be signed in to change notification settings - Fork 74
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
[SteamPipe][DoD:S] sv_pure blocks necessary textures #259
Comments
|
I've reported a texture issue as well with sv_pure 2, not sure if it's related, but might be. http://steamcommunity.com/sharedfiles/filedetails/?id=134477242 |
|
Yeah same on our dods servers, sv_pure 1/2 both cause this. Disconnect client and rejoin the server and its ok. If no one leaves to reconnect then clients and server can crash. |
|
Also deletes ramps in surf_greatriver_fix5 for CS:S. I've tried whitelisting the erroneous console feedback (which you receive after mapchange) with no luck, but to be honest, I'm not quite sure what I'm doing, there. To confirm, after being present for a mapchange in a server with sv_pure on, the error occurs, and continues to occur on all servers (maps) until the client is restarted. |
|
I've heard reports that this is happening on CS:S and TF2 SteamPipe, with TF2 having the purple/black checkboard instead of transparent textures/wireframes. |
|
Sometimes wireframe, and more commonly, wireframes that are displaying erratically around the map, appearing more like a rendering error than anything. |
|
Almost certainly same as #341 |
|
Fix is going to be released in a prerelease build today. If no major problems, will ship to main branch tomorrow. |
|
The fix for this was released a few days ago. I should have closed it then. Is it still happening? |
Hi there,
it looks like sv_pure (2) blocks textures on several maps. I played dod_argentan twice today and recognized that the wooden ground texture and some others, too were missing. After playing dod_salerno (custom map) twice, it's radar background disappeared. Strange.
Here is a screenshot of it:

I think this bug is clientside (Windows) because the bug seems to disappear after restarting the client and rejoining the server.
The text was updated successfully, but these errors were encountered: