Immer wenn ich meine map laden will, kommt folgende Fehlermeldung und CS stürzt ab. Was kann ich da machen? Die Forensuche funz nich, sonst hätt ich da ja gesucht. :(

Naja, ich würde dir mal raten in Kompiler-Fehler Artikel rein zu schauen, das muss ich aber zurück nehmen, weil ich diesen Fehler auch hab, und zwar (jetzt wird s' merkwürdig) bei teils Orginalmaps von CS. D.h. kompilier hab ich die nicht, hab sie nur runtergeladen.
Hab ca. 300 stück, und 80% davon funzen nicht und bringen genau einen solchen Fehler.

Richman's Hazardous Course - Status: 100% !!!
www.richmans-maps.ch.vu - wieder online!

Hm, weis nich wer anders was man da machen kann? :((

So ich poste nochmal meine komplette Compilier-Log, vielleicht hilft das?

** Executing...
** Command: Change Directory
** Parameters: C:\Sierra\Counter-Strike\cstrike

** Executing...
** Command: Copy File
** Parameters: "C:\Sierra\Counter-Strike\cstrike\maps\1234.map" "C:\Sierra\Counter-Strike\cstrike\maps\1234.map"

** Executing...
** Command: C:\WINDOWS\Desktop\ZHLT24\hlcsg.exe
** Parameters: "C:\Sierra\Counter-Strike\cstrike\maps\1234"

hlcsg v2.4 BETA rel (Oct 15 2000)
Based on Valve's version, modified with permission.
Submit detailed bug reports to (zoner@gearboxsoftware.com)
----- BEGIN hlcsg -----
Command line: C:\WINDOWS\Desktop\ZHLT24\hlcsg.exe C:\Sierra\Counter-Strike\cstrike\maps\1234

-= 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 C:\Sierra\Counter-Strike\cstrike\maps\1234.map
CreateBrush:
10..20..30..40..50..60..70..80..90.. (7.91 seconds)
SetModelCenters:
20..50..70.. (0.00 seconds)
CSGBrush:
10..20..30..40..50..60..70..80..90.. (3.02 seconds)
Using WAD File: \sierra\counter-strike\cstrike\torntextures.wad
Warning: ::: Larger than expected texture (240172 bytes) Wad:wad[\sierra\counter-strike\cstrike\torntextures.wad] Texture[40:TK_STONEWALLHI]

Warning: ::: Larger than expected texture (306812 bytes) Wad:wad[\sierra\counter-strike\cstrike\torntextures.wad] Texture[79:TK_CLAYROOF]

Warning: ::: Larger than expected texture (272812 bytes) Wad:wad[\sierra\counter-strike\cstrike\torntextures.wad] Texture[107:{TK_PLANTLG]

Warning: ::: Larger than expected texture (327212 bytes) Wad:wad[\sierra\counter-strike\cstrike\torntextures.wad] Texture[109:{TK_PLANTSM]

Warning: ::: Larger than expected texture (235412 bytes) Wad:wad[\sierra\counter-strike\cstrike\torntextures.wad] Texture[161:TK_TORNMAP]

Using WAD File: \worldcraft\wad\mad_spain.wad
Using WAD File: \worldcraft\wad\mad_spain_addon.wad
Using WAD File: \worldcraft\wad\jos.wad
Using WAD File: \worldcraft\wad\torntextures.wad
Warning: ::: Larger than expected texture (240172 bytes) Wad:wad[\worldcraft\wad\torntextures.wad] Texture[348:TK_STONEWALLHI]

Warning: ::: Larger than expected texture (306812 bytes) Wad:wad[\worldcraft\wad\torntextures.wad] Texture[387:TK_CLAYROOF]

Warning: ::: Larger than expected texture (272812 bytes) Wad:wad[\worldcraft\wad\torntextures.wad] Texture[415:{TK_PLANTLG]

Warning: ::: Larger than expected texture (327212 bytes) Wad:wad[\worldcraft\wad\torntextures.wad] Texture[417:{TK_PLANTSM]

Warning: ::: Larger than expected texture (235412 bytes) Wad:wad[\worldcraft\wad\torntextures.wad] Texture[469:TK_TORNMAP]

Using WAD File: \sierra\counter-strike\valve\halflife.wad
Using WAD File: \sierra\counter-strike\cstrike\cached.wad
added 16 additional animating textures.
Texture usage is at 2.66 mb (of 4.00 mb MAX)
14.77 seconds elapsed

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

** Executing...
** Command: C:\WINDOWS\Desktop\ZHLT24\hlbsp.exe
** Parameters: "C:\Sierra\Counter-Strike\cstrike\maps\1234"

hlbsp v2.4 BETA rel (Oct 15 2000)
Based on Valve's version, modified with permission.
Submit detailed bug reports to (zoner@gearboxsoftware.com)
----- BEGIN hlbsp -----
Command line: C:\WINDOWS\Desktop\ZHLT24\hlbsp.exe C:\Sierra\Counter-Strike\cstrike\maps\1234

-= 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 ]

leakonly [ off ] [ off ]
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 infodecal @ ( 73,-2048,-115)
Fatal:
LEAK's in hull 0 will generate a pointfile which should be used to locate
the leak in the game. LEAK's in the other hulls can be more serious, as
if they are not fixed the world might be broken (i.e. it might be possible
to fall out of the world, to pass through walls, or just get stuck inside
a wall.

The entity listed in the error is the source of where the leak was detected.
In the case of it being in hull 0, this is the approximate location of the
start of the pointfile. For the other hulls, it should be used as the
approxmite area a collision hull problem could exist.

Leak pointfile generated

Warning: === LEAK in hull 1 ===
Entity info_player_deathmatch @ ( 704,-2304,-128)
Warning: === LEAK in hull 2 ===
Entity info_player_deathmatch @ ( 704,-2304,-128)
Warning: === LEAK in hull 3 ===
Entity env_sprite @ ( 238,-253,-296)
9.01 seconds elapsed

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

** Executing...
** Command: C:\WINDOWS\Desktop\ZHLT24\hlvis.exe
** Parameters: "C:\Sierra\Counter-Strike\cstrike\maps\1234"

hlvis v2.4 BETA rel (Oct 15 2000)
Based on Valve's version, modified with permission.
Submit detailed bug reports to (zoner@gearboxsoftware.com)
----- BEGIN hlvis -----
Command line: C:\WINDOWS\Desktop\ZHLT24\hlvis.exe C:\Sierra\Counter-Strike\cstrike\maps\1234
>> ERRORLOG C:\Sierra\Counter-Strike\cstrike\maps\1234.err detected, hlvis processing halted
>> If you have fixed the problem, you can delete the file and rerun hlvis
----- END hlvis -----

** Executing...
** Command: C:\WINDOWS\Desktop\ZHLT24\hlrad.exe
** Parameters: "C:\Sierra\Counter-Strike\cstrike\maps\1234"

hlrad v2.4 BETA rel (Oct 15 2000)
Based on Valve's version, modified with permission.
Submit detailed bug reports to (zoner@gearboxsoftware.com)
----- BEGIN hlrad -----
Command line: C:\WINDOWS\Desktop\ZHLT24\hlrad.exe C:\Sierra\Counter-Strike\cstrike\maps\1234
>> ERRORLOG C:\Sierra\Counter-Strike\cstrike\maps\1234.err detected, hlrad processing halted
>> If you have fixed the problem, you can delete the file and rerun hlrad
----- END hlrad -----

Zitat:

Deathwing postete
Warning: === LEAK in hull 0 ===
Entity infodecal @ ( 73,-2048,-115)
Fatal:
LEAK's in hull 0 will generate a pointfile which should be used to locate
the leak in the game. LEAK's in the other hulls can be more serious, as
if they are not fixed the world might be broken (i.e. it might be possible
to fall out of the world, to pass through walls, or just get stuck inside
a wall.

The entity listed in the error is the source of where the leak was detected.
In the case of it being in hull 0, this is the approximate location of the
start of the pointfile. For the other hulls, it should be used as the
approxmite area a collision hull problem could exist.

Leak pointfile generated

Warning: === LEAK in hull 1 ===
Entity info_player_deathmatch @ ( 704,-2304,-128)
Warning: === LEAK in hull 2 ===
Entity info_player_deathmatch @ ( 704,-2304,-128)
Warning: === LEAK in hull 3 ===
Entity env_sprite @ ( 238,-253,-296)
9.01 seconds elapsed
was mag das wohl heissen?

kA, erklär plz =)

also das Problem das ihr da habt badsurface ...../..
kommt immer wenn man eine Textur zu gross oder zu klein scalt.
ihr müsst nun ganz einfach die Textur suchen welche entweder unter 0.1 oder über 999 gescalt wurde.

Mfg
<<-[~{Twiggy}~]->>
"Mapping is Lifestyle"
[Beyond the Battlefield] Wir suchen noch: Modeler und Sound-Worker
[Vereinigte Staaten von Astor][Twiggy's Home]

Hm, gibts eine möglichkeit die genaue position der textur zu finden?
Meine map ist echt gross..

eigentlich nicht, außer du compilest auf -verbose, da wird alles hargenau erklärt, dann steht da die position und der name der textur!
Und stopf mal dein leak(=loch)!

Auf -verbose compilieren? wie soll das gehen? :(