stupid leaks

Discussion in 'Mapping Questions & Discussion' started by suzzanuzza, Jun 7, 2009.

  1. suzzanuzza

    suzzanuzza L1: Registered

    Messages:
    44
    Positive Ratings:
    1
    im furious right now with this stupid map editor. it gives me nothing but trouble! ive been compiling my map and using "loadpointfile" to find a leak that the compile process window says i have. so anyway i load the file and the red line starts at a prop_static, changes direction a few times, then ends up going straight through a solid wall into the void. i first thought this some some stupid mistake so i recompiled, but this time the leak line came from a point_spotlight, and eventually made its way through another solid wall. it has changed position a few times but right now it is coming from a bench and going through a thick wall and zig zaging all over the place once it reaches the void.
     
  2. DJive

    aa DJive Cake or Death?

    Messages:
    1,466
    Positive Ratings:
    736
    make sure your "solid wall" is not a func_detail.


    when all else fails and possibly the easiest option.. delete the wall and remake.

    http://developer.valvesoftware.com/wiki/Leaks

    Also a LOT on the topic in the forums, check search function.
     
  3. Sgt Frag

    Sgt Frag L14: Epic Member

    Messages:
    1,443
    Positive Ratings:
    294
    Does the compile error say leak?

    Could be a displacement tied to a func_detail. Do you filter all your details, props and displacements to look for leak. Maybe that solid wall is a func_detail.
     
  4. Mar

    Mar Banned

    Messages:
    607
    Positive Ratings:
    63
    First select the thick wall the line is going through and hit "Alt + enter" to bring up it's properties. Chances are it says that the wall is a func_detail.

    Func_ Details are compiled as entities and they don't block leaks. In other words func_ details don't stop that little red line.

    To make your brush part of the world geometry (which means it will stop the red line) you must exit out the properties pop-up box, select the thick wall and hit "Crtl + Shit + W". This will make your wall stop the red line and you the leak should go away.

    Hope this helps!

    EDIT: Cheese nips, I got ninja'd twice.
     
  5. suzzanuzza

    suzzanuzza L1: Registered

    Messages:
    44
    Positive Ratings:
    1
    none of my walls are func_detail, they are just plain old solid blocks. and i tried deleting the wall and making a new one, but then it just creates another nonexsistent leak on another wall. i did, however, try building a skybox and it fixed the problem, but since my map is completely indoors, the skybox will do nothing but slow down the map
     
  6. NovaSilisko

    aa NovaSilisko L42: Life, the Universe and Everything

    Messages:
    502
    Positive Ratings:
    128
    What texture is the wall that's leaking?
     
  7. suzzanuzza

    suzzanuzza L1: Registered

    Messages:
    44
    Positive Ratings:
    1
    all different textures. and none of them are glass or model textures
     
  8. Pianodan

    Pianodan L3: Member

    Messages:
    108
    Positive Ratings:
    16
    If you want to post a link to your .vmt someone might be willing to look at it.
     
  9. eerieone

    aa eerieone

    Messages:
    1,009
    Positive Ratings:
    569
    use the cordon tool to narrow down your search
    chances are that you have several leaks and the pointfile output gets confused
     
  10. suzzanuzza

    suzzanuzza L1: Registered

    Messages:
    44
    Positive Ratings:
    1
    it just magically stopped happening, and i didnt even do anything. thats valve for ya!
     
  11. Vigilante212

    Vigilante212 L7: Fancy Member

    Messages:
    481
    Positive Ratings:
    33
    You really need to stop blaming valve for your mapping errors.
     
  12. suzzanuzza

    suzzanuzza L1: Registered

    Messages:
    44
    Positive Ratings:
    1
    i said it started working for no reason and i didnt change anything. how could that be my fault if i didnt do anything. it was obviously a glitch, which makes it valve's fault