Hammer is getting annoying

Hammer is getting annoying

Hammer Mapping — Page [1]
fedex _

2009 Mar 23 • 906
13 ₧
hlcsg v2.5.3 rel Custom Build 1.7 (Dec 9 2002)
Zoner's Half-Life Compilation Tools -- Custom Build
Based on code modifications by Sean 'Zoner' Cavanaugh
Based on Valve's version, modified with permission.
Submit detailed bug reports to (merlinis@bigpond.net.au)
----- BEGIN hlcsg -----
Command line: hlcsg -nowadtextures stone_bhop
Entering stone_bhop.map

Current hlcsg Settings
Name | Setting | Default
---------------------|-----------|-------------------------
threads [ 1 ] [ Varies ]
verbose [ off ] [ off ]
log [ on ] [ on ]
developer [ 0 ] [ 0 ]
chart [ off ] [ off ]
estimate [ off ] [ off ]
max texture memory [ 4194304 ] [ 4194304 ]
priority [ Normal ] [ Normal ]

noclip [ off ] [ off ]
null texture stripping[ on ] [ on ]
clipnode economy mode [ on ] [ on ]
onlyents [ off ] [ off ]
wadtextures [ off ] [ on ]
skyclip [ on ] [ on ]
hullfile [ None ] [ None ]
min surface area [ 0.500 ] [ 0.500 ]
brush union threshold [ 0.000 ] [ 0.000 ]

Using mapfile wad configuration
Wadinclude list :
[zhlt.wad]

39 brushes (totalling 238 sides) discarded from clipping hulls
CreateBrush:
(0.03 seconds)
SetModelCenters:
(0.02 seconds)
CSGBrush:
(0.09 seconds)

Using Wadfile: \documents and settings\administrator\desktop\desktop\brandons maps\maps and wads\cswad.wad
- Warning: Larger than expected texture (348972 bytes): 'KREEDZMOD'
- Warning: Larger than expected texture (348972 bytes): 'PAYPALDONATE'
- Warning: Larger than expected texture (348972 bytes): 'MARIOWEST1'
- Warning: Larger than expected texture (348972 bytes): 'MARIOWEST2'
- Warning: Larger than expected texture (348972 bytes): 'KREEDZMOD'
- Warning: Larger than expected texture (348972 bytes): 'PAYPALDONATE'
- Warning: Larger than expected texture (348972 bytes): 'MARIOWEST1'
- Warning: Larger than expected texture (348972 bytes): 'MARIOWEST2'
- Contains 26 used textures, 96.30 percent of map (1366 textures in wad)

added 1 additional animating textures.
Warning: ::FindTexture() texture LAB1_DOOR1C not found!
Warning: ::LoadLump() texture LAB1_DOOR1C not found!
Texture usage is at 0.69 mb (of 4.00 mb MAX)
0.27 seconds elapsed

----- END hlcsg -----



hlbsp v2.5.3 rel Custom Build 1.7 (Dec 9 2002)
Zoner's Half-Life Compilation Tools -- Custom Build
Based on code modifications by Sean 'Zoner' Cavanaugh
Based on Valve's version, modified with permission.
Submit detailed bug reports to (merlinis@bigpond.net.au)
----- BEGIN hlbsp -----
Command line: hlbsp stone_bhop

Current hlbsp Settings
Name | Setting | Default
-------------------|-----------|-------------------------
threads [ 1 ] [ Varies ]
verbose [ off ] [ off ]
log [ on ] [ on ]
developer [ 0 ] [ 0 ]
chart [ off ] [ off ]
estimate [ off ] [ off ]
max texture memory [ 4194304 ] [ 4194304 ]
priority [ Normal ] [ Normal ]

noclip [ off ] [ off ]
nofill [ off ] [ off ]
null tex. stripping [ on ] [ on ]
notjunc [ off ] [ off ]
subdivide size [ 240 ] [ 240 ] (Min 64) (Max 512)
max node size [ 1024 ] [ 1024 ] (Min 64) (Max 4096)


Warning: === LEAK in hull 0 ===
Entity info_player_start @ (-1377,-1887,-120)
Error:
A LEAK is a hole in the map, where the inside of it is exposed to the
(unwanted) outside region. The entity listed in the error is just a helpful
indication of where the beginning of the leak pointfile starts, so the
beginning of the line can be quickly found and traced to until reaching the
outside. Unless this entity is accidentally on the outside of the map, it
probably should not be deleted. Some complex rotating objects entities need
their origins outside the map. To deal with these, just enclose the origin
brush with a solid world brush

Leak pointfile generated

0.66 seconds elapsed

----- END hlbsp -----



hlvis v2.5.3 rel Custom Build 1.7 (Dec 9 2002)
Zoner's Half-Life Compilation Tools -- Custom Build
Based on code modifications by Sean 'Zoner' Cavanaugh
Based on Valve's version, modified with permission.
Submit detailed bug reports to (merlinis@bigpond.net.au)
----- BEGIN hlvis -----
Command line: hlvis stone_bhop
>> There was a problem compiling the map.
>> Check the file stone_bhop.log for the cause.

----- END hlvis -----



hlrad v2.5.3 rel Custom Build 1.7 (Dec 9 2002)
Zoner's Half-Life Compilation Tools -- Custom Build
Based on code modifications by Sean 'Zoner' Cavanaugh
Based on Valve's version, modified with permission.
Submit detailed bug reports to (merlinis@bigpond.net.au)
----- BEGIN hlrad -----
Command line: hlrad stone_bhop
>> There was a problem compiling the map.
>> Check the file stone_bhop.log for the cause.

----- END hlrad -----

Only when i make a skybox this leak always appears

melloyellow582 said:
I post sometimes, to make a point.
 
 
2009 Apr 7 at 12:47 PDT
Mate de Vita
Kelli

2008 Oct 4 • 2453
159 ₧
Down Rodeo said:
Q: How do I plug a leak?

First of all, make sure you did not create any entities outside your map. An entity outside your map is just like a leak, if not worse.

If you can not find any entities outside your map:
Load the pointfile generated by the compile tools by selecting the "load pointfile" option in the Hammer menus. Then follow the red line in the viewport to the hole. DON'T delete entities quoted as causing the leak, as they are just mentioned as a reference point. DO use the grid to help avoid leaks in the first instance.
...and that's the bottom line because Mate de Vita said so.
 
 
2009 Apr 7 at 13:01 PDT
fedex _

2009 Mar 23 • 906
13 ₧
Mate de Vita said:
Down Rodeo said:
Q: How do I plug a leak?

First of all, make sure you did not create any entities outside your map. An entity outside your map is just like a leak, if not worse.

If you can not find any entities outside your map:
Load the pointfile generated by the compile tools by selecting the "load pointfile" option in the Hammer menus. Then follow the red line in the viewport to the hole. DON'T delete entities quoted as causing the leak, as they are just mentioned as a reference point. DO use the grid to help avoid leaks in the first instance.




ok but the red line takes up my whole map.........
melloyellow582 said:
I post sometimes, to make a point.
 
 
2009 Apr 7 at 13:10 PDT
Mate de Vita
Kelli

2008 Oct 4 • 2453
159 ₧
Start at the entity given in the entity report (info_player_start) and follow the line. The place where it leaves the map is where the leak is. Also make sure you're loading the .lin file and not the .pts file.
...and that's the bottom line because Mate de Vita said so.
 
 
2009 Apr 7 at 13:13 PDT
Page [1]