Allocblock: Full

DarkATiDarkATi Revelation 22:17 Join Date: 2003-06-20 Member: 17532Members, Reinforced - Shadow
<div class="IPBDescription">Terrorizing My Map</div> Any information greatly appreciated. No clue how to fix this.

~ DarkATi

Comments

  • watch_me_diewatch_me_die Join Date: 2002-11-10 Member: 8107Members
    tommy is your friend...

    <!--QuoteBegin--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->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.<!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->
  • ParallaxParallax Join Date: 2002-11-08 Member: 7739Members, Constellation, Reinforced - Supporter
    For me, this was caused by having an invalid (concave) brush in my level. I just made the cordon smaller and smaller until it dissappeared, and then narrowed in until it contained only one brush. Then I fixed that brush and everything was fine.

    <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->

    -Tom
  • watch_me_diewatch_me_die Join Date: 2002-11-10 Member: 8107Members
    Also try running it through HLFix and see what it tells you <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
  • SnakeUbSnakeUb Join Date: 2003-07-02 Member: 17871Members, Constellation
    it means u ran out of memory so a leak or bad brush could cause it it can also be caused by a very complex mep or dodgy textures from when ive had it.
    try runing it through a batch compiler with nothing else in the background
    then
    try undoing the most recent changes before it happened to find the cause
  • DarkATiDarkATi Revelation 22:17 Join Date: 2003-06-20 Member: 17532Members, Reinforced - Shadow
    <!--QuoteBegin--snake_ub+Oct 14 2003, 12:10 PM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (snake_ub @ Oct 14 2003, 12:10 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> it means u ran out of memory so a leak or bad brush could cause it it can also be caused by a very complex mep or dodgy textures from when ive had it.
    try runing it through a batch compiler with nothing else in the background
    then
    try undoing the most recent changes before it happened to find the cause <!--QuoteEnd--> </td></tr></table><span class='postcolor'> <!--QuoteEEnd-->
    I wish I could undoe the last few changes, can't. Instead I'm reverting to a old backup which was made a week back, not much lost really. So problem fixed.

    ~ DarkATi
Sign In or Register to comment.