Modding:How To Find A Virtual Texture: Difference between revisions

}}{{Modding box}}{{Modding sidebar}}

You may also find [https://docs.google.com/spreadsheets/d/135XWkGCZ1A7hn4yW1Gt3i7MGfx-RsgKfLPGbHdXKbNg/edit?usp=sharing this spreadsheet] helpful.

===How to find the mesh name===

You can skip this step if you know the mesh name. The wiki has many item pages with the File names included. [[The Deathstalker Mantle]], for example.  

* Take the '''handle''' (a handle is h[string of numbers], similar to an UUID) and search that. For example, The Deathstalker Mantle's handle is ''hb7ee75e7g15f1g42a7gacf3gafe7628d8b10''. This should lead you to the ''RootTemplate'' of the item. (If it doesn't have an entry in the RootTemplate, it's in the ParentTemplate's file instead.)

* You can then find its mesh '''mapkey'''. Search that and you should find the meshes lsx entry, which will lead you to the mesh name. For example, The Deathstalker Mantle's mesh name is ''UNI_DarkUrge_Bhaal_Cloak''.  

You will need to find the GTexFileName in order to find the correct virtual texture to extract. So search the mesh name in the search index in Multitool.

You may need to append it with HUM_M_ instead of whatever race you are looking for, as '''most of the universal gtex are under HUM M meshes.''' The same applies with HUM F and meshes that are different on the female to the male.  

Some meshes also share textures with other versions of the mesh, so you may need to remove the ''_a'' or ''_broken'' (for example) appendage if you aren't getting any matches.

For example, we like ''''HUM_M_ARM_Bandit_C_Body'''<nowiki/>' so we search this in the multitool.

It has an entry in '''<nowiki/>'Shared\Public\Shared\Content\Assets\Characters\Humans\[PAK]_Male_Armor\_merged.lsf''<nowiki/>' ''''' so we click ''convert & open'' for that.

      '''<attribute id="MaterialID" type="FixedString" value="57a6fd6e-c00d-60eb-5e52-31560b95332b" />''' <!-- This is the material ID -->

This material ID (57a6fd6e-c00d-60eb-5e52-31560b95332b) is what we need. We scroll back up to the very start of the '''_merged.lsf '''(materials are usually near the top) and CTRL+F for that.

We find:

We scroll down to the end of the material, past the vector parameters and we find the VirtualTextureParameters ID:

So we search d53fa1a1-aa8e-2564-1077-42f6c36086c5. Luckily for us, it is in the same file. (If it isn't, you may need to search the multitool for it.)

The GTexFileName, b049a62336641c449903f6ec8b4dae67, is the correct string. Now you can extract it from the virtual textures.

Now that you have your GTexFileName, you can extract the textures from VT. Search your GTexFileName (in this case: b049a62336641c449903f6ec8b4dae67) in the multitool. Select the file that's inside VirtualTextures and click on the Extract file icon.

Here are the three texture files you will need, in .dds format. The red underlined one is the PM (Physical Map), the green underlined one is the NM (Normal Map), and the purple underlined one is the (BM) Base Map. The PM is usually brighter colors, the NM is usually almost all blue, and the BM is usually very light with a sort of beige tone. We recommend copying all of these to your project folder and renaming them with the mesh name + _BM, _NM, or _PM, so it's easier to keep track of them later.