- Joined
- Jun 27, 2010
- Messages
- 4,183
non-reforged wc3 doesnt use .dds image, convert to blp
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
That's a myth. Normal SD graphics are fully compatible with .dds format, except on older patchesnon-reforged wc3 doesnt use .dds image, convert to blp
That's true, I can confirm that.That's a myth. Normal SD graphics are fully compatible with .dds format, except on older patches
You should've asked for my permission before altering my asset, but fair enough. No biggieHere's the myth all completed so everyone else can use this great asset too.
do you have discord? I can explain you with screenshots how it works in a DM if you wantI didn't understand how to use it, but it looks great in the screenshots. xD
I'm sorry but I edit my textures with Photoshop and use GIMP for file conversion. I personally exclusively work with .dds files, because they work universally for both SD and HD which is very convenient to me, especially for universal models like this. I didn't start modeling/texturing until after reforged dropped so I never learned it any other way. I've never worked with .blp and would probably mess up the texture and rendering and I have no knowledge or desire to fix it.convert the texture to blp to be comatible with older patches of classic
Review accepted by Footman16
you are in the SD section, it must be compatible with classic as well. You can use BLP Lab v0.5.0 to convertI'm sorry but I edit my textures with Photoshop and use GIMP for file conversion. I personally exclusively work with .dds files, because they work universally for both SD and HD which is very convenient to me, especially for universal models like this. I didn't start modeling/texturing until after reforged dropped so I never learned it any other way. I've never worked with .blp and would probably mess up the texture and rendering and I have no knowledge or desire to fix it.
I've also never worked with any older patches since Reforged came out. This model is made in the Reforged era to be compatible with Reforged, so it seems silly to me to unapprove my model just because of personal preference and because some minority running old patches can't use it. That's like as if you unapprove an SD model from 2008 for being incompatible with HD graphics or something.
If people who want to use this on older patches, they are free to fix it for themselves, but I'm not going to.

Technically, the rules only mention the type of .dds for Reforged models. There is no explicit mention of .blp for Classic ones.you are in the SD section, it must be compatible with classic as well. You can use BLP Lab v0.5.0 to convert
That's not how things work, I would advise against refusing co-operation.If people want to use this on older patches, they are free to fix it for themselves, but I'm not going to.
I think this might be the best solution and would just circumvent the entire non-arguement with the .dds/.blpi question why custom texture is even necessary here
here it is with Textures\GenericGlow64.blp, additive filtering and 0.25 alpha, in-game 255/255/255 tinting, scaled up to 5
you can even make several versions by changing the alpha's intensity instead of having one that's barely noticeable
View attachment 597403
if there is some issue with additive filtering that i'm not aware of, you can try using Textures\GenericGlow1.blp with blend filtering and less than 1 alpha
if you use blizzard textures then you won't have to convert anything yourself too, just have versions with .dds for reforged and .blp for normal warcraft
That should work two ways, meaning for the users too if they need it if it's that easy and since the rules don't specify it but for some reason it is enforced.There's no debate here, it should be .blp for compatibility. It takes 2 seconds.
You are right, there is no rule or guideline for that.That should work two ways, meaning for the users too if they need it if it's that easy and since the rules don't specify it but for some reason it is enforced.
You can't blame me for this, I have no idea how blp works as I didn't start modeling until abouts 2021, also never worked with older patches. I guess at least some people running legacy or whatever can use it now, but I won't be providing bug fixes or support for any issues with this legacy variant, though.View attachment 597425
Left: DDS
Right: BLP
I don't agree with the Hive catering exclusively to players playing on the latest version, so here you go:
(p.s., this literally took me less than 2 minutes to do. If we cannot ask of this basic principle of our modellers, we have a problem lol)
It's an image format.You can't blame me for this, I have no idea how blp works as I didn't start modeling until abouts 2021, also never worked with older patches. I guess at least some people running legacy or whatever can use it now, but I won't be providing bug fixes or support for any issues with this legacy variant, though.
If this is such a big deal to everyone why not make it an official site rule and put a required "Insert Legacy variant/BLP" on the upload page for SD models? Such a hassle to backpedal on this, I don't want to throw some random .exe file from 2009 on my PC just to crap a file that's useless to me anyway. Or add a .dds/.png to .BLP coverter on the site under the "Utility" tab? Idk this whole thing feels archaic to me.
i think BLP is de facto standard for textures in SD war3 and it's a fact that older 3d modelling app like wa3ME 1.07 and MDLVIS and War3Tuner cant read DDS. So if a reviewer is inspecting a model he has to use RMS or the newer War3ME. So it's also about third party tools compatibility.I set it back to pending - perhaps a bit quick. I will sit down with @Archian tonight and talk this over. Initially I think the decision about backwards compatibility should be up to the author, but I can see the benefits of requiring BLP as well for legacy-compatible things.
A thought. MDX1200 format and earlier are not legacy compatible anyway, so should people be prevented from using those too for SD? I think that is kind of too strict. And if stan Sapprine happens to be using a recent MDX format, will be also be asked to use an older one?
There is no reason to save your model in MDX1200 format instead of MDX900 for SD anyway, is there?A thought. MDX1200 format and earlier are not legacy compatible anyway, so should people be prevented from using those too for SD? I think that is kind of too strict. And if stan Sapprine happens to be using a recent MDX format, will be also be asked to use an older one?
It would be MDX800, but no, there ain't.There is no reason to save your model in MDX1200 format instead of MDX900 for SD anyway, is there?


