So I was trying to map for Portal... [Fixed!]
...When suddenly I opened Hammer the next day and found that none of the grid views worked. They were pitch black, even when I tried to changed the view settings on them. Does anybody else have this problem?
EDIT: By grid views I mean Window views.
Maybe the solution is very simple: In the left top corner there is the button "Toggle grid".
A map pack coming soon. - click for more information
I should have been more specific: It's not the grid, (I've known about that trick since the beginning,) but the screens don't show up at all. The view boxes are completely black, and changing the view settings won't fix it. The Textured view is disabled too. Sometimes when I put my mouse cursor over the screen, it just disappears. Something must of broken during the upgrade to Source MP last month...
Are you opening the file from the normal open, or from an autosave?
There is a bug where if when you start Hammer, and the previous shutdown was 'bad', then it asks if you want to load the autosaved version, if you say yes, then it screws up the 2D views (form em atleast), but its ok again if you then close/reopen hammer.
Rob.
No, I never use autosave. Just to clarify; the problem I'm having is just in the Portal Hammer Editor, not the Portal 2 authoring tools one. If anybody else still has the Portal tools, can you check to see if you have the same problem as I do?
I almost have the same problem.
Except i still have my grid.
But when i place an entity, the icon of the enitity is blurry.
Except i still have my grid.
But when i place an entity, the icon of the enitity is blurry.
hmm... Strange... Sounds like the source MP update broke it then.
I usually have that problem after switching from portal 2 back to hammer. But then I drag around the 3d view and things usually pop up. (Sorry, not quite sure that helped you)
No, this is about Portal and Source SDK,
but your problem usually happens when not running portal 2 in -sw mode
This happens majorly when the configurations are used in the wrong engine. I have had this happen to me many times when I tried to use the 2007 source engine to launch hammer for hl2:deathmatch or TF2. The fix would be to copy over the game configurations to another engine and try to launch hammer.
You could also try verifying the integrity of the cache also.