OK everyone, here's the scoop on why deleting the HPK seems to help. HL has to cache a lookup table for the HPK.
If the cache is large it occupies memory that could otherwise be used when the models problem happens. This "memory can't be read error" is all about memory usage and if you decrease the inital overhead then you'll provide more working memory for the problem. Unfortunately it won't fix the problem, it just happens later after n+ more events happen. Since other players (but not all) are being kicked when one player fires the shotgun (as one example) this means the problem is an observed phenomena, players not in visible range won't be kicked (and won't show the model problem). Same thing with zoom. If you're zoomed and looking at someone firing the shotgun you'll get kicked, but if you're zoomed and someone next to you is firing the shotgun, you won't be kicked >UNLESS< you unzoom before the decay time, see all the shells around you then blam, you're gone. So deleting the HPK will help if it's largish to huge but doesn't actually fix the problem. qUiCkSiLvEr ----- Original Message ----- From: James Nine sent: Saturday, July 24, 2004 5:17 AM Deleting custom.hpk seems to work, but it still complains, and it doesn't show brass ejections. ----- Original Message ----- From: "Wrench" > Sent: Saturday, July 24, 2004 7:19 AM > The error was occurring for me whenever I was scoped in right after I fired > on cs_assault and on a custom map sct_box. After that happened about 6 > times, I deleted the clientregistry.blob and custom.hpk (I know it only has > sprays but thought it was a good time to clean up this file too). This > cleared up the problem for me, another clan member, and several server > regulars. We went to de_airstrip and when the CTs got to the T in the tunnel > outside of the T spawn one of the CTs shot with a shotgun and that gave all > 4 of us the error at the time the shot gun was fired. The last sound I heard > was the shotgun. Then I deleted the clientregistry.blob in the c:\hlserver > directory and ran the hldsupdatetool for valve and cs. The problem has not > occurred since I did this and without the new mp.dll Alfred created. > > Alfred I have the mini dump files from my CS client if they will help. > > I'm trying to better understand this glitch and I have a question. What was > happening with this error, was it client or server side or a mismatch of > client/server files? > > Wrench > > > > Message: 10 > > From: "Kevin Ottalini" > > Subject: Re: [hlds] Memory Can't be Read (and Linux equivalent) > > Date: Fri, 23 Jul 2004 23:24:23 -0700 > > > > Make sure you download that zip at least twice and check the size, > > the first time you download the file may be truncated. > > > > I'm setting up two CS test servers right now: > > > > 67.100.129.85:27016 - current build CS Win32 10 slots, stock maps > > > > 67.100.129.82:27016 - Alfred's MP.DLL CS Win32 10 slots, stock maps > > > > My dsl line can't handle 20 players but I don't expect them to fill up so > we > > should be ok. > > > > If anyone gets the memory error, please re-join and let me know. > > > > qUiCkSiLvEr > > > > ----- Original Message ----- > > From: Alfred Reynolds > > Sent: Friday, July 23, 2004 9:49 PM > > > > I have been unable to reproduce the crash locally but I have a couple > > suspects based on various reports. I have built a new game server binary > > for cstrike (and cstrike only!), if you want to test it get it from: > > http://www.steampowered.com/mp.zip > > > > This is for windows only (the problem I suspect is not present in the > > linux build). I would appreciate any feedback on this binary, and any > > precise repro reports for the bug (i.e a small set of steps that always > > cause the crash). > > > > - Alfred > > > > ----Original Message---- > > From: Wrench > > Sent: > > Friday, July 23, 2004 9:07 PM > > > > > I had the same problem with my client and HLDS CS server. > > > > > For the client I deleted the clientregistry.blob and custom.hpk > > > restarted steam and let it update. I saved my mini dump files if > > > they'll help Quicksilver and I have the server logs too. I've looked > > > through the server logs but didn't see anything unusual except a lot > > > of client disconnects. > > > > > > After doing this I still had the problem with the shot gun crashing > > > the cs client to windows with the memory error, but the problem with > > > the scoped weapons seemed to be fixed. > > > > > > I thought it might be a file mismatch between the client and server > > > even though the server had been updated last night so I wasn't real > > > sure. But for the heck of it, I took the server offline, deleted the > > > clientregistry.blob from the hlserver directory, ran the > > > hldsupdatetool for valve and cs, and restarted the server. I've been > > > in there since I tried this workaround and haven't had anymore > > > problems in over 5 hours. I'm not sure exactly what happened with the > > > clientregistry.blob for the server but its seemed to fix the problem > > > tonight. > > > > > > Wrench > > > > > > > > > > > > From: "Kevin Ottalini" > > > <[EMAIL PROTECTED]> > > > Date: Fri, 23 Jul 2004 02:07:11 -0700 > > > > > > If you are getting this error on your server or have groups of > > > players > > > getting disconnected by this error (on their side) I need to know > > > the > > > exact error messages that you and they are seeing, screenshots > > > would be welcome. > > > > > > I visited 6 or 7 CS servers and in about 1/2 of them when I asked, > > > players reported getting this error. > > > > > > PM me screenshots if you want. > > > > > > qUiCkSiLvEr _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
