It's Not Hammer Time Created 15 years ago2009-03-28 17:43:02 UTC by TawnosPrime

I went to start my mapping again, and lucky me, Hammer isn't working.

What happens, on both new and old maps, after I click on an object, it'll give me a warning that my 'load is very high' and after clicking ok, it will begin to cycle through every object behind the pointer (if there are 4 objects in line behind the pointer, it'll cycle through selecting each one).

WTF is the problem?

Uuummmm...it seems to have somehow fixed itself...

I'm baffled as to HOW, but it seems to be working again.

The Cycling, I don't understand, but it seems to be a by-product of the system load error, caused by the RAM being around full. Try turning off your computer more if you always have it in standby or hibernation, to clear the RAM or buy a bit more RAM if you always turn it off. (Correct me if I'm wrong about the cause and fix of the error.)

It's not my load, as this is the same system I've used since I joined TWHL and just finished a reformat. However, it does seem the be a load issue as I lowered the number of times I can undo, and it seemed to fix it.

AS I said though, it happened w/ a brand new, never seen a brush map. I placed two brushes, clicked on one, and got the error and the cycling. This makes me think, it's something else.

Your draw distance may need to be lowered as well, though I don't know if that would actually fix your problems as that's more to do with rendering than RAM consumption I believe. I've never seen anything like the constant cycling you described, but I believe there's some method of manually cycling through overlapped brushes in Hammer (I don't think I ever used it). Just how old is this computer you're working on, anyway?

In any case, best thread title ever.

Actually, my draw distances were quite reduced at the time. Lowering my undo levels allowed me to normalize them though.

As for the age of the system, it's about 3-4 years old w/ a P4 3.4GHz HT, 1GB RAM and an X300.

Oh, and thanks for the complement, though looking back, I probably should have put not in brackets

That is actually a slightly buggy feature of Hammer. If you click and hold while selecting in the 3D view, you cycle through all the objects that are in line with the pointer. useful for selecting things just behind each other. However, if the process is interrupted or gets activated while hammer is doing something else (like when you clicked the ok button) then it gets stuck, just click elsewhere to stop it

Well I was thinking this was like a PIII 400 MHZ or something crazy slow. You shouldn't have to reduce your RAM usage at all, and in fact you should be able to increase it from the default setting.

Hammer worked ok on my windows 95
true story