Hammer not starting after DLC update
E: Verifying Portal 2 and Authoring Tools cache helped. Now I can compile.
BTW, did someone try whether you can now build cubemaps easily without moving the map to the dlc folders?
Brainstone wrote:
Thank god, it works again.
BTW, did someone try whether you can now build cubemaps easily without moving the map to the dlc folders?
On that note, do VPKs work again? I would test it myself, but I'm at school now.
EDIT: Just tested VPKs. Still no VPK functionality.
Also, I got Hammer to start, except that it won't respond to any input when I try to browse for a model. any ideas?
EDIT 2: If the problem with building cubemaps before was that it crashes right before it's finished, that still seems to be the case.
Spam Nugget wrote:
Do valve not test these things before they release them? I mean, honestly, it wouldnt be that much work to update one pc and check that things work before they send the updates to everyone. its not like its an obscure error or anything, it just doesnt bloody work. and yes i know its fixed now, and if its that quick to fix then that just reinforces the arguement that they should have tested and fixed this before it was released. They do this all the time, do they not learn from their mistakes?
Exactly! It pissed me off as well that they don't care about looking stupid in front of millions of ppl.
If they REALLY NEED the game to start looking into the new dlc2 folder because there's no other way they can make the game run as they expect, AT LEAST tell ppl! Tell us "ey, you know what?, from now on the main path the game will search into is portal2_dlc2... if you want to build cubemaps for example, put your vmf there
"
I think there should be a really good reason to force us begin to use a new folder... but at least tell us.
Random wrote:
I still can't compile with Hammer. It says it can't find vvis. And yes, I've tried verifying the files several times.
For some reason SDK redownloaded all the SDK compiling executables and I found my firewall was blocking them in the sandbox.
Check if they exist first and then check if your firewall is the problem.
I had the problem with the vvis aswell but lp's fix worked for me!
lpfreaky90 wrote:
Quote from a valve employee if you're still experiencing problems with hammer:Quote:
You'll need to delete vbsp.exe, vrad_dll.dll, vrad.exe, vvis_dll.dll, and vvis.exe from your bin directory, then re-verify your Portal 2 cache.
The issue is that the build tools in SDK were colliding with the tools now packaged into Portal 2. By deleting the files, Portal 2 should put the correct files back on your disk.