Hammer freeze on quick compile at portal flow

Discussion in 'Mapping Questions & Discussion' started by Unh3lpful, May 11, 2015.

  1. Unh3lpful

    Unh3lpful L2: Junior Member

    Messages:
    95
    Positive Ratings:
    57
    I'm building my map and everything was going fine, but recently I cannot use the run map feature because it freezes at the portal flow counting. I was wondering what is causing this and how I can fix this.

    Here's this. Also, when I compile I notice it has quite a few errors so I was wondering if it was this?
     
    Last edited: May 11, 2015
  2. Vel0city

    aa Vel0city func_fish

    Messages:
    1,938
    Positive Ratings:
    1,542
    Depends on the errors. And what do you mean by quick compile? Set everything to fast?

    It's common for Hammer to become unresponsive during certain parts of the compile process. Compiling takes up all your processing cores, unless you tell Hammer to work with less cores.

    Also, try using a different compiler, lik VBCT. Maybe that works.
     
  3. Unh3lpful

    Unh3lpful L2: Junior Member

    Messages:
    95
    Positive Ratings:
    57
    I managed to get a picture of the errors. By quick compile I mean the run map (F9).

    [​IMG]
     
  4. Vel0city

    aa Vel0city func_fish

    Messages:
    1,938
    Positive Ratings:
    1,542
    Copy and paste the compile log here. It's a compile log checker that checks for errors in your compile log and then says what to do to fix those errors.
     
  5. Unh3lpful

    Unh3lpful L2: Junior Member

    Messages:
    95
    Positive Ratings:
    57
    I can't get the compile log onto my clipboard, it keeps going into not responding.
     
  6. Vel0city

    aa Vel0city func_fish

    Messages:
    1,938
    Positive Ratings:
    1,542
    Well, your compile log says it has issues with some of your displacements doing weird stuff. Try recreating them. Also, it's perfectly normal for the compiler to go into not responding. Compiling takes up a lot of computer power. Let it do its thing for a while before trying anything else with your pc, assuming it doesn't get stuck on the VBSP part.
     
  7. Pocket

    aa Pocket func_croc

    Messages:
    4,489
    Positive Ratings:
    2,377
    Yeah, in 2007 Microsoft decided to make it so that if a window isn't interactable, it automatically assumes the program has crashed and refuses to let it update the window anymore, even though that makes no goddamn sense since if it's still trying to update the window then it clearly hasn't crashed...

    ...Anyway, Valve never bothered to update Hammer's compiler to get around that. Wouldn't really be surprised if they don't even use the built-in compiler and just run it manually from the command line, or maybe send it into a batch process that runs on the company mainframe.
     
  8. Vel0city

    aa Vel0city func_fish

    Messages:
    1,938
    Positive Ratings:
    1,542
    Yay for Microsoft AND Valve. GG to both.