Post your Portal 2 Authoring Tool Bugs
Hammer crashes randomly that's just how it goes. Unless a particular action triggers it repeatedly just live with it.
Two problems I have run into while mapping:
After hammer crashes, it reloads an "autosave" which has no views other than the 3D view. All the instances are collapsed (you have to click on them to reload them for some reason)
The compiler compiles my entities backwards. I have no clue why this happens; they are the right way in Hammer, then turned 180 in Portal 2.
I get the same thing. I usually click yes (then cilck yes for it to rename) and then close hammer then reload.
Uhmm, sorry if I am just doing something stupid, but I cannot get instances to work in my maps.
When I try to select the VMF file, the instance does not load. If I try to compile a map (Example maps), that already have instances in them, hammer crashes. If I select an instance in these maps, an error message pops up, and the instance promptly deletes itself.
Since this problem comes up when I am messing around in properly functioning maps, I am sure that it's a hammer problem, not something I'm doing wrong. I've tried for days to fix this and still have no idea what's going on. Please help!
Edit: Found out what was going on thanks to Will T. Had to "Verify the cache". Works like a charm now.
Did you use "Verify integrity of tool cache" to automatically check for and re-download broken or missing files?
Make sure the "instances" folder is in the same directory as the map you are loading.
Hammer seems to crash often when manipulating instances (moving, duplicating, etc). I cannot reproduce the crash as it seems to happen randomly (however, it is always the case after doing something with an instance).
I have error with leaks to entities but when I fix it and look around there's no leak.
but when I run map again it refer other entities again and again that the entities did not cause the leak before.
but when I run map again it refer other entities again and again that the entities did not cause the leak before.
Entities dont (unless theyre outside the map) cause leaks. The compiling process simply uses them as points of reference to what is inside the level and what isnt - so it only points out the FIRST entity it finds leaked, as at that point, theres no point continuing anyway. Id say, check harder - load the pointfile. Its far more likely (though it IS possible) that theres a tiny gap that you overlooked somewhere than that the system that hammer used for compiling maps for years now is broken.
I've experienced a rare bug in which the "Properties" window for an entity opens up when I tell it to, then immediately goes "inactive" and can't be clicked on - Windows just dings at me when I try. The only way to get that screen space back seems to be to restart Hammer. At least it's still possible to save open projects while it's obstructing everything...
I've never experienced this one with older versions of Hammer. It's infrequent, but incredibly annoying when it happens.