923
editsModding:How To Find A Virtual Texture: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
This should lead you to the ''roottemplate'' of the item. (if it doesnt have one in the roottemplate, it's in the parenttemplate's file instead) | This should lead you to the ''roottemplate'' of the item. (if it doesnt have one 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.(You can skip the above if you know the mesh name.) | You can then find its mesh mapkey. Search that and you should find the meshes lsx entry. (You can skip the above if you know the mesh name.) | ||
=== Finding the GTexFileName with the mesh name === | === Finding the GTexFileName with the mesh name === | ||
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 female specific meshes. 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. | 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 female specific meshes. 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. | ||