Looks like a map from OpFor. I think one of the first places where you get to meet those alien troopers.
Don't know the name though.
EDIT: Damn that coding tut, why didn't it tell me about ANYTHING being case sensitive tired -Probably because that tutorial assumes you already know that. It's pretty standard stuff.
Tell me Scottie, if you can, you have destroyed so much (posters), what is it, exactly, that you have created?Just felt like saying that.
It really pays off.Literally, heh.
"%~dp0hlcsg.exe" "%~dpn1"If you're only benchmarking compile times, then there's no need to know about the Half-Life folders at all, only the compile tools and the .map file matter.
"%~dp0hlbsp.exe" "%~dpn1"
"%~dp0hlvis.exe" "%~dpn1"
"%~dp0hlrad.exe" "%~dpn1"
Read that . You guys talk like professionals , really .I program for a living, so yeah.
Completely wrong, potatis. I have never read a programming book in my life, and I know several programming languages. Practical experience is a lot better than reading some stupid old book. I knew nothing about PHP when I started TWHL3, nothing about C# when I started Twister 5, nothing about Visual Basic when I started my first VB program, nothing about C++ when I started that, either. To be fair, I was taught Java, Assembly, C (and C++, but this was after my first C++ project) and Scheme at uni, but not from a book.While I'd agree that good books are hard to find, there are still some good ones around. You're hindering your progress by ignoring them. I had been working with C++ for various years but only when I read 'Effective C++' by Scott Meyers did I learn various important things I had missed before.