ti|T
25-07-2004, 02:02
Come riportato su www.counterstrike.it pare che sia stato individuato il problema che provoca l'errore di memoria dall'ultimo update.
Ecco i post ufficiali dai forum steampowered.com
Originally posted by qUiCkSiLvEr
That model error is one symptom of the problem, it happens when you shoot one of three weapons.
These three weapons are the only ones that caused the problem
(terrorist names, I don't know the CT names):
Leone 12 Gauge Super
Schmidt Scout
Magnum Sniper Rifle
This is typical of the model error message:
No model -504!
The numbers are completely variable and can change depending on how many events have been happening (IE: the number itself doesn't mean anything).
quickswitching isn't related, just firing the weapon is important.
NOTE: You don't have to have the weapon yourself to get crashed, you just have to be near / see / hear a player with one of the offending weapons.
If you are visible / audible distance of the weapon when its fired you also will see the model error.
If you are zoomed you might not be able to see the shells or whatever it is that is causing the problem so you might not crash, but if you unzoom and there are a bunch of spent shells around you then you might crash immediately as soon as they are rendered.
If there are too many of these errors in a row then you and everyone that sees/hears enough of them will crash out.
That means if you have 5 players in the same area all shooting that shotgun (for example) all 5 of you will all crash very quickly.
If you have a large Custom.HPK file, the index table for it fills up some of your memory and aggrevates the problem.
If you put in a bogus classmenu.res file, that might also (sometimes) decrease some of the temporary memory usage and might delay the crash (but it won't fix it).
This current error is actually unrelated to the memory error that this thread was originally talking about ... the thread has effectively been hijacked by the same error message but a different cause ... <sigh>
Still they all need to be fixed, please be patient everyone.
Pare che entrando in zone dove i giocatori usano determinate armi, si verifichi il crash.
E' scritto che e' possibile migliorare la situazione, non risolverla per il momento, eliminando il file custom.hpk che contiene gli spray degli altri giocatori (io ho cl_allowdownload a 0, con 50kb di file, ma ho lo stesso i crash).
Originally posted by qUiCkSiLvEr
One thing that everyone can do that will help this problem is:
go delete your custom.hpk file.
Look in your MOD directory:
C:\Program Files\Steam\SteamApps\<account>\counter-strike\cstrike\custom.hpk
This file just stores all the other player's sprays and isn't an important file,
but it can get very large and take up a fair amount of memory.
HL will re-create it again, but you might want to limit the size by setting this CVAR:
hpk_maxsize 1.0
This will limit the custom.hpk file to 1 megabyte.
The default is hpk_maxsize "0" which means unlimited size.
This will give you a little more memory and may decrease the number of times that this problem happens.
Before you delete it look at your file size and report back here on how big the file is.
This is not a fix, it's just a 'help" for the problem.
Ecco i post ufficiali dai forum steampowered.com
Originally posted by qUiCkSiLvEr
That model error is one symptom of the problem, it happens when you shoot one of three weapons.
These three weapons are the only ones that caused the problem
(terrorist names, I don't know the CT names):
Leone 12 Gauge Super
Schmidt Scout
Magnum Sniper Rifle
This is typical of the model error message:
No model -504!
The numbers are completely variable and can change depending on how many events have been happening (IE: the number itself doesn't mean anything).
quickswitching isn't related, just firing the weapon is important.
NOTE: You don't have to have the weapon yourself to get crashed, you just have to be near / see / hear a player with one of the offending weapons.
If you are visible / audible distance of the weapon when its fired you also will see the model error.
If you are zoomed you might not be able to see the shells or whatever it is that is causing the problem so you might not crash, but if you unzoom and there are a bunch of spent shells around you then you might crash immediately as soon as they are rendered.
If there are too many of these errors in a row then you and everyone that sees/hears enough of them will crash out.
That means if you have 5 players in the same area all shooting that shotgun (for example) all 5 of you will all crash very quickly.
If you have a large Custom.HPK file, the index table for it fills up some of your memory and aggrevates the problem.
If you put in a bogus classmenu.res file, that might also (sometimes) decrease some of the temporary memory usage and might delay the crash (but it won't fix it).
This current error is actually unrelated to the memory error that this thread was originally talking about ... the thread has effectively been hijacked by the same error message but a different cause ... <sigh>
Still they all need to be fixed, please be patient everyone.
Pare che entrando in zone dove i giocatori usano determinate armi, si verifichi il crash.
E' scritto che e' possibile migliorare la situazione, non risolverla per il momento, eliminando il file custom.hpk che contiene gli spray degli altri giocatori (io ho cl_allowdownload a 0, con 50kb di file, ma ho lo stesso i crash).
Originally posted by qUiCkSiLvEr
One thing that everyone can do that will help this problem is:
go delete your custom.hpk file.
Look in your MOD directory:
C:\Program Files\Steam\SteamApps\<account>\counter-strike\cstrike\custom.hpk
This file just stores all the other player's sprays and isn't an important file,
but it can get very large and take up a fair amount of memory.
HL will re-create it again, but you might want to limit the size by setting this CVAR:
hpk_maxsize 1.0
This will limit the custom.hpk file to 1 megabyte.
The default is hpk_maxsize "0" which means unlimited size.
This will give you a little more memory and may decrease the number of times that this problem happens.
Before you delete it look at your file size and report back here on how big the file is.
This is not a fix, it's just a 'help" for the problem.