Whenever I try to compile my map, it compiles the wrong version.

Discussion in 'Mapping Questions & Discussion' started by Kazagin, Aug 6, 2009.

  1. Kazagin

    Kazagin L3: Member

    Messages:
    130
    Positive Ratings:
    9
    I compiled my map last night because I wanted to see if I made any mistakes yet, and it ran fine.
    I realized that the volcano's slope was too hard to walk up without problems, so I added a flight of stairs (They are props, by the way) going up the volcano in front of either spawn.
    I also added a Raygun at the top, along with a platform and a few other tid-bits.
    Now, when I try to compile my map, it runs the old version.

    Why is it doing this and how do I fix it?
     
  2. DJive

    aa DJive Cake or Death?

    Messages:
    1,466
    Positive Ratings:
    736
    You have a leak, so it never saves the new compile.
     
  3. Kazagin

    Kazagin L3: Member

    Messages:
    130
    Positive Ratings:
    9
    Is there a list of everything that causes leaks?
    I checked my Skybox, and everything is inside it.
     
  4. A Boojum Snark

    aa A Boojum Snark Toraipoddodezain Mazahabado

    Messages:
    4,767
    Positive Ratings:
    5,508
  5. What Is Schwa

    What Is Schwa L6: Sharp Member

    Messages:
    375
    Positive Ratings:
    220
    Sometime this happens to me when I have one of the following:

    func_brush on a displacement
    bad geometry (usually from a misplaced vertice)

    It isn't actually compiling an older version, it just finds the fatal area than skips the rest. You have it auto run the map, so it loads up the old map with the same file name.
     
    Last edited: Aug 6, 2009
  6. Vigilante212

    Vigilante212 L7: Fancy Member

    Messages:
    481
    Positive Ratings:
    33
    Another thing that causes this is having the map too close to the edge of the grid in hammer.
     
  7. Kazagin

    Kazagin L3: Member

    Messages:
    130
    Positive Ratings:
    9
    I ran my compiler log through Interlopers, and it gave me two errors.
    One was that I was running VVIS in fast mode and "zero area child patch".
    I'm trying to compile my map with everything set to normal, but it is taking a long time...
    And I did what it said for the "zero area child patch", and now I'm waiting for it to recompile...
    I'll post what happens when compiling is done later.

    RESULTS: Ok, it was the zero area child patch error.
    Unfortunately, I can't get it to run VVIS is normal mode.
    Why is that?
     
    Last edited: Aug 6, 2009