03-01-2023, 02:20 AM
(This post was last modified: 03-01-2023, 03:06 AM by Saeki Amae.)
@Lagertha
Ok, first of all, the project appliers button is active when you select a single project. Unselection of all projects (like you shown on the image) or selecting more than one project, will disable the button (Applier menu can work only with a single project active). You select projects by simply clicking on them :) Also click and hold or ctrl+click works in case you wanted to select more than one project (for example for multidae feature or multiexport).
Secondly: applier section = applier tab in the manual with instructions :D Project appliers button is for accessing applier menu :D
You can read about this in Introduction page, chapter about GUI (really i wonder why people don't read full manual first and just chosen chapters and then they feel lost :D)
Thirdly: make sure you actualy select proper project before clicking Dir: Copy/Open buttons - otherwise it may lead you to the folder of wrong project and thus you may find wrong or even no dae file at all.
Fourthly: you do not export the HUD :)
Because creators usually export single image of hud with invisible buttons that actually send data to the clothing, it is impossible to rip textures from the hud directly because all UUIDs stay in the script. The same case is in case of texture menus - they don't show images at all actually ^^. My tool works indirectly - you simply apply data to the mesh object from the hud, and then export the mesh object itsself. Then apply other data from hud, and again you export the same mesh object, just with textures (or other face parameters) changed. You can export any options (or even all options) from HUD this way and the program smartly recalculates them to find out their behaviour and reverse-engeneer the texture applier behaviour. About the details how it actually calculates i invite you to read about engines in the applier section of the manual. And then in order to switch textures you can use chat commands. I plan in the future to release special HUD that applies these commands for even easier tex applying (to get more touch-image-like interface rather than typing commands). I know that exporting XML of each texture option is slower than exporting just entire HUD at once but it is best option we actually have unless someone finds the way to hack scripts. And is still way faster than the methods before this program's existence. Really, appliers section says it all :) Read it (especially all 3 examples at the bottom of the section) and if you actually get lost in some point, then ask and I will help you to move forwards <3
Ok, first of all, the project appliers button is active when you select a single project. Unselection of all projects (like you shown on the image) or selecting more than one project, will disable the button (Applier menu can work only with a single project active). You select projects by simply clicking on them :) Also click and hold or ctrl+click works in case you wanted to select more than one project (for example for multidae feature or multiexport).
Secondly: applier section = applier tab in the manual with instructions :D Project appliers button is for accessing applier menu :D
You can read about this in Introduction page, chapter about GUI (really i wonder why people don't read full manual first and just chosen chapters and then they feel lost :D)
Thirdly: make sure you actualy select proper project before clicking Dir: Copy/Open buttons - otherwise it may lead you to the folder of wrong project and thus you may find wrong or even no dae file at all.
Fourthly: you do not export the HUD :)
Because creators usually export single image of hud with invisible buttons that actually send data to the clothing, it is impossible to rip textures from the hud directly because all UUIDs stay in the script. The same case is in case of texture menus - they don't show images at all actually ^^. My tool works indirectly - you simply apply data to the mesh object from the hud, and then export the mesh object itsself. Then apply other data from hud, and again you export the same mesh object, just with textures (or other face parameters) changed. You can export any options (or even all options) from HUD this way and the program smartly recalculates them to find out their behaviour and reverse-engeneer the texture applier behaviour. About the details how it actually calculates i invite you to read about engines in the applier section of the manual. And then in order to switch textures you can use chat commands. I plan in the future to release special HUD that applies these commands for even easier tex applying (to get more touch-image-like interface rather than typing commands). I know that exporting XML of each texture option is slower than exporting just entire HUD at once but it is best option we actually have unless someone finds the way to hack scripts. And is still way faster than the methods before this program's existence. Really, appliers section says it all :) Read it (especially all 3 examples at the bottom of the section) and if you actually get lost in some point, then ask and I will help you to move forwards <3