@hobbidude: Go He doesn't mean that. He means retexturing a model using TextureSelectById method.
@Kabelkorven: Go One thing I know is TextureSelectById got a little more picky after WoL/HoTS big patch. I'm sure there's a thread around covering that.
@Kabelkorven: Go One thing I know is TextureSelectById got a little more picky after WoL/HoTS big patch. I'm sure there's a thread around covering that.
Didn't notice any problems with that... =/
You need a prefix since 1.5, though...
It works if I follow the instructions I already sent you via PM. You seem to have mixed up the field names, in particular you still haven't fixed the Slot names on any of the Model objects.
Select the Oracle Model data object and open up the Texture Declarations+ field
Select the first Adaption entry. Change the Trigger On Substring field from "_diffuse" to "_Diff". Add ".diffuse" to the Slot field, so it reads "main.diffuse"
Select the second Adaption entry. Change the Trigger On Substring field from "_specular" to "_spec". Add ".specular" to the Slot field, so it reads "main.specular"
Select the third Adaption entry. Change the Trigger On Substring field from "_emissive" to "_emis". Add ".emissive" to the Slot field, so it reads "main.emissive"
The Trigger On Substring field names are derived from the model asset's Materials (Cutscene Module, Shift+D), the Slot names are what you set on the Texture data objects.
Note that your setup won't work for units placed in the editor, and possibly those constructed by a Build ability too. You should use ActorCreation as the trigger for applying the textures unless you encounter a problem with that.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
In WoL I import skins and use the TextureSelectByID method. It usually works. When I import textures for a HoTS model, the same method does not work.
How do you do when you import skins for HoTS models?
For example: http://www.sc2mapster.com/assets/dark-protoss/images/147-khalai-oracle/
You can't; importing hots content into wol will earn you a one way ban.
Yeah I know, I import a HoTS skin into HoTS.
@hobbidude: Go He doesn't mean that. He means retexturing a model using TextureSelectById method.
@Kabelkorven: Go One thing I know is TextureSelectById got a little more picky after WoL/HoTS big patch. I'm sure there's a thread around covering that.
Didn't notice any problems with that... =/
You need a prefix since 1.5, though...
I haven't had any issues replacing textures since HotS. Make sure all you have the proper prefixes set up with the underscore included.
Administrator of Staredit.net and GalaxyWiki.net
The imported Oracle skin refuses to work. Would anyone mind to take a look?
(Note that I've managed to get the imported Stalker skin to work.)
It works if I follow the instructions I already sent you via PM. You seem to have mixed up the field names, in particular you still haven't fixed the Slot names on any of the Model objects.
Select the Oracle Model data object and open up the Texture Declarations+ field
The Trigger On Substring field names are derived from the model asset's Materials (Cutscene Module, Shift+D), the Slot names are what you set on the Texture data objects.
Note that your setup won't work for units placed in the editor, and possibly those constructed by a Build ability too. You should use ActorCreation as the trigger for applying the textures unless you encounter a problem with that.