Hammer Resource Usage: Difference between revisions
Jump to navigation
Jump to search
(FAQ item for Hammer resource consumption) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
[[Category: | [[Category:Level Design FAQ]] | ||
The 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 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. | ||
Revision as of 20:19, 21 January 2006
The 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.