Hammer Compile Freezes: Difference between revisions
Jump to navigation
Jump to search
m (categorize) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{otherlang2 | |||
|ru=Hammer Compile Freezes:ru | |||
}} | |||
[[Category:Hammer]][[Category:Level Design FAQ]] | [[Category:Hammer]][[Category:Level Design FAQ]] | ||
The compile has likely not actually frozen, it's actually just taking a very long time for your map to compile. Although complex maps can often take a long time to compile fully, this is usually the sign of an poorly optimized map. In general, long [[Vvis]] compile times are much easier to reduce than [[Vrad]]. | The compile has likely not actually frozen, it's actually just taking a very long time for your map to compile. Although complex maps can often take a long time to compile fully, this is usually the sign of an poorly optimized map. In general, long [[Vvis]] compile times are much easier to reduce than [[Vrad]]. | ||
See [[Controlling Geometry Visibility and Compile Times]] for suggestions of ways to optimize your map and decrease compile times. | See [[Controlling Geometry Visibility and Compile Times]] for suggestions of ways to optimize your map and decrease compile times. | ||
Revision as of 14:23, 1 June 2011
Template:Otherlang2 The compile has likely not actually frozen, it's actually just taking a very long time for your map to compile. Although complex maps can often take a long time to compile fully, this is usually the sign of an poorly optimized map. In general, long Vvis compile times are much easier to reduce than Vrad.
See Controlling Geometry Visibility and Compile Times for suggestions of ways to optimize your map and decrease compile times.