One error leads to another and so on ... :(

Now I can run csg just fine with no problem.. log writes fine and everything but when it time for bsp to kick in crashes with an unable to read memory error. When you click ok on it vis kicks in and the same thing happens with it...

Now I tested compiling an old map it worked fine.

Anyone have any idea what might cause this...

If I finish this map I can problebly write "The complete error guide to mapping in DoD - dos and don'ts" .. :o

My main problem is that I backup everyday... but this time I have worked like 6-8 hours since the last backup... :rolleyes:

Edit: I tried replacing all my texture with one and it compiled just fine... so now I just have to retexture my whole map it should be back on track :(

Edit2: Bah after another 4 hours work retextureing it happens again...

Apperently this happens when I have used to much texture memory or something... it doesnt matter what I do, if I texture a brush, it doesnt matter which one, the bsp compiler crashes and when I revert it null texture it workes fine...

Anyone else experienced this kind of problem. I have retextured my whole map but it didnt help at all either...

YES! :)

I found the problem. I used the include textures in the bsp and it didnt work... once I removed the option it started working again :)

/me feels like a madman, talking to myself...


EDIT: The above information isn't correct, it was in the csg not the bsp I include the textures.

ahha! yes, the include textures only works with CSG, not BSP.

To clearify somethings, unlike I wrote above (I was so happy it worked again, I didnt really get it out correctly), I didnt include the textures in the bsp, it was while csg:ing. Somehow that didnt work and my compiler crashed 100% when running bsp.

Once I removed the wad including it worked fine.

The really strange thing is that it didnt matter what brush I textured, once I had reached a certain limit of brushes it started crashing.

I use Zoners tools 2.5.3 - 1.7 for compiler and Nems batch compiler 2.0.1.

I hope this helps someone else in the future....

I seem to be having the same problem. So where do I deselect that option? I can't find it. :(

If you are using Nems Batchcompiler you have it under the CSG window. Its NOT selected by default so if you havent selected it before, it isnt selected...

