Das is so ein Problem :
hlcsg v2.5.3 rel (May 2 2001)
Based on Valve's version, modified with permission.
Submit detailed bug reports to (zoner@gearboxsoftware.com)
----- BEGIN hlcsg -----
Command line: E:\CS-Tools\Worldcraft\ZHLT253\hlcsg.exe E:\Sierra\HalfLife2\cstrike\maps\de_dust2k

-= 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 ]
onlyents [ off ] [ off ]
wadtextures [ on ] [ on ]
skyclip [ on ] [ on ]
hullfile [ None ] [ None ]
min surface area [ 0.500 ] [ 0.500 ]
brush union threshold [ 0.000 ] [ 0.000 ]

Wadinclude list :
[zhlt.wad]

entering E:\Sierra\HalfLife2\cstrike\maps\de_dust2k.map
CreateBrush:
(0.22 seconds)
SetModelCenters:
(0.00 seconds)
CSGBrush:
(0.94 seconds)
Using WAD File: \sierra\halflife\valve\halflife.wad
Using WAD File: \sierra\halflife\valve\decals.wad
Using WAD File: \sierra\halflife\valve\liquids.wad
Using WAD File: \sierra\halflife\cstrike\cstrike.wad
Using WAD File: \sierra\halflife\tfc\tfc2.wad
Using WAD File: \sierra\halflife\tfc\tfc.wad
Texture usage is at 0.09 mb (of 4.00 mb MAX)
1.26 seconds elapsed

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

hlbsp v2.5.3 rel (May 2 2001)
Based on Valve's version, modified with permission.
Submit detailed bug reports to (zoner@gearboxsoftware.com)
----- BEGIN hlbsp -----
Command line: E:\CS-Tools\Worldcraft\ZHLT253\hlbsp.exe E:\Sierra\HalfLife2\cstrike\maps\de_dust2k

-= 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 ]
notjunc [ off ] [ off ]
subdivide size [ 240 ] [ 240 ] (Min 64) (Max 240)
max node size [ 1024 ] [ 1024 ] (Min 64) (Max 4096)

Warning: === LEAK in hull 0 ===
Entity info_player_deathmatch @ (-128,-2624, 256)
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

Warning: === LEAK in hull 1 ===
Entity info_player_deathmatch @ (-128,-2624, 256)
Warning: === LEAK in hull 2 ===
Entity info_player_deathmatch @ (-128,-2624, 256)
Warning: === LEAK in hull 3 ===
Entity info_player_deathmatch @ (-128,-2624, 256)
4.67 seconds elapsed

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

hlvis v2.5.3 rel (May 2 2001)
Based on Valve's version, modified with permission.
Submit detailed bug reports to (zoner@gearboxsoftware.com)
----- BEGIN hlvis -----
Command line: E:\CS-Tools\Worldcraft\ZHLT253\hlvis.exe E:\Sierra\HalfLife2\cstrike\maps\de_dust2k
>> There was a problem compiling the map.
>> Check the file E:\Sierra\HalfLife2\cstrike\maps\de_dust2k.log for the cause.

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

hlrad v2.5.3 rel (May 2 2001)
Based on Valve's version, modified with permission.
Submit detailed bug reports to (zoner@gearboxsoftware.com)
----- BEGIN hlrad -----
Command line: E:\CS-Tools\Worldcraft\ZHLT253\hlrad.exe E:\Sierra\HalfLife2\cstrike\maps\de_dust2k
>> There was a problem compiling the map.
>> Check the file E:\Sierra\HalfLife2\cstrike\maps\de_dust2k.log for the cause.

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

Bidde Bidde helft mir !!!

Wo kämen wir denn hin, wenn jeder sagen würde, wo kämen wir denn hin, und niemand ginge, um zu sehen wohin wir kämen wenn wir gingen?!

Zitat:

Halok postete

Warning: === LEAK in hull 0 ===
Entity info_player_deathmatch @ (-128,-2624, 256)
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

Warning: === LEAK in hull 1 ===
Entity info_player_deathmatch @ (-128,-2624, 256)
Warning: === LEAK in hull 2 ===
Entity info_player_deathmatch @ (-128,-2624, 256)
Warning: === LEAK in hull 3 ===
Entity info_player_deathmatch @ (-128,-2624, 256)

Also, da ich jetzt keinen Bock hab das zu erklären, ließ dr malde Englische Fehlemeldung durch und dann guck mal nen par Threads drunter! Da stejt irgendwo genau das selbe mit Lösung!!!
Nur ein Tip: Geh in Hal-Life und gib in deinem Level "pointfile" (ohne die Anührungszeichen!) ein! Dann kommt sonen Strich der zeigt dir auf das Leak!

Danke für deine Hilfe !
Ich hab das aber vorher schon hinbekommen da mein Freund mir geholfen hat !
Aber das mit dem pointfile is voll scheisse das zeigt überall hin aber nich zum leak !

Wo kämen wir denn hin, wenn jeder sagen würde, wo kämen wir denn hin, und niemand ginge, um zu sehen wohin wir kämen wenn wir gingen?!

Doch, das Pointfile "zeigt" dorthin !!!

Du musst (starte HL mit Parameter "-particles n" n laut diversen readmes auf 20000, aber bei mir hab ich das auf 512000 stehen und es funzt) einfach vom Entinity aus den Linien folgen - irgendwo geht es ins "äussere" der Map - voila , dort ist das Leak !!!
Einfacher Trick : Alle Linien ausserhalb sind unwichtig, da sie noch ne bisserl rumbouncen, woran auch immer. Alle Stellen, wo eine Linie hin, und wieder zurückführt, kannste auch vergessen, interessant ist, wenn du eine Linie irgendwohingehen siehst, und keine kommt daher zurück. Meist findest du dort den Fehler.

p.s.: Ich hatte schon nen Leak direkt neben dem info_Player_start - und trotzdem fing der bei nem Light am anderen Ende der Map an.