Lol, I feel like a bad member now
Well, that quite unmotivated me

HAWTNESS

JUU ARE AWESOME!

It says that the module may not be compatible with my x86 or x64 thingy.
What the fux?
I tried the three solutions there.
D:

Figure out what operating system you have and what architecture (32-bit, 64-bit) and google comdlg32.ocx and your OS.

64 bit.
I have downloaded comdlg32.ocx and tried to put in every folder Corbo said to.
I registered it too.
Nothing works.

... Which is why I said google it.

Updated for SC2 retail ... finally.

OH DEAR GOD FINALLY.

I have a few questions,

What's the ordering of the layers themselves? Does it just go like Layer 1 = base Layer 2 = first texture added, layer 3 = second texture added... and so on? or does the engine have different textures assigned to each layer?

Would it be possible for you to add a "make unused" button and completely delete the mask... meaning making it unused. I've found out that even if you "mistakenly" add a texture and even if you undo to complete deletion of it it will still keep the layer, completely black, of course, but that should increase the filesize, right? Which is a bad thing for something we're not actually using.

If the "t3texturemap" determines the layers order, would it be possible for you to make this program also able to "order" the layers? Meaning that I want certain layer to be on top of another, for that matter, meaning like this I've painted a dirt spot (Layer 2) then I painted a grass on top of it with a lower strenght on the editor so I could still see the dirt (layer 3) then on top of that I painted a rocky texture, with not complete opacity, meaning I could still see the grass, but not the dirt. (layer 4) Would it be possible for you to make this program such that you could rearrange that order, meaning, I want the layer 2(dirt) to now be "on top" of the grass and grass (layer 3) inmidiately after the default base (layer one). Meaning that I want to make layer 2 into 3 and 3 into 2 or are the texture references to each layer not pointed by the t3texturemask? It wouldn't be much of a mask swapping but rather a "assign the other one's texture to another layer" kind of thing.

Is 2048 by default the max size of the layers? Can you make them bigger for much more detailing?

What happens if I give a mask to one of these unuseds? what texture does it use?

Would it be possible to use more than 8 textures, in theory, if you could assign more layers and assign those layers to a texture reference? Where are the textures for each layer referenced anyway?

EDIT: I just realised that the masks aren't really building an opacity mask but rather all 8 masks seem to be of an "absolute" value meaning that if I merged all textures together I'd get a completely white mask, right? That kinda invalidates questions 1 and 3 but I'll wait for your answer.
I thought the masks all had values sorta like an opacity mask in which all of them can have ranges from black to white but this seems to be more of a if you have 100% ammount (white) in a mask you will NOT have 100% in another mask, but rather in all other layer masks it'll be 0%, however you can have mixed values like 50% in one and 50% in another mask so the two masks "blend" and build up to a total of 100% but never 100% in more than one mask. Which simply sucks completely makes what I'm doing almost impossible, if not impossible already and quite honestly this is just simply innefficient This means that you don't actually have 8 textures blended but rather you just have one...
Upon actually testing it it seems that you CAN actually have more than one mask with 100% "ammount" except that they'll act as 50% opaque which is just funny disregard my first edit, questions still remain.

Figured as much it was easier for me to post rather than ask you as they were long questions and you weren't online anyway

Post has been edited 2 time(s), last time on Oct 16 2011, 6:08 am by BossGT10.

I haven't really tested the limits and variability of the format ...

I haven't used the sc2 editor in a while and I haven't updated SC2 recently so I can't really look at specifically where, but wherever you define what textures the map uses is the order that these exist in. (also see a couple blocks down...)

All 8 layers always exist in the file. I haven't played around to see what happens if some don't exist.

t3texturemasks (or whatever, the name is a variable) does not. t3terrain does, and t3texturemasks uses this order:


I don't think so, but I haven't tried loading wrong-sized images.

None.

8 textures is hardcoded. I've tried playing with this (adding entries to textureList, etc.) and t3texturemasks seems to always (and only) have 8 textures.

Should I just... try? or do I need to be a god and change something so I can import an oddly sized mask?

Sucks.

Thanks

Only problem with it is that some pictures don't translate well to the map epically pictures that are intricate.

Did you ever update this to newer formats?

Any chance of you making it for t3heightmap too?

I haven't played with the sc2 data files in a long time ... xD I could check them out again.

I think the problem I had with t3heightmap was that each value is a 16-bit number, which creates either depth problem (limiting to an 8-bit number) or makes it more difficult to edit (image editors that support 16-bit greyscale).