Ich habe in den FAQ´s nachegesehn und habe ein passendes gefunden. Doch ich glaube das es veraltet ist da es noch für Worldcraft beschrieben wurde und eigentlich die Erklärung für die notwendigen Einstellungen von ZHLT nicht übereinstimmen. Ich meine also ich kann die erklärten Dinge in meinem Valve Hammer Editor 3.5 nicht anwenden. Wenn ich alles so lasse wie es ist im Expert Modus passiert das Problem das es keine Schattenberechnung gibt und die gesamte Map super Hell ist....

Kann mir also bitte jemand es erklären oder per Mail schreiben oder auf einen passendern der unzähligen anderen Threads zu diesem Thema verweisen den ich leider dann nicht finden konnte da es schon so viel davon gibt.

Forenregeln beachten! wenn du den FAQ gefunden hast, dann kannst da ja auch mal nachschauen warum deine map super hell ist... und der Hammereditor ist im grunde genau das gleiche wie Worldcraft. die einstellungen die bei worldcraft nicht gibt, aber im VHE sind für einen anfänger egal

Mir ist durchaus klar warum die map so hell ist aber bei dem normalen compilen ist das ja nicht der fall. ich will zhlt ja auch nur verwenden um mehr texturen nutzen zu können

poste doch einfach mal dein compile log, dann können wir dir sagen woran es liegt.

http://choerbaert.org
Ein Gespenst geht um im Netz - das Gespenst des Open Source
csndr

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

** Executing...
** Command: C:\zhlt\hlcsg.exe
** Parameters: "c:\programme\valve hammer editor\maps\de_bpm_beta3"

hlcsg v2.5.3 rel Custom Build 1.7p3 (Feb 21 2003)
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: C:\zhlt\hlcsg.exe "c:\programme\valve hammer editor\maps\de_bpm_beta3"
Entering c:\programme\valve hammer editor\maps\de_bpm_beta3.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 ]
clip hull type [ legacy ] [ legacy ]
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 ]

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

0 brushes (totalling 0 sides) discarded from clipping hulls
CreateBrush:
10%...20%...30%...40%...50%...60%...70%...80%...90%... (0.23 seconds)
SetModelCenters:
20%...40%...60%...80%... (0.00 seconds)
CSGBrush:
10%...20%...30%...40%...50%...60%...70%...80%...90%... (1.02 seconds)

