Just bought a new desktop, was quite excited to see how much easier it was to work on hamemr with the extra power and to my amazement it ran like crap. I loaded up one of my maps and as I "flew" around it would stutter. I could work on the map just fine on my old crappy computer which only had a 2.0ghz single core, 1.5gb ram, and 7800 gtx.
This new computer has a 2.8ghz i5 (quad), 4gb DDR3, and gtx 460. So it shouldnt have any problems.
Could it be that hammer is a 32 bit application and I'm running windows 7 x64?
I just tried compiling the map to see how that ran and it would get to "Building physics collision Data" and then stop responding. All 4 cores would shoot up to 100% when this happens.
EDIT: Well I looked around and found out that the compile process IS NOT stopping. It is still going but the compile window freezes. I guess it is a windows 7 issue. Hammer is also running fine now. I reset game configurations and then reran hammer and it was better.
[QUOTE=S W;24841051]Just bought a new desktop, was quite excited to see how much easier it was to work on hamemr with the extra power and to my amazement it ran like crap. I loaded up one of my maps and as I "flew" around it would stutter. I could work on the map just fine on my old crappy computer which only had a 2.0ghz single core, 1.5gb ram, and 7800 gtx.
This new computer has a 2.8ghz i5 (quad), 4gb DDR3, and gtx 460. So it shouldnt have any problems.
Could it be that hammer is a 32 bit application and I'm running windows 7 x64?
I just tried compiling the map to see how that ran and it would get to "Building physics collision Data" and then stop responding. All 4 cores would shoot up to 100% when this happens.
EDIT: Well I looked around and found out that the compile process IS NOT stopping. It is still going but the compile window freezes. I guess it is a windows 7 issue. Hammer is also running fine now. I reset game configurations and then reran hammer and it was better.[/QUOTE]
Yes, I found that 64 bit was better... I was using 32 bit and it was crap I then I upgraded to 64 bit and found it was AMAZING I also have similar specs to your computer so I hope this helps.
[QUOTE=Ugrd;24846143]Yes, I found that 64 bit was better... I was using 32 bit and it was crap I then I upgraded to 64 bit and found it was AMAZING I also have similar specs to your computer so I hope this helps.[/QUOTE]
It depends on the specs of the computer, 64-bit primarily allows higher limits, such as removing the 3GB ram limit
Ive used a 32-bit Vista and 64-bit Server 2008 R2 on the same machine. No difference in performance, only performance potential.
[QUOTE=Ugrd;24846143]Yes, I found that 64 bit was better... I was using 32 bit and it was crap I then I upgraded to 64 bit and found it was AMAZING I also have similar specs to your computer so I hope this helps.[/QUOTE]
I'm pretty sure he was saying that [i]hammer[/i] was a 32 bit application. He's running a 64 bit OS.
yes nerdeboy is correct. I still find it unusual that the compile log freezes but I'm glad it works.
The compile log will always freeze. If you don't want it to use the VBCT.
[QUOTE=Firegod522;24850872]The compile log will always freeze. If you don't want it to use the VBCT.[/QUOTE]
Mine would freeze only if I clicked somthing, windows vista and 7 usually will think the program crashed. But to be sure if it creashed or not, use the processes tab on Task Manager.
I'm running 64 bit and no problems here.
But I also have 12Gb ram, I7 core, and a nvidia 295 gtx.
[QUOTE=Firegod522;24850872]The compile log will always freeze. If you don't want it to use the VBCT.[/QUOTE]
Mine never freezes. Running Win Xp on 2 machines, an intel P4 3.8GHz, 2 gig RAM and a 2.7GHz i5, 4 Gigi RAM, both fine with the standard compile tools.
My compile used to freeze upon key press / clicking anywhere when I was on Vista, but after a switch to Server 2008 R2 I never had a problem with it unless doing too much while compiling.
Sorry, you need to Log In to post a reply to this thread.
