It worked before 3.0 and I am not the only one this issue. The model has its texture designated into "Root" (aka to no folders). It might be that I need to change it to Assets/Texture in the model and then move the texture to Assets/Texture to fix it.
Ah, I see. Are the textures .tga? TGA's appear to no longer be supported. You can fix this by converting each TGA to .dds (you can do this in GIMP with a plugin), and reverting the file extension back to .tga (sometexture.dds > sometexture.tga). The editor will yell at you, but the model can still apply the texture just fine.
So we've identified the issue with the War3 data mod and we're looking into ways of fixing it so it's usable again. I don't have an ETA at this time but I'll update you all again when I know more.
After 3.0 I can no longer sell items in a shop. Attempting to do it would bring up an error sound and the alert "Can't pawn that." Has anyone else had this problem?
I can't even debug this as I have no idea what requirement/validator is raising the error. I found the text ID to be "e_cmdCantPawnThisUnit." Is there any way I can use that to search for the issue?
So we've identified the issue with the War3 data mod and we're looking into ways of fixing it so it's usable again. I don't have an ETA at this time but I'll update you all again when I know more.
Seems to be back, for now
Is it just me or is creep/blight not working for it though?
When my units are not turning or moving, their attached weapons break off and just hang in the air. However, if the unit is turning or moving, the attached weapon works fine....
Thanks for the update! Hope someone with more technical knowledge of the editor sees this thread as well, we want to help you all there at blizzard identify problems so work can be done on our end :D
I have framerate cap set to 60 in Variables.txt to lower the GPU heat, but with this patch it doesn't matter what value i put behind the "frameratecap" it always capping it to 50. I know that my monitor got higher than that, so why is this happening? The game also runs a little bit slower when this turned on. Anyone got that issue?
This is a completely unmodified UI using a unit with a veterancy behavior. The weapon icon should be displayed, but is not. This happens with any weapon, including ones made by Blizzard.
Ah, I see. Are the textures .tga? TGA's appear to no longer be supported. You can fix this by converting each TGA to .dds (you can do this in GIMP with a plugin), and reverting the file extension back to .tga (sometexture.dds > sometexture.tga). The editor will yell at you, but the model can still apply the texture just fine.
Nope, they are dds textures, now I even tried different DXT compressions and dds with mipmaps, but those too didnt work.
I really have now the feeling that all kind of textures must be in Assets/Textures to work, but I am lazy to change model's texture paths.
pitfall: Send transmission and send transmission (advanced) are no longer available in trigger listing of functions. It will still work in old maps that have it though.
Solution: copy/paste the function from old maps.
I don't understand why they would hide/get rid of those. The simple and campaign versions are for those specially made ones with sounds n such. Or is there a way to use them? If so I imagine you have to go into data which makes it needlessly more complex to make transmissions.
This is a completely unmodified UI using a unit with a veterancy behavior. The weapon icon should be displayed, but is not. This happens with any weapon, including ones made by Blizzard.
I don't have a solution for this.
Override the hero atk frame could work. I've already fixed it in the war3 mod.
I have textures in the import root folder and still work. Some have found deleting and reimporting all textures (and/or the model) has fixed the issue.
Pitfall: I get the trigger error "TextError: Text [0] is too tall for a single line. Exceeds by [4]". I get this during editor play testing and the odd thing is it doesn't happen all the time. When it does, it's at map start.
Solution: I don't have a solution for this yet.
Increase the labels height by 4 to fix the problem. Its a new warnign added for labels that are too small to store their text value properly. You need to figure out which label it is by yourself though. :) In your case, it has something to do with the text "0".
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
@greythepirate: Go
It worked before 3.0 and I am not the only one this issue. The model has its texture designated into "Root" (aka to no folders). It might be that I need to change it to Assets/Texture in the model and then move the texture to Assets/Texture to fix it.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium@Hookah604: Go
Ah, I see. Are the textures .tga? TGA's appear to no longer be supported. You can fix this by converting each TGA to .dds (you can do this in GIMP with a plugin), and reverting the file extension back to .tga (sometexture.dds > sometexture.tga). The editor will yell at you, but the model can still apply the texture just fine.
@PirateArcade | I make games | Ask me things on Discord
So we've identified the issue with the War3 data mod and we're looking into ways of fixing it so it's usable again. I don't have an ETA at this time but I'll update you all again when I know more.
After 3.0 I can no longer sell items in a shop. Attempting to do it would bring up an error sound and the alert "Can't pawn that." Has anyone else had this problem?
I can't even debug this as I have no idea what requirement/validator is raising the error. I found the text ID to be "e_cmdCantPawnThisUnit." Is there any way I can use that to search for the issue?
@Dorkles: Go For items you are trying to sell, enable the Pawnable flag. It is found in the Unit flags.
All the items already have that flagged. The shop was working fine before this patch.
Seems to be back, for now
Is it just me or is creep/blight not working for it though?
You're right, thanks! It was the wc3 data mod :(
rewritten in later post
Anyone else have their attachments break?
When my units are not turning or moving, their attached weapons break off and just hang in the air. However, if the unit is turning or moving, the attached weapon works fine....
(This is with WoW models)
The War3 mod should be back up for everyone.
In Map Menu, Map Options ... List of options at bottom, check appropriate option http://i.imgur.com/HUC5ErH.png
@Traysent: Go
Thanks for the update! Hope someone with more technical knowledge of the editor sees this thread as well, we want to help you all there at blizzard identify problems so work can be done on our end :D
I have framerate cap set to 60 in Variables.txt to lower the GPU heat, but with this patch it doesn't matter what value i put behind the "frameratecap" it always capping it to 50. I know that my monitor got higher than that, so why is this happening? The game also runs a little bit slower when this turned on. Anyone got that issue?
Hero weapon icons are no longer being displayed.
This is a completely unmodified UI using a unit with a veterancy behavior. The weapon icon should be displayed, but is not. This happens with any weapon, including ones made by Blizzard.
I don't have a solution for this.
Nope, they are dds textures, now I even tried different DXT compressions and dds with mipmaps, but those too didnt work.
I really have now the feeling that all kind of textures must be in Assets/Textures to work, but I am lazy to change model's texture paths.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumpitfall: Send transmission and send transmission (advanced) are no longer available in trigger listing of functions. It will still work in old maps that have it though.
Solution: copy/paste the function from old maps.
I don't understand why they would hide/get rid of those. The simple and campaign versions are for those specially made ones with sounds n such. Or is there a way to use them? If so I imagine you have to go into data which makes it needlessly more complex to make transmissions.
Override the hero atk frame could work. I've already fixed it in the war3 mod.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium@Hookah604: Go
I have textures in the import root folder and still work. Some have found deleting and reimporting all textures (and/or the model) has fixed the issue.
@PirateArcade | I make games | Ask me things on Discord
Increase the labels height by 4 to fix the problem. Its a new warnign added for labels that are too small to store their text value properly. You need to figure out which label it is by yourself though. :) In your case, it has something to do with the text "0".