I've been working on large maps for many games such as Team Fortress 2.
But most of the time when the base of my map is finished ( Simple geometry , a lot of dev textures ) Hammer starts to freeze and crash alot making it very hard to work.
I have tried lowering draw distance however that didn't help much, and besides it even made working on maps a lot harder.
Is there a way to at least temporarily reduce freeze time and lower the chance of my hammer crashing ( No doubt it wont ever crash, this is Hammer ).
If you're asking I'm using NVDIA GeForce GTX 560 with 8 gigs of RAM.
Are you already using visgroups and the cordon tool ?
[url]https://www.youtube.com/watch?v=kEW_JIYEBAo[/url]
Could you post a compile log, if it takes a long time to compile then the map will need more optimising.
[QUOTE=FestiveSalmon;50912010]Are you already using visgroups and the cordon tool ?
[url]https://www.youtube.com/watch?v=kEW_JIYEBAo[/url][/QUOTE]
I dont use Visgroups too often since there's not alot of Func_details and other entity brushes.
I'f im working on a particular bulding/part of the map I hide most of the level to reduce lag.
[editline]19th August 2016[/editline]
[QUOTE=1 Duck;50912475]Could you post a compile log, if it takes a long time to compile then the map will need more optimising.[/QUOTE]
The map itself doesn't freeze and there's nothing wrong with compiling.
Hammer itself tends to lag and crash alot when I'm working
Ah sorry I misread. Cordon tool and Visgroups may be your saviour as FestiveSalmon suggested. You can make custom Visgroups. See if that helps at all. It generally helps me if I experience hammer lag.
Sorry, you need to Log In to post a reply to this thread.
