ok, so i start making my map. get to the point where i want to use the uhh... clipping tool i think its called. (the one with the icon of a box with a cut corner) well, as soon as i click my hammer freezes. i get one of those stupid ass windows errors. any help?

what is the exact error? I know for a fact source hammer uses a lot more resources than 3.5... when my system load is high i get really sluggish performance from it and in photoshop "not enough ram" errors when performing certain tasks, specs are

p4 3.2ghz HT
1g corsair 400mhz

so yer, it could be attributed to the general load from hammer. Have you tried restarting your pc without running apps in the bg and seeing if it helps? What are your specs? screenshot of error window?

lol, source hammer is a 'general load' alright. Its undoubtably a memory issue PanFrie. Try quiting other programs, and find a program that will defrag or recover memory. I've found that most of all has helped me.

Its so much easier to just map it in Hammer 3.5, export to map, and plop your building or structure in. Add your displacements, entities, and textures and your ready to go.

I wish they'd do away with the whole steam tie-in stuff because it seems to be very in-efficient on a even a high-end pc.

well, i would just map it in 3.5 then transfer it over, but i cant make a sphere in 3.5 well... i can, but its alot more work. il try the defrag thing...

Originally posted by Watchtower
I wish they'd do away with the whole steam tie-in stuff because it seems to be very in-efficient on a even a high-end pc.

Hell yes, id consider my PC rather high end and its still chugs from time to time... I remember the first time i opened cbbl for cs:s in vhe and it took about 40 seconds to load then when i tried to buzz round in camera there was like a 5-10 second delay on movement.

We all know valve want to keep their software to HL2 product owners but running it thru steam is random.

my system is relatively high end (athlon 64 3400+, 1 gig ram, GF6800u) and it gets bogged down in source hammer now and then. if i have been using the system for a while, particularly for gaming, then do some mapping -or- just map for a while, then Hammer freezes for five seconds then unfreezes. when that happens i usually take a break.

remember to save your work often.

as for building in 3.5, you could do that, but it makes retexturing a pain sometimes. remember 3.5 default scale is 1.0 where 4.0 is .25. though for your particular issue with the clipping tool, that may be a temporary solution if you can't otherwise find one.

Originally posted by PanFrie
well, i would just map it in 3.5 then transfer it over, but i cant make a sphere in 3.5 well... i can, but its alot more work. il try the defrag thing...

your not trying to cut a sphere up with the clip tool by any chance? if so thats the problem right there, for some reason hammer will crash if you try to either use the clip tool on a sphere or use the vertex tool aswell.

Izuno, a direct imported .map from hammer 3.5 retains all texture coordinates and scaling. It will be however you left it in 3.5

So if you scale everything .25 in hammer 3.5, it will be so when you import it.

The importing method is really only useful for buildings or things you know you wont be editing much once its imported, so use as needed i guess. And yes you will have to retexture it but thats not a problem if you dont spend anytime texturing it beforehand.

id deffinately suggest looking into the resource strain side of things. It may be the case that you have to run minimal background processes in order to use hammer successfully on your system. Hassle - yes but it if solves your problem id run with it.