Hammer snaps to the lowest grid

There are times when I'll be mapping and (maybe) I'll hit a hot key and
hammer will suddenly make me snap to the lowest grid value (1 unit).
I'll increase the grid size to the highest, but hammer will still make
me snap to 1 unit reguarless to the fact that its suppost to snap to
every 256 units. This is really annoying when trying to do bigger grid
snaps.

The only way I can fix this by deleting all of the source SDK and re installing it (takes me about an hour to do).

Any thoughts/suggestions?

---

Posting And You

Does this have anything to do with it?

Valve Wiki said:
Snap Selected to Grid <Ctrl+B>
Not all objects will align perfectly to the grid, due to moving or resizing of the objects or changes in the grid size. This command will snap the bottom and left sides of the object to the grid. If more than one object is selected, the command will use the lowest to the bottom and leftmost objects to align all the objects as a single group.

<A name=Snap_Selected_to_Grid_Individually_.3CCtrl.2BShift.2BB.3E></A>
Snap Selected to Grid Individually <Ctrl+Shift+B>
Identical to Snap Selected to Grid, except that each object in the selection is snapped to the grid on its own, instead of using the bottom and left edges of the group bounding box.

The problem isnt where it snaps....its the fact that I change the grid
size to 256 x 256 (as in an object will snap to every 256 units) units
and hammer is STILL making objects snap to every 1 unit

---

Posting And You

I did some googling but couldn't find an answer, sorry. I hope someone else knows whats up.

It's because the thing is always snapped to 1 unit (otherwise you could make floating point values which aren't supported by the engine). Chances are you hit a shortcut key to turns snap to grid off.

You didn't explicitly say that "Snap was on", so I'm just pointing it out. If this is the case, give Morphine credit.

---

Blame it on Microsoft, God does.

Yeah that actually makes sense... with snap to grid off it just ignores the grid completely, regardless of size.

Thanks for pointing that out Crono.

They changed the shortcut for toggling snap to grid to shift-w...bloody stupid shortcut to assign to it if you ask me. I use shift a lot, and I use W a lot, so inevitably accidental shift-w's also happen. Even worse is the fact that ctrl-w toggles ignore groups - a hugely useful feature, sure, but one I don't like jumping into accidentally all the damn time.

---

[img]http://card.mygamercard.net/sig/Default/reno84.png[/img]
Designer @ Haiku Interactive | ReNo-vation.net

Yeah that actually makes sense... with snap to grid off it just ignores the grid completely, regardless of size.

That was what I was looking for, and reno's suggested answer fixed the
problem (shift-w fixes the problem). Morphine's answer had more to do
with where the snapping point was (center/bottom/left).

In anycase the problem was cleared up when I hit shift-w. Who should I mark correct?

---

Posting And You

The issue was you turned off "snap to grid". Morphine suggested that was the issue first ... everyone else just added to it with a reason why. Also, no one else marked their response as an answer.

Do you need me to tell you how to tie your shoes next, or ... ? :razz:

---

Blame it on Microsoft, God does.

ReNo's answer was correct, he could repost his comment as a possible solution, or just mark the thread case closed.

The issue was you turned off "snap to grid". Morphine suggested
that was the issue first ... everyone else just added to it with a
reason why. Also, no one else marked their response as an answer.

Do you need me to tell you how to tie your shoes next, or ... ? :razz:

Im reminded of the time in Futurama when fry needed to hit a giant button the size of his head, but misses...

---

Posting And You