[problema-ayuda] falta error full

[Miniscula]

hola ayudenme porfavor !

 

llevo como 4 meses creando este mapa , y de repente lo fui a compilar por rutina para fijarme de que todo andara bien y puss no puedo quitar el siguiente error ! fuckkkkkkkkkkkkkkkkkkkkkkkkk

 

 

hlcsg v3.4 Final (Feb 25 2006)

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 (amckern@yahoo.com)

----- BEGIN hlcsg -----

Command line: C:\VALVEH~1\tools\ZHLT\hlcsg.exe "C:\Program Files\valve\cstrike\maps\blo223322222"

Entering C:\Program Files\valve\cstrike\maps\blo223322222.map

 

Current hlcsg Settings

Name | Setting | Default

---------------------|-----------|-------------------------

threads [ 2 ] [ Varies ]

verbose [ off ] [ off ]

log [ on ] [ on ]

developer [ 0 ] [ 0 ]

chart [ off ] [ off ]

estimate [ off ] [ off ]

max texture memory [ 4194304 ] [ 4194304 ]

max lighting memory [ 6291456 ] [ 6291456 ]

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 ]

nullfile [ 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:

(0.08 seconds)

SetModelCenters:

(0.00 seconds)

CSGBrush:

(0.38 seconds)

 

Using Wadfile: \program files\valve\cstrike\bloques.wad

- Warning: Larger than expected texture (327212 bytes): '{PLANTAVOLADORA'

- Contains 8 used textures, 80.00 percent of map (67 textures in wad)

Using Wadfile: \program files\valve\valve\halflife.wad

- Contains 2 used textures, 20.00 percent of map (3116 textures in wad)

 

Texture usage is at 0.58 mb (of 4.00 mb MAX)

0.61 seconds elapsed

 

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

 

 

 

hlbsp v3.4 Final (Feb 25 2006)

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 (amckern@yahoo.com)

----- BEGIN hlbsp -----

Command line: C:\VALVEH~1\tools\ZHLT\hlbsp.exe "C:\Program Files\valve\cstrike\maps\blo223322222"

 

Current hlbsp Settings

Name | Setting | Default

-------------------|-----------|-------------------------

threads [ 2 ] [ 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 ]

noopt [ 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 8192)

 

 

SolidBSP [hull 0] 500...1000...1500...1899 (0.15 seconds)

Warning: === LEAK in hull 0 ===

Entity info_player_start @ (-131,-467,-169)

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

 

SolidBSP [hull 1] 500...940 (0.04 seconds)

Warning: === LEAK in hull 1 ===

Entity info_player_start @ (-131,-467,-169)

SolidBSP [hull 2] 500...931 (0.04 seconds)

Warning: === LEAK in hull 2 ===

Entity info_player_start @ (-131,-467,-169)

SolidBSP [hull 3] 500...1000...1177 (0.06 seconds)

Warning: === LEAK in hull 3 ===

Entity info_player_start @ (-131,-467,-169)

0.77 seconds elapsed

 

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

 

 

 

hlrad v3.4 Final (Feb 25 2006)

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 (amckern@yahoo.com)

----- BEGIN hlrad -----

Command line: C:\VALVEH~1\tools\ZHLT\hlrad.exe -extra "C:\Program Files\valve\cstrike\maps\blo223322222"

>> There was a problem compiling the map.

>> Check the file C:\Program Files\valve\cstrike\maps\blo223322222.log for the cause.

 

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

 

 

 

 

 

 

 

Cuando abro el mapa en el counter me sale esto "allocblock:full"

Editado agosto 29, 2011 a las 00:31 por Incrusser

[Restiur11709396421]

Ya de por si tenes leak en el mapa , quizas pueda ser eso que te tire ese error (?

 

Es solo mi deduccion , nunca me paso esto ami :(howard):

[S34Qu4K3]

entonces tu pc no sirve para compilar mapas :(O.O):

 

allocblock:full

 

A tough one to figure out, vague error that usually shows up when you start the game or during compile, or even when WC/Hammer starts up - you have gone over the memory limit somewhere for some reason. It can be too little RAM (128M is about minimum), a leaf saw into leaf error, too long pathnames, too many textures, too big a level, too big or too many model/sprites, too big a wav sound file - or it could be that old "too many wads" mistake, a huge "noob" brush around the map to prevent leaks, too many SKY faces on hidden brush faces in the level - or even something else. Example: In early versions of NS, the 3D area info location entities were a major cause.

If it happens during compile, do not use WC/Hammer to "run" the map, but use a front end or batch file to compile with. You could also get more RAM.

(The following may still be handy, however be aware that Software mode allocates memory dynamicly, so it may automaticly seem to "fix" any error. Therefore the following info MAY lead you into a dead end:

Some brush-based entities have rendering properties that, when they interact in OpenGL/D3D video cards, they crash. Switch Half-Life to Software mode first, then load the map. If it loads you now know it is something that is handle different in software, then for Opengl/d3d check water, glows, additive, sprites, transparencies (illusionaries, windows, ect.), env_beams and so on.)

 

If it happens in opening a level in WC, it may be you have an animating model showing in one view. You must switch to single view instead of multiple, and try different ones until you get past it.

 

Por una de esas causas es tu error, ademas tienes Leak como ya te dijeron

http://www.mundomapper.net/foro/showthread.php?t=52&highlight=allocblock

Editado agosto 27, 2011 a las 14:38 por S34Qu4K3

[Martinssj4]

borra el sky q recubre el mapa (si es que hay uno)

 

para encontrar el leak usa esto:

http://www.mundomapper.net/foro/showthread.php?t=10555

[Miniscula]

nojoda ya le quite varios errores del mapa y las texturas extirada que tenia hasta lo volvi mas pequeño , le quite lo cuadrado y ahora resulta que me sale esto

 

Warning: No vis information, direct lighting only.
9767 faces
Create Patches : 65659 base patches
0 opaque faces
700883 square feet [100927280.00 square inches]
Error: Exceeded MAX_PATCHES
Description: The map has a problem which must be fixed
Howto Fix: Check the file http://www.zhlt.info/common-mapping-problems.html for a detailed explanation of this problem

[Martinssj4]

eso generalmente pasa cuando recubris el mapa con un bloque de la textura sky

[Miniscula]

no man ! nisiquiera le eh colocado la sky ¬¬

 

PD: y cuando le coloco el sky me sigue igual con el mismo error

[Martinssj4]

si compilas con el batch compiler, habilta la funcion "-sparse" que esta en la pestaña rad y vas a poder compilar con el vis y todo.

[Miniscula]

:(D=): coloque ese comando en parametro y nada (saca .bsp) pero sigue igual ¬¬

 

hlcsg v3.4 Final (Feb 25 2006)
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 (amckern@yahoo.com)
-----  BEGIN  hlcsg -----
Command line: "C:\Valve Hammer Editor\tools\ZHLT\hlcsg.exe"-wadinclude bloques.wad "C:\Users\juan olmos\Desktop\xmax10"
Entering C:\Users\juan olmos\Desktop\xmax10.map

Current hlcsg Settings
Name                 |  Setting  |  Default
---------------------|-----------|-------------------------
threads               [       2 ] [  Varies ]
verbose               [     off ] [     off ]
log                   [      on ] [      on ]
developer             [       0 ] [       0 ]
chart                 [     off ] [     off ]
estimate              [     off ] [     off ]
max texture memory    [ 4194304 ] [ 4194304 ]
max lighting memory   [ 6291456 ] [ 6291456 ]
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 ]
nullfile              [    None ] [    None ]
min surface area      [   0.500 ] [   0.500 ]
brush union threshold [   0.000 ] [   0.000 ]

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

5 brushes (totalling 30 sides) discarded from clipping hulls
CreateBrush:
(0.19 seconds)
SetModelCenters:
(0.00 seconds)
CSGBrush:
(0.55 seconds)

Including Wadfile: \program files\valve\cstrike\bloques.wad
- Contains 21 used textures, 52.50 percent of map (79 textures in wad)
Using Wadfile: \program files\valve\valve\halflife.wad
- Contains 18 used textures, 45.00 percent of map (3116 textures in wad)
Using Wadfile: \program files\valve\cstrike\cstrike.wad
- Contains 1 used texture, 2.50 percent of map (123 textures in wad)

added 13 additional animating textures.
Texture usage is at 1.54 mb (of 4.00 mb MAX)
0.93 seconds elapsed

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



hlbsp v3.4 Final (Feb 25 2006)
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 (amckern@yahoo.com)
-----  BEGIN  hlbsp -----
Command line: "C:\Valve Hammer Editor\tools\ZHLT\hlbsp.exe""C:\Users\juan olmos\Desktop\xmax10"

Current hlbsp Settings
Name               |  Setting  |  Default
-------------------|-----------|-------------------------
threads             [       2 ] [  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 ]
noopt               [     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 8192)


SolidBSP [hull 0] 500...1000...1500...2000...2500...2887 (0.15 seconds)
Warning: === LEAK in hull 0 ===
Entity info_player_start @ (2340,1440,-132)
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

SolidBSP [hull 1] 500...1000...1500...1889 (0.06 seconds)
Warning: === LEAK in hull 1 ===
Entity info_player_start @ (2340,1440,-132)
SolidBSP [hull 2] 500...1000...1500...1898 (0.07 seconds)
Warning: === LEAK in hull 2 ===
Entity info_player_start @ (2340,1440,-132)
SolidBSP [hull 3] 500...1000...1500...2000...2229 (0.09 seconds)
Warning: === LEAK in hull 3 ===
Entity info_player_start @ (2340,1440,-132)
1.70 seconds elapsed

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



hlvis v3.4 Final (Feb 25 2006)
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 (amckern@yahoo.com)
-----  BEGIN  hlvis -----
Command line: "C:\Valve Hammer Editor\tools\ZHLT\hlvis.exe""C:\Users\juan olmos\Desktop\xmax10"
>> There was a problem compiling the map.
>> Check the file C:\Users\juan olmos\Desktop\xmax10.log for the cause.

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

 

 

 

Ayuda porfavor!

alguien que sepa bastante de mapping me podria ayudar ?=():

[Martinssj4]

awe pero tenes un leak, arreglaste el anterior error, pero tenes leak, busca el tutorial de leakmaker q postee, eso te va a ayudar

[Miniscula]

awe pero tenes un leak, arreglaste el anterior error, pero tenes leak, busca el tutorial de leakmaker q postee, eso te va a ayudar

 

 

man ese tutorial no me ah servido en lo mas minimo ! lo hago y tal como dices . nose que pasara , pero cada vez que coloco una entidad "info_player_star" sale como un leak (demasiado raro) y uso el programa y cuando abro el .map con el VHE me sale un leak (un solido que en el VHE nunca hice, un objeto volando) lo elimino (solo me sale ese y en la compilacion me dice que hay 3 leaks) y bueno para asegurarme de que por lo menos ese leak fue solucionado vuelvo hacer el procedimiento del tutorial y adivina q , el mismo leak presente D:

 

 

Ayuda por el amor a Dios :(lloro):

 

 

PD: no quiero que 4 meses se vayan a a la $#$$%$%$

[S34Qu4K3]

Osea, que ni te molestaste en leer el tutorial

[Miniscula]

Osea, que ni te molestaste en leer el tutorial

 

man yo dije "ese tutorial no me ah servido en lo mas minimo" si escribi eso fue porque lo segui paso por paso ¬¬

 

Alguien porfavor ayuda , como lo explique arriba en mi anterior comentario , el programa leakmaker solo me encuentra un leak (un leak de un solido invisible) pero lo mas raro es que cuando vuelvo hacer el procedimiento me sigue saliendo el mismo leak y eso que lo borro y sigue apareciendo!

SOLUCION PLEASE D:

 

 

 

PD: tu nisiquiera te molestas en leer lo que escribo xD

[S34Qu4K3]

Repito, ni leiste lo que hace el programa

 

El leak marker TE VA A CREAR UN SOLIDO EN EL LUGAR DONDE ESTA EL LEAK, osea, te esta marcando donde tienes un agujero en el mapa para que tu lo cierres. Si solo borras el solido que crea el leakmarker es obvio que no te va a solucionar nada.

 

Espero que ahora lo entendieses

Editado agosto 28, 2011 a las 17:08 por S34Qu4K3

[Miniscula]

bueno man ahora si entiendo el uso del programa !

pero man vengo a decirte que es imposible que halla un hueco donde sale el solido , ya que sale suspendido en el aire D:

[S34Qu4K3]

Pon una imagen de tu mapa en el VHE donde te aparezca el solido

 

Recuerda, tu mapa tiene que estar cerrado, con SKY o lo que sea, no puede haber nada en contacto con el "vacio negro" del VHE

[Miniscula]

Pon una imagen de tu mapa en el VHE donde te aparezca el solido

 

Recuerda, tu mapa tiene que estar cerrado, con SKY o lo que sea, no puede haber nada en contacto con el "vacio negro" del VHE

 

no man el problema es mas grande , con una foto no se solucionara nada !

sigo sin entender que sucede , como te dije el solido sale suspendido en el aire sin ningun solido alrededor , lo mas extraño es que use la forma mas compleja que es la de "cargar point file" y se ve que las rayas salen por todos los lados del mapa estando cellado de pies a cabeza , rebiso igualmente porque donde sale el point file y esta super cellado , lo ms extraño es que traspasa el solido como si no estuvier presente en el mapa , transpasa el suelo y en el counter se ve bugeado D:

 

Ayuda porfavor ='():

[S34Qu4K3]

Ponme una imagen del mapa desde arriba

[Miniscula]

Bueno man te dejo 2 imagenes una en el VHE y una en el counter !

Ya pude solucionar el problema de allouckblock:full !

 

pero me resulta imposible quitar los leaks

 

en el VHE

 

 

 

 

 

en el Counter (fijate el suelo y de las rejas bugeadas)

 

les coloco func_wall y rendermode-solid no light y se ven rosadas en el counter D:

me imagino que el problema de las rejas el por los leaks.

 

 

bueno a las palmeras no le coloque func_wall todavia xD

 

 

 

PD: entonces cual seria el problema ? ='()::(lloro):

Editado agosto 28, 2011 a las 23:30 por Miniscula

[S34Qu4K3]

Aja, vale, te lo voy a explicar a ver si lo entiendes:

 

Ninguna entidad o solido con entidad(en tu caso las rejas) pueden estar fuera del mapa, osea, en contacto con el vacio

Te pongo un ejemplo:

 

Tengo una habitacion vacia, un cubo, si yo selecciono una de sus paredes y la convierto por ejemplo en func_wall, voy a tener un leak porque ese solido que ahora es una entidad esta en contacto con la nada

 

Espero que entendieses y que fuera eso

[Martinssj4]

pasame el rmf tuyo y el wad por mp y lo reviso mañana.

[Miniscula]

Aja, vale, te lo voy a explicar a ver si lo entiendes:

 

Ninguna entidad o solido con entidad(en tu caso las rejas) pueden estar fuera del mapa, osea, en contacto con el vacio

Te pongo un ejemplo:

 

Tengo una habitacion vacia, un cubo, si yo selecciono una de sus paredes y la convierto por ejemplo en func_wall, voy a tener un leak porque ese solido que ahora es una entidad esta en contacto con la nada

 

Espero que entendieses y que fuera eso

 

 

men pero el piso no es ninguna entidad y se ve bug ! y las rejas no tocan el vacio , lo que toca el vacio son las palmeras y no les eh coloca entidad

 

man y como te dije , igualmente hice lo que nadien recomienda , envolvi mi mapa en un gran cubo de sky para ver si era lo que dices y nada , sigue el problema

[S34Qu4K3]

Ponme el log.

La parte del leak nada mas

[Miniscula]

aca esta

SolidBSP [hull 0] 500...1000...1500...2000...2500...2887 (0.14 seconds)
Warning: === LEAK in hull 0 ===
Entity info_player_start @ (2340,1440,-132)
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

SolidBSP [hull 1] 500...1000...1500...1889 (0.07 seconds)
Warning: === LEAK in hull 1 ===
Entity info_player_start @ (2340,1440,-132)
SolidBSP [hull 2] 500...1000...1500...1898 (0.06 seconds)
Warning: === LEAK in hull 2 ===
Entity info_player_start @ (2340,1440,-132)
SolidBSP [hull 3] 500...1000...1500...2000...2229 (0.10 seconds)
Warning: === LEAK in hull 3 ===
Entity info_player_start @ (2340,1440,-132)
1.86 seconds elapsed

 

 

hasta los cts se me bug en la compilacion :(nuu):

[S34Qu4K3]

Borra todos los spawns que tengas y compila, y pon el log