Compiling crash when map gets too big Created 7 years ago2017-10-20 12:59:28 UTC by qckdth

Hey there,

here is another one: when my map gets too big or whatever the problem is, the compiling program doesn't finish the compiling process. CPU-Usage goes to 100%. Even if I stop the editor, cpu-Usage continues to be 100% on other programs running.

I'm using Valve Hammer Editor 3.5.2. with zhlt 34f x86sse2 build files.

Also had some trouble to get water moving. I could imagine that's somehow connected.

Greetings
qd

That's not quite enough to go on, could you post the compile log? Maybe show us how big your map is, that will also help.

Sounds like the compile is taking a long time, and that perhaps you are impatient?

"not finishing" means its still compiling.

Also, the compile process is not linked to the editor being open or closed. The compilers will continue to run with the editor open or not (csg, vis, rad etc...). (you can always kill them from the task manager)

I think your first mistake is using VHE.

Just let it compile for a while, take a walk or go grab something to eat. If no errors appear, let it go on, your computer could be slow. Some compiles take hours, if not days.

Now the thing is, i compile the map several times during the process of mapping. It starts taking like 5 seconds. The last time it usually works, it takes like max 30 seconds. Then suddenly the compiling doesnt finish anymore after 5 minutes and longer. So that doesn't fit together really.
I'm gonna try other compiling tools now and let you know what happens.

Now I tried to use these one here: https://forums.svencoop.com/showthread.php/44536-Modified-version-of-VHLT-34 (UnkleMike's ZHLT v34.zip). Now I assume, since it is kind of the same name as before, it doesn't differ that much from the files I had before. But this time i used the x64 versions. The program successfully compiled the .bsp files, even though in the end it gave me an error message. This message only occurred when it tried to build the .pts file. Now I looked into my compile folder and all the .pts files are 0 kb, even before i changed the compiling tools. But the .bsp is now working. I repeated this to make sure, and the .bsp compilation is now working (including the error message about the .pts file in the end).

What are .pts files? Are they important for anything?

Visleaves

Portals

If your PTS file is 0 kb, then VIS didn't run properly I guess. This means you probably have a leak in your map.
Also try tying all complex brushwork on your level to func_detail, but first make sure if the specific piece of brushwork you want to tie doesn't seal the map from the void.

Sorry if you find any mistakes, my English is pretty bad.

You should open the compile process log file and look for any error messages. Post the error message(s) here so we can help you fix those. I'm guessing there's a problem with your map that prevents a successful compile.

Using Hammer is fine, but there are other editors out there that are better, such as JACK and Sledge. If you want to stick to Hammer for now, that's totally fine.

It's BatchCompiler, not PatchCompiler, SSB.

Hey,

https://www.dropbox.com/s/1eqrjwrzh00y8ql/qd1a2hv6.log?dl=0

this is a link to the log file for one of my latest maps that didn't work with the old compile tools but are working for .bsp compilation now, however not for .pts compilation. It is an outdoor map with a skybox around it (I do that for every map to prevent light leaks).
Can you tell me what's wrong?

Greetings

@qckdth

Let me take a look at your map.

Hey there,

I didn't really want to post any specific map, but in the further process i found out that this issue happens on pretty much every map I'm compiling now with the new compile tools.

Greetings

Try using Vluzacn's tools, Uncle Mike's tools are way more advanced and much newer, so there might be unknown issues there.

If it works with Vluzacn's then the problem is in the tools, if it still fails then you should post a couple logs so we can see if anything strange is showing up.

Also provide one of the map sources so we can see if you've got anything weird going on.