Originally Posted by
Dirkjr
well then. I guess I will delete the props I just added.
Once they release the fix you should be able to use props just as you were before, as it is at the moment some sort of config is pointing towards old files, from what I understand this is something we generally can't change. Wish Valve would hurry up! This bug has been here since the update, I would of expected a patch to be released a day or so after.
Quite a few bug reports here:
https://github.com/ValveSoftware/Sou...mes/issues/287
Code:
Since HL2DM Steampipe:
1. The console has been filling up with Pre-cache loading model errors.
2. HL2DM noticably loads up slower than before, especially on maploads.
3. Player models automatically switch back to combines when changed to a rebel.
4. Source SDK is not working without having to waste diskspace as mentioned in my first post on this thread.
5. Editing a custom texture and looking at it in hammer, then compiling and going ingame takes twice as long because we now have to place our custom texture file in two locations - adding workload.
6. Sourcescheme.res file is not found and force crashes hammer when setup with the new /common layout.
7. Counter-strike source was just changed to steampipe and already CSS mappers are noticing the same fatal bugs as mentioned in this thread which could of been avoided and fixed.
8. People are getting VGUI error msgs boxes which force close hammer since the steampipe update.
Just looked at a bug report, seems that valve know about the issue and are working at it:
https://support.steampowered.com/kb_...7388-QPFN-2491
Code:
Bugs
Q. Where do I report a bug or give feedback for these changes?
For issues particular to gameservers, please send an email to the HLDS mailing list. (You can subscribe to this mailing list here.)
Otherwise, please communicate your feedback using the github bug database.
Q. What are the known issues?
Known bugs:
The dedicated server might fail to load the Steam libraries the first time you boot it. Booting it a second time will fix the problem.
The SDK and content creation tools have several major problems. Please bear with us, we are going to get these fixed soon. We don't have any intention of abandoning our content creators!