There are lots of problems with compiling inside Hammer. Compiles are often slowed down because of Hammer using a lot of memory, plus Hammer is frozen while the Compile is going on. And when you finally get ingame, Hammer is still using the memory, and depending on your computer, the game will run slower than it would with Hammer closed. I don't recommend compiling with Hammer open and esspecially not testing with Hammer open.
If you want to compile outside Hammer, I suggest you get a copy of VBCT by Quicksilver <http://qsextreme.com/vbct/> It's an excellent tool - although it still isn't fully polished - I actively use it for compiling and it has a lot of useful features. I just wish it was Open Source so I could polish it a bit more. ;)// > I hear your pain, bro. > > Thanks, > - Saul. > > > 2009/8/30 Jorge Rodriguez <[email protected]> > > >> This is only slightly off topic, but: >> >> Every version of Hammer (even back to Worldcraft and before) I've ever >> worked with, the build window always stops updating about 20 or 30 seconds >> into the process. All of Hammer then freezes up until the build is >> completely done, so progress isn't visible. Does this happen to anybody >> else? >> >> -- >> Jorge "Vino" Rodriguez >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlcoders >> >> >> > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
