Optimization help

Discussion in 'Mapping Questions & Discussion' started by That's the plan, Apr 15, 2019.

  1. That's the plan

    That's the plan L3: Member

    Messages:
    147
    Positive Ratings:
    30
    I can't test my map because it never finished compiling. It always gets stuck on the "portal flow" section of the compile, and then just crashes hammer. I tried to open up the portal-file for the map to optimize it but that won't work either. I can't even get a copy of the compile log because it just crashes hammer every time. Help?
     
  2. Johnny_RussianBoy

    Johnny_RussianBoy L2: Junior Member

    Messages:
    96
    Positive Ratings:
    28
    Try to use the Compile Pal, if it continues to crash, then your problem is in the portals themselves and you should fix this problem on your map in hammer
     
  3. That's the plan

    That's the plan L3: Member

    Messages:
    147
    Positive Ratings:
    30
    Never used compile pal before. I tried compiling the map in compile pal but it didn't run after.
     
  4. Da Spud Lord

    aa Da Spud Lord L0: Crappy Member

    Messages:
    1,028
    Positive Ratings:
    698
    You should be able to fetch your compile log from the <mapname>.log file within the same folder as your VMF. I think it puts the compile log there even when it crashes, although I could be wrong.

    Also, check your Alt-P problem checker.

    Also also, are you using func_detail appropriately?
     
  5. worMatty

    aa worMatty Repacking Evangelist

    Messages:
    1,080
    Positive Ratings:
    846
    Visibility optimisation is a step in your design and finishing process which requires knowledge of how VVIS calculates visibility. I suggest you take some time to read and digest some guides.

    In brief, though: The portal flow step commonly takes too long because there are a lot of visleaves (the shapes which are made up of individual portals, or 'sides') which can see each other. VVIS needs to spend time on each corner of each portal to see what other corners of other portals it can see. The more portals that can see each other, the longer it takes. That counts for both small to medium areas and very large areas. The program which creates the portals in the first place is actually VBSP. If you perform a VBSP-only compile (no VVIS or lighting), you can load the map's portal file using the option in Hammer's menu, which shows the portals as blue shapes. Look for places where there are a high number of portals in a small space and try to reduce them. Then look at your larger, open spaces and have a think about which portals can see each other. You may need to partition some areas so that the portals can't see each other as much.

    VVIS should only take five minutes at most. See what you can find out and post your progress.