Difference between revisions of "Hammer Resource Usage"

From Valve Developer Community
Jump to: navigation, search
 
Line 1: Line 1:
 
[[Category:Hammer]][[Category:Level Design FAQ]]
 
[[Category:Hammer]][[Category:Level Design FAQ]]
 
{{otherlang2
 
{{otherlang2
| ru = Hammer Resource Usage:ru}}
+
| ru = Hammer Resource Usage:ru
 +
| ko = Hammer Resource Usage:ko
 +
}}
 
The [[Valve Hammer Editor]] uses lots of resources when loading models and textures, easily 400-500 megabytes when the full texture browser is loaded. This is not a bug or a "memory leak". Memory usage should plateau after that amount.
 
The [[Valve Hammer Editor]] uses lots of resources when loading models and textures, easily 400-500 megabytes when the full texture browser is loaded. This is not a bug or a "memory leak". Memory usage should plateau after that amount.
  
 
Usage of the model and texture browsers are the largest source of increased memory usage. When using these browsers, the application is forced to load a very large amount of raw source content.
 
Usage of the model and texture browsers are the largest source of increased memory usage. When using these browsers, the application is forced to load a very large amount of raw source content.

Latest revision as of 05:54, 4 August 2014

Русский 한국어

The Valve Hammer Editor uses lots of resources when loading models and textures, easily 400-500 megabytes when the full texture browser is loaded. This is not a bug or a "memory leak". Memory usage should plateau after that amount.

Usage of the model and texture browsers are the largest source of increased memory usage. When using these browsers, the application is forced to load a very large amount of raw source content.