VBCT - Valve Batch Compile Tool - Page 3

ChronoTriggerFan · 07-15-2009, 04:17 PM

I use it for anything that doesn't take 30 seconds to compile (like my testmaps do). But apparently thats not an option of this poll...

(s2a) yahodahan · 07-15-2009, 04:23 PM

good point. that would be like...like, tying my shoes for anything other than a Level 9.5 Event. unwarranted use of overkill.

grazr · 07-15-2009, 06:28 PM

Quote:

Originally Posted by A Boojum Snark

...
Really the only reason I see to use VBCT is being able to monitor the status of the compile. Every other thing about it I don't like.

Plus, if your processor is powerful enough, (dual core helps), You'll be able to monitor its progress in Hammer anyway, as it compiles with relatively more ease.

If you're running a decent system this seems somewhat redundant.

I don't usually get this problem unless i've used the computer previously to do something else, that has eaten up a whole load of memory i forgot to free up before starting a compile.

Mokagogo · 07-15-2009, 07:37 PM

I've been using VBCT since about March and I love it. Yes, it does use the same executables.

One tip I have for you: for a fast bsp-only-style compile, or even bsp+LDR rad, it's ideal to keep TF2 minimised in the taskbar, run the compile (without vis, and using the -fast button) on VBCT and then task back into TF2. It's kept my workflow very solid indeed. However, if you're doing proper, full or final compiles, you'll probably need to close TF2 because I've found that it tends to crash vrad with an unspecified error at the very end of a full or final compile. Sometimes, anyway (but not always).

Quote:

Originally Posted by A Boojum Snark

That's only because VBCT automatically runs the compilers at "Below Normal" priority, which you can do via the task manager regardless of how you started the compile. Not to mention all the compilers have -low and -high flags to specific their priority.

Really the only reason I see to use VBCT is being able to monitor the status of the compile. Every other thing about it I don't like.

Frankly VBCT's 'ugliness' is really a weird thing for people to take issue with: it has a clean interface, is completely lag-free, works almost instantly out-of-the-box. Do we really need some shiny windows skin with alpha-transparency to round off the edges of the tool?

With Hammer, it's impossible ever to be _quite_ sure that the compile hasn't crashed and you're just watching your computer mindlessly crunch data. Certainly back in the days when I didn't know what a sensible portals number was and desperately needed to func_detail a few things, it was horrible that Hammer would lag the heck out of my computer and the status of the actual compile wasn't even clear. Now that my vvis stage is pretty quick it's not such an issue.

I tried playing with process priorities in the task manager for Hammer and it doesn't always work; and when it does work, it doesn't work well. VBCT requires no such tinkering, and I can close Hammer entirely and watch a TV show or a movie while my compile is happily chugging away in VBCT.

VBCT also gives you precisely the same tools log output when you use it, so there's no loss of information should you encounter errors.

Furthermore, because it simply batches Valve's included compile tools, it'll never go out of date; it's as trustworthy as the real thing; and you can be sure that you're not losing 'something special' that Hammer should be giving you.

Furthermore, it's listed on Valve's own wiki: http://developer.valvesoftware.com/w...h_Compile_Tool

I suggest you use it!

*edit:* Note: There should be a poll option that says, 'My existing choice for all compiling'!

A Boojum Snark · 07-15-2009, 09:21 PM

Quote:

Originally Posted by Mokagogo

Frankly VBCT's 'ugliness' is really a weird thing for people to take issue with

With Hammer, it's impossible ever to be _quite_ sure that the compile hasn't crashed and you're just watching your computer mindlessly crunch data.

Furthermore, because it simply batches Valve's included compile tools, it'll never go out of date; it's as trustworthy as the real thing; and you can be sure that you're not losing 'something special' that Hammer should be giving you.

Furthermore, it's listed on Valve's own wiki: http://developer.valvesoftware.com/w...h_Compile_Tool

I suggest you use it!

To respond in order:
I never said anything about "ugly". As I said, it's the hardcoded stuff I don't like. I want to be able to run at BSPZIP to the end of the compile automatically. Something I could do with batches/nem's and now only can do with Hammer because VBCT is lame and has no open-ended fill-in-the-blank options.

It's entirely possible to know if the compile is still running. If the exe is listed in the task manager, and it's still using cpu cycles, it's still running. If it crashes or freezes it will either be missing or at 0%.

All third party compile managers use valve's tools, so that's a moot point. And the only custom compile tools themselves are usually better than valve's. (though that's yet to really show up yet, since valve has been updating the source engine so fast and repeatedly.)

By definition, a wiki can be edited by anyone. It doesn't mean valve is endorsing it or anything, it's just a resource site.

I'll use it (and I do), when I feel like it. The shortcut is sitting next to the SDK one, I just take issue with it being so damn unfriendly to advanced users for the sake of what amounts to nothing more than monitoring the compile nicely.

Open Blade · 07-16-2009, 01:49 PM

I've thought about using one of these newer programs but honestly, after 5 hours of straight Hammer work, when I finally do decide to run a compile, it doesn't hurt me to get up and leave the PC for an hour and go do something else (play with dogs, eat, light weights, etc..). I guess if you're somebody who wants to compile all the time, then this would be great. But I probably run a compile every few days and that's it. No need to change a single light and then go see how it looks

SiniStarR · 07-16-2009, 02:40 PM

I like it for it's cancel button plain and simple. I cant tell you how many times I forgot to tick a visgroup like the skybox and have to wait for the compiler to stop in Hammer.

Quote:

Originally Posted by Open Blade

No need to change a single light and then go see how it looks

well aren't we Mr.Perfectionist