vrad.exe constantly crashing Created 13 years ago2011-04-25 21:04:14 UTC by Striker

So for some time I'm having this absolutely frustrating problem with vrad.exe: it stops compiling when it's about to finish.
It only happens on bigger maps, but I used the cordon tool and it still does that.

I'm trying to complete the work on gm_abysslift, Sunday making the first "test" compile after quite some time, and it worked. The second compile, after just adding a npc_pigeon, it refused to compile!
Then, I thought, let's test it on only one core. And it compiled. Next time, it didn't. It kinda randomly compiles, when it wants, but it does that rarely.

Vrad.exe stops using the CPU when it has consumed about 960-970 RAM memory, although plenty of memory remains free(about 1,2-1,5 GB).
What seems to be the issue? This problem drives me crazy, I've encountered it several times on other maps too, and only compiled them "by luck".

Add to all that having to kill hammer, SDK and Steam everytime I kill vrad.exe. Else, when I try to compile again I get the foolish Steam Startup error -_-.

Did you try to reinstall?

are you compiling using -low priority parameter by any chance?

Anything in the log? And for now, nerf the pigeon.

Nope, nope, and nope.

This is what I have for $light_exe:
-StaticPropLighting -game $gamedir $path$file

Sounds like your cpu doesn't have enough to push vrad. Happens on my comp all the time. Im on a AMD Athlon x3 3ghz, with 4 gigs of ram.

Sounds like your cpu doesn't have enough to push vrad. Happens on my comp all the time. Im on a AMD Athlon x3 3ghz, with 4 gigs of ram.

Sorry, that's not a valid explanation. It only has to take longer on slower processors, but not crash due to lack of power.

have you tried just a regular compile? not an expert one?

have you tried just a regular compile? not an expert one?

Yep. Same result :(.

You think you've got a problem?

My compiler is a twat ; Most of the time , it won't even start vbsp. Sometimes , after doing vbsp , it finishes there. Even fewer times it'll do vvis.

I think you can see where i'm getting at ; it takes half an hour to actually get all three programs to actually run

I have vague memories of a similar problem that I was experiencing a while ago. Is Windows returning an error that vrad.exe has stopped working, or does the progress counter in the compile window simply stop? If it's the former of the two, I found that vrad.exe seemed to be crashing after it had completed all of its lighting calculations and was preparing to stop, so I could simply let it "crash" and the map, itself, would be compiled successfully.

If the progress counter just stops, try killing vrad.exe through the task manager and then see if you get properly compiled results; killing it should tell the compiler to move on to the next step in the compile process, if I'm not mistaken.

I guess the next step would be shutting down hammer and running a batch compiler.
See if The Mighty Atom has the Compilator setup for source compiling yet.

Whats you computer specs? CPU ram?

Fi3nd, I don't think I have such low specs that it even matters. You can check my profile if you want for my pc specs.

See if The Mighty Atom has the Compilator setup for source compiling yet.

Sorry, but i don't, compiling Source maps outside sdk is very buggy and leads to vbsp crashing and missing materials errors.

So for the time being, there's not going to be support for Source. I might give it another try, but not for the moment.

Sorry.

Nothing helps it work. I deleted Source SDK :x. I had enough.

Reinstalling now.
[EDIT] Wow. That worked. I"m posting here the full compile log just in case this was a one-time luck compile.
Curiously, I have no errors. I even checked on the Interlopers error page.

[EDIT2] Nevermind the log. I was right, that was a lucky compile. The difference is that now it "properly" crashes. Windows displays the error box message and then hl2 launches displaying a fullbright map.
Absolutely wonderful.

[EDIT3] Made a 'simple' map: A torus within a box. Vrad.exe crashed.
WHAT IS WRONG WITH IT

[EDIT4] Found this external compiler. I'm going to try it. Seems like an updated software(last update 31st March 2011).I hope it works.

Minor edit(yeah,I know, lots of edits): Hah, I found a "twhl.jpg" file inside the archive of this program. It's gotta be somebody we know :D.

Ok, very simple question:
Where do you guys keep the path for the vmfs?

Sorry for double post.

[EDIT] Nevermind, I changed the path from within sourcesdk_content to another folder, but it still doesn't work. Vrad.exe still crashes. Even on simple maps. And I reinstalled SourceSDK. And I tried setting different compatibility modes. It just refuses to work :(.

Ha, i may have found an answer to your question, at least, i've found conditions when this happens to me.

Sometimes, i can keep hammer and counter-strike open, and compile multiple times while playtesting, with no problem. However on bigger, more complex maps, i find i have to shut down hammer and restart CS every time, else i get the VRAD hanging or crash error.

For example, sometimes VRAD compile crashes or or runs forever for no apparent reason, but if i shutdown CS and restart Hammer (sometimes requiring to restart SDK), the vrad glitch is gone the next time i compile. Also, make sure you don't accidentally have to instances of Hammer open. (not sure if it's related, but sometimes when this happens i also have a extra hammer window open)

hope helps! =)

I already tried that :).

If you run with fast vvis, does your vrad still crash? i've also noticed on big, wide open maps that my vrad will crash on full vvis, but not on fast fsr.

What optimization techniques have you used? i've found using func_lod on my my nuketown map makes it crash fsr. stupid/dumb question: have you changed everything not a visblocker into func_detail?

EDIT: just thought of something else for this. I've found recently that adding too many cubemaps(even one or two) can make a map compile FOREVER. Also, waiting is compounded if the map is poorly optimized or wide open.

BTW: are you running normal or fast vvis?