You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yo, I imported the MotherShip model from Starcraft II, and I want to use it in Hots. There was no problems with the model itself, but with its textures. The edges are blue color (or red if the MotherShip is the enemy), the rest is all black.
I tried using "TextureSelectById" directly in "CActorUnit". However, without success.
Looking at other Units' code, I see examples like this:
However, where did Storm_Hero_Malthael_ come from and what does it even mean?
Using Brute Force I found a file named: CONTENT_KEY\8f\8fce0ec4eb50b45b61b938cea3d3fe38
There's a line in it.
Perhaps this is exactly what is the texture for the hero, but it also means that it can not be changed using TryMode2.0 without upgrading the files of the game itself?
The text was updated successfully, but these errors were encountered:
I decided to take a picture of the MotherShip. Hots recognized where the texture should be to differentiate the ally from the enemy, as it happens in Starcraft
Yo, I imported the MotherShip model from Starcraft II, and I want to use it in Hots. There was no problems with the model itself, but with its textures. The edges are blue color (or red if the MotherShip is the enemy), the rest is all black.
I tried using "TextureSelectById" directly in "CActorUnit". However, without success.
Looking at other Units' code, I see examples like this:
However, where did Storm_Hero_Malthael_ come from and what does it even mean?
Using Brute Force I found a file named: CONTENT_KEY\8f\8fce0ec4eb50b45b61b938cea3d3fe38
There's a line in it.
dds:64:64:1:7:7:0:storm_hero_malthael_base_diff.dds:1024:1024:1:11:7:0:storm_hero_malthael_base_norm.
Perhaps this is exactly what is the texture for the hero, but it also means that it can not be changed using TryMode2.0 without upgrading the files of the game itself?
The text was updated successfully, but these errors were encountered: