Compile shortening?

Discussion in 'Mapping Questions & Discussion' started by HQDefault, Sep 14, 2014.

  1. HQDefault

    aa HQDefault ...what

    Messages:
    1,039
    Positive Ratings:
    400
    Umm... I'm currently trying to to compile my map, but recentley, the comile time has been taking longer and longer, to the point where I'm literally waiting 45 minutes for it to compile. If it works. 75% of the time, it just stops responding and won't compile. Any way to fix this?


    EDIT:
    ITS FIXED. CONVERSATION OVER!
     
    Last edited: Sep 15, 2014
  2. Dain

    Dain L3: Member

    Messages:
    106
    Positive Ratings:
    40
    Most long compiles are caused by poor VIS management.

    Make sure any small and/or complicated brushwork is a func_detail, so that they don't cut VIS.

    Use visclusters in large areas to tell VVIS that all the visleaves in that area can see each other.
     
  3. wareya

    wareya L7: Fancy Member

    Messages:
    493
    Positive Ratings:
    172
    use hint brushes at your common rooftop levels
     
  4. Sergis

    aa Sergis L666: ])oo]v[

    Messages:
    1,871
    Positive Ratings:
    1,131
    compile overnight
     
    • Thanks Thanks x 4
  5. Tumbolisu

    aa Tumbolisu  I ⌄ I 

    Messages:
    937
    Positive Ratings:
    905
  6. YM

    aa YM LVL100 YM

    Messages:
    7,099
    Positive Ratings:
    5,741
    Only compile what you need to. If you're just testing entities or layout, you don't need vis or lighting info, so just do VBSP and turn off VVIS and VRAD. If you're just doing a lighting test, you don't need proper visability info, just the basics that VVIS provides to VRAD, so do a fast VVIS (and if you don't need to do super fine tuning, just leave VRAD at fast too)

    45 isn't bad for a full on release compile. If you're PC is getting on a little that's fine. Mine takes about 50 for snowplow and my PC was a BEAST, but it was a beast five years ago. (Frozen's newer rig takes 20)

    You only know you have problems when VVIS specifically is taking most of the time, especially as if you're running VRAD for HDR every time, VRAD is running twice, and for local testing compiles you really don't need that.

    Also, for things like leak checking, just run VBSP, don't bother with VVIS or VRAD since the error is in VBSP.

    Look at your most recent compile log, scroll through and see what times VBSP,VVIS,VRAD and the second VRAD (if applicable) are taking. Then tell us. If VVIS is taking longer than VRAD, you might need to do some geometry optimisation. Otherwise I'd just say you've got an older PC and are compiling on full every time.

    ninja edit: Also, hammer will stop responding during a compile, that is normal. Just leave it be unless you see VBSP.exe, VBSP.exe or VRAD.exe at 0%cpu, then they've crashed.
     
    • Thanks Thanks x 2
  7. Crash

    aa Crash func_nerd

    Messages:
    3,148
    Positive Ratings:
    4,746
    When I reformatted my rig recently I got rid of my overclock. My compiles started taking about a third longer than they did before. Overclocking again from 3.3 GHz to 4.2 dropped it back down to normal. Glassworks full compile takes me about 25 minutes now, for reference.

    Not sure if it's an option for you, but thought I'd mention.
     
    Last edited: Sep 15, 2014
  8. DonutVikingChap

    DonutVikingChap L5: Dapper Member

    Messages:
    227
    Positive Ratings:
    142
    And I'm just sitting here doing final compiles of ctf_infiltration_b13 at 3 minutes flat B)
     
  9. henke37

    aa henke37

    Messages:
    1,876
    Positive Ratings:
    440
    If VVIS takes more than a few seconds then you have a problem. Load the portal file and check for silliness.
     
    • Thanks Thanks x 1
  10. YM

    aa YM LVL100 YM

    Messages:
    7,099
    Positive Ratings:
    5,741
    Very much wrong. Small, incredibly simple maps might take a few seconds, but anything more complex or larger is gunna take time. You certainly can't make that kind of statement.
     
    • Thanks Thanks x 1
  11. Lampenpam

    aa Lampenpam

    Messages:
    1,019
    Positive Ratings:
    337
    From my experience it's often more a matter of the complexity of solid brushes and how open the map is.

    A giant map can compile VVIS in 2 seconds if its not too open (usually all indoor) Large open areas will take their time, especially if you can't use func_viscluster a lot because of complex brush work.
     
  12. Fr0Z3nR

    aa Fr0Z3nR Creator of blackholes & memes. Destroyer of forums

    Messages:
    6,391
    Positive Ratings:
    4,906

    Should note, my computers 5 years old too ;)
     
  13. Dain

    Dain L3: Member

    Messages:
    106
    Positive Ratings:
    40
    Datapoint: I compiled the tc_hydro VMF provided with the SDK in 5 minutes 5 seconds on normal settings. My computer is nothing special.

    (the VRAD part of a HDR compile with -final took over half an hour though :s)
     
  14. fubarFX

    aa fubarFX The "raw" in "nodraw"

    Messages:
    1,608
    Positive Ratings:
    1,698
  15. wareya

    wareya L7: Fancy Member

    Messages:
    493
    Positive Ratings:
    172
    VVIS for my 5CP maps only takes a few minutes, even the ones that don't seal huge areas from eachother with areaportals and roof skyboxing. And... I have a TERRIBLE CPU for compiling maps. We're talking third generation of 64-bit processors here, seven or six years old.
     
  16. RaVaGe

    aa RaVaGe

    Messages:
    726
    Positive Ratings:
    1,049
    Actually it depends a lot of your hint brushes and how silly you are when you map, with no hints in my maps, my vvis always takes less than 10 seconds, and most of the time it takes 0 seconds when i'm in the early stage of the development. (blorav takes 0 seconds actually).

    The processor of course has an important part into the time it takes to compile a map, but often the way you make your map is also pretty important, you should cut your map as much as possible into small boxes, and use wisely your hint brushes.

    But remember that the in-game optimisation is always way more important than the optimisation of the compilation time.

    So imo, when your map is in it's first blockout stage, where you don't need to use the hint brushes (I use the areaportals most of the time in my blockout), vvis should always takes less than approx 1 min, depends of you processor of course, but if your processor is a beast and that it takes you already more than one minute for vvis to compile in a blockout stage, then you have an issue.

    The use of func_detail is pretty important if you want to shorten your compile time, use them everywhere except where you have to block the visibility (stairs, roofs, windows, doors) have to be func_detailled.

    But use them wisely because you can ran out of them pretty easily, and there's also the T-Junction issue wich is kinda annoying to deal with.

    EDIT: Also for a fully optimised map, it depends a lot of the size and the geometry, and there's no defined time for that, ofc.
     
    Last edited: Sep 15, 2014
  17. Kill_the_Bug

    Kill_the_Bug L14: Epic Member

    Messages:
    1,461
    Positive Ratings:
    237
    Also use VBCT instead of compiling in Hammer.

    Hamer compliles totally lock up your machine - VBCT will compile in the background and still allow you to use you machine.