Hammer error!!

Discussion in 'General Chat' started by Bulletproof, 2 Sep 2009.

  1. Bulletproof Last one alive, Lock the door.

    Hammer error!!

    Ok, im making a css bhop map on hammer. Whenever i create a func or trigger something like that when i click off it to do something else on the map i get this error and it closes down .... Id'e just set my floor to be a teleport and i clicked the orange at the side then error. Do any of you know what it is and how i can solve it?

    [​IMG]
     
    Last edited by a moderator: 28 Dec 2016
  2. Bulletproof Last one alive, Lock the door.

    Re: Hammer error!!

    Also after iv'e made something like that I cant place an entity
     
  3. Geit Coding wizard!

    Re: Hammer error!!

    If it's consistently happening;

    Restart Steam
    If it still happens;
    Reinstall the SDK
     
  4. Bulletproof Last one alive, Lock the door.

    Re: Hammer error!!

    The restart worked, thanks :)
     
  5. BeauChaotica bodyshot noob

    Re: Hammer error!!

    Was this the error?
     

    Attached Files:

  6. Gaw discord is my friend now

    Re: Hammer error!!

    The only way to make the error go away completely, is to upgrade your RAM, that's pretty much why it happens.
     
  7. Re: Hammer error!!

    Memory doesn't just corrupt from bad/inadequate hardware
     
  8. Geit Coding wizard!

    Re: Hammer error!!

    Under the source engine, that error can be caused by thousands of things (In TF2) Here's a nice list;


    • model entities or sound entities with no models or sounds specified
    • invalid brushes (that somehow got past hammer, vbsp and vrad)
    • too many of a certain kind of thing (eg entities) in your map
    • too long or invalid filenames/paths
    • intersecting brushes
    • intersecting entities
    • the use of infinites (including zero) in any entitiy
    • path entities linking to themselves
    • entities triggering themselves (infinite loop)
    • physics anomalies (including too complex stuff), like towers or constraintsystems that hang onto themselves
    • bad models
    • bad collisions
    • bad entity naming (only use 0-9, a-z, A-Z, and '_'. for special occasions, you may use '*' or '!'. Not avoiding curly brackets or quotes will make your map crash, and become unreopenable.
    • linking to non-existant entities
    • using bad textures or other resources
    • normals in a funky direction
    • bad map (BSP structure, or a bit messed up)
    • hardware anomalies
    • software anomalies
    • making unexpected constructions (non-geometric, mean I/O's and physics)

    In Hammer, the list is probably just as big.
     

Users Viewing Thread (Users: 0, Guests: 0)