i have the same texture problem now :( any more textures i add and it wont work :mad:

set your texture amount to 10000

if you have done that already

remove some of your wad files you have 2 many
or better yet compile all used textures into one wad clean and easy.

also make a D:\wads folder and place all your wads inthere
and use it from there hammer and zonerst. dont like getting
wads from alover the place specially from other drives , desktop &
my documents folders


hope this helps

thx, but i am using only 1 wad anyway, and its in my dod folder, how do u set the texture memory to 10000??

do I need nems? i dont use it, but i know i should :rolleyes:

Best bits from thread on my webby, subsitute 8192 for the amount you need:

-texdata 8192:

It needs to be added to all of the Compiler tools.

So all of the following lines in the Advanced compiler settings need to be edited.

$csg_exe $path\$file -texdata 8192
$bsp_exe $path\$file -texdata 8192
$vis_exe $path\$file -texdata 8192
$light_exe $path\$file -texdata 8192

This is the one reason why Nem's is so much easier to use



Taken from the Q&A Thread.

Only useful if you still, like me, use Hammer to compile.

Ok, here's the thing. I am a noob at this mapping thing so I still use Hammer to compile my maps. Everytime I try to create a map that is bigger, by this I mean similar to the size of "official" DoD maps, I get errors that crash Hammer. Hammer crashes when trying to run the game to test the map. I crash back to Hammer and dod never loads, but dod.exe isn't in my task manager and Hammer is all messed up visually. Something from this crash ties up my CPU and I have to reboot to get back to normal.

It seems to me like once I hit a certain limit of textures or of objects this crash starts occuring. 4 maps are currently on hold because of this problem.

I should also mention that I am using DoD retail.

Any ideas?

stop using hammer to compile ..

i know its not easy to setup a batch or understand how a compiler like tbcc or nem works, but compiling with hammer
is the road to more trouble

get tbcc and zonerst and follow the tuts that come with it

Nem's batch compiler and merl's tools are your best friend.

Originally posted by IR -inw-
stop using hammer to compile ..

I was afraid you'd say that, I'm just not good with all that stuff. I was pleased to see how easy Hammer was. :(

Once all that stuff is setup is it easy to use again and again?

It lets you get the exact stuff you want done, with more options, and doesn't freeze up a la "not responding" (even though technically hammer is...) But once you go batch, you never go back.

Can anyone tell from this why my map crashes when trying to run it?



** Executing...
** Command: Change Directory
** Parameters: C:\Program Files\Day of Defeat


** Executing...
** Command: Copy File
** Parameters: "C:\Program Files\Valve Hammer Editor\maps\dod_halten.map" "C:\Program Files\Day of Defeat\dod\maps\dod_halten.map"


** Executing...
** Command: C:\EP1\DODMAP~1\hlcsg.exe
** Parameters: "C:\Program Files\Day of Defeat\dod\maps\dod_halten"

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: C:\EP1\DODMAP~1\hlcsg.exe "C:\Program Files\Day of Defeat\dod\maps\dod_halten"
Entering C:\Program Files\Day of Defeat\dod\maps\dod_halten.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 [ 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.27 seconds)
SetModelCenters:
20%...40%...50%...70%...90%... (0.00 seconds)
CSGBrush:
10%...20%...30%...40%...50%...60%...70%...80%...90 %... (1.11 seconds)

Using Wadfile: \program files\day of defeat\valve\halflife.wad
- Contains 3 used textures, 11.54 percent of map (3116 textures in wad)
Using Wadfile: \program files\day of defeat\dod\dod_donner.wad
- Contains 9 used textures, 34.62 percent of map (124 textures in wad)
Using Wadfile: \program files\day of defeat\dod\dod_merderet.wad
- Contains 3 used textures, 11.54 percent of map (80 textures in wad)
Using Wadfile: \program files\day of defeat\dod\dod_kalt.wad
- Contains 11 used textures, 42.31 percent of map (85 textures in wad)

Texture usage is at 1.28 mb (of 4.00 mb MAX)
1.47 seconds elapsed

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




** Executing...
** Command: C:\EP1\DODMAP~1\hlbsp.exe
** Parameters: "C:\Program Files\Day of Defeat\dod\maps\dod_halten"

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: C:\EP1\DODMAP~1\hlbsp.exe "C:\Program Files\Day of Defeat\dod\maps\dod_halten"

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)


BSP generation successful, writing portal file 'C:\Program Files\Day of Defeat\dod\maps\dod_halten.prt'
1.50 seconds elapsed

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




** Executing...
** Command: C:\PROGRA~1\DAYOFD~1\dod.exe
** Parameters: +map "dod_halten"

I use Nemesis' batch compiler, and it is the easiest front end out there for compiling.

I don't see any reason right there for the error, so I either overlooked something, or the problem lies elsewhere...

like were is rad and vis ? :)

Originally posted by IR -inw-
like were is rad and vis ? :)

True but not very helpful, the lack of VIS and RAD shouldn't make the map crash.

Try using Nem's and see if that helps. Bare in mind that you need to save the file as a map file for Nem's. This is something Hammer will do automatically for you when using it to compile. You will need to save it if you use Nem's.

You could always search or ask at The Collective (http://collective.valve-erc.com/) . They have a forum for asking questions about Hammer and compiling: http://www.chatbear.com/board.plm?a=boardlisting&b=12&v=flatold

Originally posted by IR -inw-
like were is rad and vis ? :)

If you understand what is writen you will see that the compiler crashes in windows and a crashed dos based program will be stopped and doesnt generate a log file, thus you cant se it in the log.

So, its probebly vis that crashed and since it didnt run to the end, it didnt leave anything in the logfiles, since its the last thing it does before exiting.

actually he exluded VIS and RAD from the compile, look at these lines
** Executing...
** Command: C:\PROGRA~1\DAYOFD~1\dod.exe
** Parameters: +map "dod_halten"
thats running HL and the map.

Hammer had a sort of specialness with me and would always crash when i treid to start HL from it. try opening HL sepratly and running your map. the .bsp generated sucesfully so you should be fine. then you are moreliekly to get an error priunted out for you from HL.

Originally posted by Angry Beaver
actually he exluded VIS and RAD from the compile, look at these lines
** Executing...
** Command: C:\PROGRA~1\DAYOFD~1\dod.exe
** Parameters: +map "dod_halten"
thats running HL and the map.


True, but they are several separeted program batched together and its the programs that crashes, not the batch, atleast that's what happened in my case and since Keller says the same thing happened to him... So the program crashes, a windows error message comes up and when you click the only button in the message ("OK") the batch just jumps to the next program and continues without writing anything to the log.

In my case it was the wad include option that didnt work... here I have no idea....