Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
tool build-cache-file "scenarios\multi\example" dx11_64 compress|resource_sharing|remastered_support
Or
tool build-cache-file "scenarios\multi\example" dx11_64 compress resource_sharing remastered_support
For example, took those from
https://c20.reclaimers.net/h2/tools/h2-ek/h2-tool/#build-cache-file
But I have a question, how do I compile a Halo 2 maps so that it has the anniversary and classic graphics?
I only see classic graphics when I compile the map and test it in MCC i cannot change them to anniversary
Tools like Reclaimer and Assembly were built AFTER the games released, by modders who only had the .map files to work with. The "mod tools" are to my knowledge used by the developers themselves to make new maps from scratch, not to modify existing ones. There is a world of difference in their intended use.
And as Nathan said; all the assets used within the campaign maps are available as asset files alongside the modding tools. These tools aren't lame, you're just missing the point of them entirely.