SDK Known Issues List
This page contains the list of current known issues in the SDK
Server: weapon_citizensuitcase Assert on startup
Workaround: Install copy of the SP SDK, then copy the scripts/ directory over
Server: Some bullet weapons set to do 0 damage.
Workaround: Need to edit their AddAmmoType which are strangely set to 0 for some reason.
Server: Some projectile weapons set to do 0 damage.
Workaround: Need to edit their source files and set a damage.
Client: --- Missing Vgui material vgui/steam/games/icon_cz
Workaround: Manually extract files from GCF and copy them into your mod directory? Haven't tried this. There must be a better way.
Server: The crossbow causes an assertion failure.
Workaround: Comment out ai_activity.cpp line 53. This doesn't appear to be something that can be fixed in code?
Server? Client?: RL explosion invisible, per http://www.chatbear.com/board.plm?a=viewthread&t=970,1107153392,30132&id=786504&b=4991&v=flatold
Workaround: No known workaround.
util.cpp (531) : Assertion Failed: !"UTIL_GetLocalPlayer"
Workaround: See the patch below.
Assert !"UTIL_GetLocalPlayer" when using combine ball
Workaround: See the patch below.
CreateEvent: event 'break_prop' not registered
Significance and fix both unknown
HL2.exe mysteriously segfaults if you forget to put the client.dll and server.dll in your mod's bin directory
Workaround: Don't do that.
If you leave a server online on a certain map for roughly 12-24 hours straight, it begins using 100% CPU. Possibly a core srcds.exe bug, not an SDK bug?
I suppose there could be some array or something inside the HL2 core that grows over time, and must be iterated over each frame?
I haven't run the long-running map scenario in a long time. The alpha server for my mod is full most of the day and players frag out so the map is always changing.
That said, I seem to recall that the move from the usual 5% cpu to 100% cpu was fairly drastic and immediate. I never saw an intermediate stage where the server used 25% cpu or 50% cpu etc. I would expect to see those intermediate levels if it was a memory leak.
Workaround: Ensure you have mp_timelimit set to something nonzero, but less than 12 hours or so.
Negative entitygroundcontact crash
Workaround: See patch below
Doing a 360 quickly with the Stun Baton as your active weapon causes the screen to flash white
Fix unknown