Using Wadfile: \counter-strike\cstrike\basics.wad
- Contains 4 used textures, 10.81 percent of map (14 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part1.wad
- Contains 4 used textures, 10.81 percent of map (320 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part2.wad
- Contains 0 used textures, 0.00 percent of map (139 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part3.wad
- Contains 2 used textures, 5.41 percent of map (103 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part4.wad
- Contains 0 used textures, 0.00 percent of map (92 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part5.wad
- Contains 0 used textures, 0.00 percent of map (66 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part6.wad
- Contains 2 used textures, 5.41 percent of map (106 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part7.wad
- Contains 0 used textures, 0.00 percent of map (79 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part8.wad
- Contains 7 used textures, 18.92 percent of map (238 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part9.wad
- Contains 6 used textures, 16.22 percent of map (290 textures in wad)
Using Wadfile: \counter-strike\cstrike\tdk_wad_part10.wad
- Warning: Larger than expected texture (348972 bytes): 'TDK10_BUILD08C'
- Warning: Larger than expected texture (348972 bytes): 'TDK10_BUILD09B'
- Warning: Larger than expected texture (348972 bytes): 'TDK10_BUILD19B'
- Warning: Larger than expected texture (348972 bytes): 'TDK10_BUILD23B'
- Warning: Larger than expected texture (348972 bytes): 'TDK10_BUILD24B'
- Warning: Larger than expected texture (261932 bytes): 'TDK10_BUILD25B'
- Warning: Larger than expected texture (348972 bytes): 'TDK10_BUILD30B'
- Warning: Larger than expected texture (348972 bytes): 'TDK10_FLOOR04B'
- Warning: Larger than expected texture (348972 bytes): '{TDK10_FENCE02B'
- Warning: Larger than expected texture (348972 bytes): '{TDK10_TREE01A'
- Warning: Larger than expected texture (348972 bytes): '{TDK10_TREE04B'
- Contains 7 used textures, 18.92 percent of map (382 textures in wad)
Using Wadfile: \counter-strike\cstrike\xentextures1.wad
- Contains 5 used textures, 13.51 percent of map (168 textures in wad)

Warning: More than 8 wadfiles are in use. (12)
This may be harmless, and if no strange side effects are occurring, then
it can safely be ignored. However, if your map starts exhibiting strange
or obscure errors, consider this as suspect.

Texture usage is at 1.99 mb (of 4.00 mb MAX)
1.36 seconds elapsed

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

** Executing...
** Command: C:\zhlt\hlbsp.exe
** Parameters: "c:\programme\valve hammer editor\maps\de_bpm_beta3"

hlbsp v2.5.3 rel Custom Build 1.7p (Jan 25 2003)
Zoner's Half-Life Compilation Tools -- Custom Build
Modified to bump up MAX_MAP_PLANES by Karl 'XP-Cagey' Patrick
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: C:\zhlt\hlbsp.exe "c:\programme\valve hammer editor\maps\de_bpm_beta3"

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 @ ( 160,-648,-404)
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

2.42 seconds elapsed

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

** Executing...
** Command: C:\zhlt\hlvis.exe
** Parameters: "c:\programme\valve hammer editor\maps\de_bpm_beta3"

hlvis v2.5.3 rel Custom Build 1.7p (Jan 25 2003)
Zoner's Half-Life Compilation Tools -- Custom Build
Modified to bump up MAX_MAP_PLANES by Karl 'XP-Cagey' Patrick
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: C:\zhlt\hlvis.exe "c:\programme\valve hammer editor\maps\de_bpm_beta3"
>> There was a problem compiling the map.
>> Check the file c:\programme\valve hammer editor\maps\de_bpm_beta3.log for the cause.

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

** Executing...
** Command: C:\zhlt\hlrad.exe
** Parameters: "c:\programme\valve hammer editor\maps\de_bpm_beta3"

hlrad v2.5.3 rel Custom Build 1.7p (Jan 25 2003)
Zoner's Half-Life Compilation Tools -- Custom Build
Modified to bump up MAX_MAP_PLANES by Karl 'XP-Cagey' Patrick
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: C:\zhlt\hlrad.exe "c:\programme\valve hammer editor\maps\de_bpm_beta3"
>> There was a problem compiling the map.
>> Check the file c:\programme\valve hammer editor\maps\de_bpm_beta3.log for the cause.

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

** Executing...
** Command: Copy File
** Parameters: "c:\programme\valve hammer editor\maps\de_bpm_beta3.bsp" "C:\Counter-Strike\cstrike\maps\de_bpm_beta3.bsp"

** Executing...
** Command: Copy File
** Parameters: "c:\programme\valve hammer editor\maps\de_bpm_beta3.pts" "C:\Counter-Strike\cstrike\maps\de_bpm_beta3.pts"

** Executing...
** Command: C:\COUNTE~1\cstrike.exe
** Parameters: +map "de_bpm_beta3" -dev -console

Zitat:

Warning: === LEAK in hull 0 ===
Entity info_player_start @ ( 160,-648,-404)
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

edit:
auch hast du 12wads benutzt, 8soltlen es nur sein. das kann auch gelegentlich zu fehlern führen, also nicht benutzte wads rausschmeisen

Danke sehr für die Info aber wieso passiert mir dieser Fehler nicht wenn ich die normale Compile verwende? und da steht doch auch LEAK in hull 0

Ich habe jetzt die unwichtigen Wads entfernt und sogar zur Sicherheit clipping wände gemacht aber das funzt einfach nicht! Immernoch hab ich diesen Fehler und ich weis einfach nicht wieso.

Ein Leak ist ein Loch da liegt nicht an den wad´s.

Suche das Loch und stopfe es

such mal in den tutorials nach leaks, da findest du ne methode wie du ein LEAK findest.

Bei den alten compilern war es so, dass diese trotz Leak die Map mit Licht bzw. Schattewurf berechnen konnten. Die neuen compiler machen das nicht, sondern brechen ab, wenn ein Leak gefunden wurde.

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

Yepp, allerdings waren die r_speeds natürlich im Keller da die Sichtbarkeitsberechnung nicht ordnungsgemäß durchlaufen konnte. Die Lichtberechnung ist sicherlich auch nicht so der Hammer ohne vis.

http://choerbaert.org
Ein Gespenst geht um im Netz - das Gespenst des Open Source
csndr