The window title is "Fatal Error"
And the box says: "AllocBlock: Full"
This is urgent! The map needs to be finished soon, to take place in a competition! Plz help!
Mapping Problem - Urgent!
Created 18 years ago2006-02-19 14:23:42 UTC by
ChapterNine
Created 18 years ago2006-02-19 14:23:42 UTC by
ChapterNine
Posted 18 years ago2006-02-19 14:23:42 UTC
Post #163975
When I run my maps, the compiling works fine... But just when the game is about to start I get a "Fatal Error":
The window title is "Fatal Error"
And the box says: "AllocBlock: Full"
This is urgent! The map needs to be finished soon, to take place in a competition! Plz help!
The window title is "Fatal Error"
And the box says: "AllocBlock: Full"
This is urgent! The map needs to be finished soon, to take place in a competition! Plz help!
Posted 18 years ago2006-02-19 14:32:22 UTC
Post #163976
http://forums.gamedesign.net/viewtopic.php?t=50006&sid=88e933c375cea4f092107884541c2623 Check the third post out on this forum. Just an idea dont know too much about it myself.
Posted 18 years ago2006-02-19 17:49:00 UTC
Post #163987
allocblock:full
A tough one to figure out, vague error that usually shows up when you start the game or during compile, or even when WC/Hammer starts up - you have gone over the memory limit somewhere for some reason. It can be too little RAM (128M is about minimum), a leaf saw into leaf error, too long pathnames, too many textures, too big a level, too big or too many model/sprites, too big a wav sound file - or it could be that old "too many wads" mistake, a huge "noob" brush around the map to prevent leaks, too many SKY faces on hidden brush faces in the level - or even something else. Example: In early versions of NS, the 3D area info location entities were a major cause.
If it happens during compile, do not use WC/Hammer to "run" the map, but use a front end or batch file to compile with. You could also get more RAM.
(The following may still be handy, however be aware that Software mode allocates memory dynamicly, so it may automaticly seem to "fix" any error. Therefore the following info MAY lead you into a dead end:
Some brush-based entities have rendering properties that, when they interact in OpenGL/D3D video cards, they crash. Switch Half-Life to Software mode first, then load the map. If it loads you now know it is something that is handle different in software, then for Opengl/d3d check water, glows, additive, sprites, transparencies (illusionaries, windows, ect.), env_beams and so on.)
If it happens in opening a level in WC, it may be you have an animating model showing in one view. You must switch to single view instead of multiple, and try different ones until you get past it.
http://www.slackiller.com/tommy14/errors.htm
Best I can do. Sorry. Still semi-noob myself.
A tough one to figure out, vague error that usually shows up when you start the game or during compile, or even when WC/Hammer starts up - you have gone over the memory limit somewhere for some reason. It can be too little RAM (128M is about minimum), a leaf saw into leaf error, too long pathnames, too many textures, too big a level, too big or too many model/sprites, too big a wav sound file - or it could be that old "too many wads" mistake, a huge "noob" brush around the map to prevent leaks, too many SKY faces on hidden brush faces in the level - or even something else. Example: In early versions of NS, the 3D area info location entities were a major cause.
If it happens during compile, do not use WC/Hammer to "run" the map, but use a front end or batch file to compile with. You could also get more RAM.
(The following may still be handy, however be aware that Software mode allocates memory dynamicly, so it may automaticly seem to "fix" any error. Therefore the following info MAY lead you into a dead end:
Some brush-based entities have rendering properties that, when they interact in OpenGL/D3D video cards, they crash. Switch Half-Life to Software mode first, then load the map. If it loads you now know it is something that is handle different in software, then for Opengl/d3d check water, glows, additive, sprites, transparencies (illusionaries, windows, ect.), env_beams and so on.)
If it happens in opening a level in WC, it may be you have an animating model showing in one view. You must switch to single view instead of multiple, and try different ones until you get past it.
http://www.slackiller.com/tommy14/errors.htm
Best I can do. Sorry. Still semi-noob myself.
Posted 18 years ago2006-02-19 18:42:06 UTC
Post #163995
The problem is simple. You don't have enough virtual memory to finish the compiling procces. Don't touch your computer during compiling, don't even move your mouse and close all the unnessesry programs working at the same time. If that doesn't work try using batch compiling, it requires less virtual memory. If that doesn't work, try removing/rebuilding complex parts of your map and make them less complex. Take paticular attention to complex world brush work. Vis ignores entities and this problem usally happens in vis/rad so it may not be the problem. Brushes that create leaf saw into portal errors should be fixed, these always are in areas with very detailed world brushes.
If nothing else works then you need to upgrade your computer. :
If nothing else works then you need to upgrade your computer. :
Posted 18 years ago2006-02-20 12:01:50 UTC
Post #164065
SOLVED! It was some texture that messed up the entire level... But thank you guys, even if thishad nothing to do with RAM... 
You must be logged in to post a response.