Source 2/Docs/Porting Legacy Content: Difference between revisions
mNo edit summary |
m (Nesciuse moved page Source 2/Docs/Porting Legacy Content/en to Source 2/Docs/Porting Legacy Content without leaving a redirect: Move en subpage to basepage) |
||
| (16 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{LanguageBar}} | ||
Source 1 models, materials, maps, and all of it's content is completely different to how Source 2 handles the same files. These files are now unsupported, but with some built-in tools and some know-how, you can learn to import Source content to Source 2. | {{Source 2 topicon}} | ||
{{Source|3.1|nt=3}} models, materials, maps, and all of it's content is completely different to how {{Source 2|3.1}} handles the same files. These files are now unsupported, but with some built-in tools and some know-how, you can learn to import {{Source|3.1}} content to {{Source 2|3.1}}. | |||
== Some Context and Preamble == | == Some Context and Preamble == | ||
Source 2 uses new file formats for it's content. Maps are now | {{Source 2|1}} uses new file formats for it's content. Maps are now {{Ext|vmap}} instead of {{Ext|vmf}}, materials are now {{Ext|vmat}} instead of {{Ext|vmt}}, models are now {{Ext|vmdl}} instead of {{Ext|mdl}}. See the pattern yet? Almost every file used in {{Source|1|nt=3}} is now some form of {{Code|.v___}}. Some of them haven't changed much, like {{Ext|vcfg}} files are just old-school {{Ext|cfg}} files from {{Source|1|nt=3}} renamed. But what is unique about these files is that for models, maps, materials, sounds, etc. they all use a compiled version of said file. | ||
Take for instance the .vmat file. If you open a .vmat file inside of your 'Half-Life Alyx/content' directory, it will be in plain-text and can be edited. However, find that same material in 'Half-Life Alyx/game' and it will become a | Take for instance the .vmat file. If you open a .vmat file inside of your 'Half-Life Alyx/content' directory, it will be in plain-text and can be edited. However, find that same material in 'Half-Life Alyx/game' and it will become a {{Ext|vmat_c}} file. Think of {{Ext|vmat}} as just a plain-text version of {{Ext|vmat_c}}, which is the real material file loaded by the engine. So, if you're making new content or have the sources of the {{Source|1|nt=3}} content, you should probably just convert your content using the regular paths, as it's much easier to retain your ideal look with the new GUI tools {{Source 2|1}} offers. | ||
== Guides For Converting Content == | == Guides For Converting Content == | ||
The Counter-Strike 2 Workshop Tools come bundled with a map importing script, which uses various tools behind the scenes to import legacy content. | |||
Source2Converter builds off of SourceIO and allows mass porting for models and their textures. | Source2Converter builds off of SourceIO and allows mass porting for models and their textures. | ||
* [https://github.com/REDxEYE/Source2Converter REDxEYE's Source2Converter] | * [https://github.com/REDxEYE/Source2Converter REDxEYE's Source2Converter] | ||
You can also port from Source 1 using these methods | You can also port from Source 1 using these methods | ||
* [[ | * [[{{ROOTPAGENAME}}/Docs/Porting Legacy Content/Models|Importing .MDL Files]] | ||
* [[ | * [[{{ROOTPAGENAME}}/Docs/Porting Legacy Content/Materials|Converting .VMT to .VMAT Files]] | ||
* [[ | * [[{{ROOTPAGENAME}}/Docs/Porting Legacy Content/Maps|Importing .VMF Files]] | ||
If you'd like to port over your own content to Source 2, modeling and material creation guides are here: | If you'd like to port over your own content to {{Source 2|1}}, modeling and material creation guides are here: | ||
* [[Half-Life: | * [[Half-Life: Alyx Workshop Tools/Modeling|Modeling and Using ModelDoc]] | ||
* [[ | * [[Dota 2 Workshop Tools/Materials|Materials in Dota 2 (still applicable to HL:A)]] | ||
[[Category:Source 2]] | [[Category:Source 2]] | ||
Latest revision as of 11:03, 12 July 2024
Source 1 models, materials, maps, and all of it's content is completely different to how Source 2 handles the same files. These files are now unsupported, but with some built-in tools and some know-how, you can learn to import Source content to Source 2.
Some Context and Preamble
Source 2 uses new file formats for it's content. Maps are now .vmap instead of .vmf, materials are now .vmat instead of .vmt, models are now .vmdl instead of .mdl. See the pattern yet? Almost every file used in Source 1 is now some form of .v___. Some of them haven't changed much, like .vcfg files are just old-school .cfg files from Source 1 renamed. But what is unique about these files is that for models, maps, materials, sounds, etc. they all use a compiled version of said file.
Take for instance the .vmat file. If you open a .vmat file inside of your 'Half-Life Alyx/content' directory, it will be in plain-text and can be edited. However, find that same material in 'Half-Life Alyx/game' and it will become a .vmat_c file. Think of .vmat as just a plain-text version of .vmat_c, which is the real material file loaded by the engine. So, if you're making new content or have the sources of the Source 1 content, you should probably just convert your content using the regular paths, as it's much easier to retain your ideal look with the new GUI tools Source 2 offers.
Guides For Converting Content
The Counter-Strike 2 Workshop Tools come bundled with a map importing script, which uses various tools behind the scenes to import legacy content.
Source2Converter builds off of SourceIO and allows mass porting for models and their textures.
You can also port from Source 1 using these methods
If you'd like to port over your own content to Source 2, modeling and material creation guides are here: