Modding:How To Find A Virtual Texture: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
===How to do it=== | ===How to do it=== | ||
First thing you need to find the item is its name. | First thing you need to find the item is its name. (If you don't know the name but it's on an NPC, it may be found in [PAK]_CharacterVisuals\_merged.lsf) | ||
Put the name in the modder's multitool. This should lead you to its entry in the english.loca file. | Put the name in the modder's multitool. This should lead you to its entry in the english.loca file. |
Revision as of 13:00, 2 January 2024
This tutorial requires Modder's Multitool, LSLib v19 and a knowledge of how to find things with the multitool.
How to do it
First thing you need to find the item is its name. (If you don't know the name but it's on an NPC, it may be found in [PAK]_CharacterVisuals\_merged.lsf)
Put the name in the modder's multitool. This should lead you to its entry in the english.loca file.
Take the handle and search that.
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.
Search the mesh name. You may need to append it with HUM_M_ as most of the gtex are under hum m arm meshes.
search gtex in that same file and you should start seeing applicable codes.
Lslib
Lslib v19 lets you unpack just specific gtp files via the gtex name.
Alternately you can just unpack all the VT into one folder, but this is extremely file intensive and not recommended.