So, there is this issue that seems to be a recurring event with hammer that just upsets me slightly. Sometimes when saving and then reloading a map, hammer will displace almost everything by .5 units. When you restart the map, suddenly half the map is off the grid by .5 units, and because there is that one square that isn't, you can't select the entire group and fix it. This has happened 2 times. Once on a version of money that I worked on with DrummerX, and once recently with mines. I just spent an hour moving the damned vertices back onto the x64 grid lines that they seemed to be off by some slight margin. anyone else had weird shit like that happen that is just annoying as fuck?
Not as much hammer as the engine itself. Hammer pretty much can't do anything, so it doesn't do much wrong for me either. Most problems i have are related to it not registering the release of keyboard keys or mouse buttons. I remember one time though it would save the map in a corrupt way. Couldn't open it afterwards. Unfortunately i didn't know this at the time, so when i was done for that day i copied the last save to all my backup folders. Every single version i had of that map was lost to me that day. When i found out a few days later i decided never to restart that map again. For weeks after when i was done mapping for the day i always closed down hammer and the sdk, opened them all up again, and loaded the map to see if it was corrupt. Only then would i copy it to my backup folders.
first flag on eastborough would not show up at all on the minimap. keef had to do some weird hacky shit just to make it work.
vmf is text based, use git for versioning, version every trivial change, don't worry about corruption ever again. Also I read that Valve are developing new tools for portal 2 and if I understood it right that includes something for mapping too. One can hope .... :D
This one time, Hammer just stopped showing half my map. Literally random areas just had bits deleted from them. Any time I even OPENED a vmf, it would do that to the VMF, let alone saving it.
The bug with the new orange box was pretty annoying, the one where everything went to black and the only way to show stuff was to put out entities. http://forums.blackmesasource.com/showthread.php?t=5706
That's a bug with my custom water texture, there should be a visgroup I set up (or an automatic one) to hide the water and fix that. I have no idea why it does that. Although if you decompiled it you quite possibly wont' have any of my visgroups or object groups, which will make the map kind of annoying to edit. Strange that you appear to have my skip handles though, I wasn't aware the compiler exported them with the map.
I get this strange error only with the shaded textured camera view where the textures on the sides of brushes get scaled up by about 100x but only if i look at them from a certain angle. I dont see it anymore now that I'm using the source 2009 hammer, which, by the way, makes OB hammer feel like ep1 hammer. Never really came across an explanation for that bug though.
"Never use the carve tool. Ever. For anything. And dont blame Hammer for crashing. It was you that cause it by excessive carving. You can make beautiful terrain in Hammer by using triangular prisms, meticulously sculpting the terrain whilst keeping the brush count low, which gives faster compile times and faster maps. " No shit sherlock :D
I posted it in the facepunch mapping section when he first uploaded it. So many tears of rage, I think the thread was 20 pages of crying.
If you make complex geometry in hammer, saving and loading the map can cause vertices to be moved because the vmf format stores brushes using planes, while hammer stores them using vertices, the conversion causes slight errors that aren't visible until you reload the map.
