Woa! What a large sloppy code for slicing :) The program is slicing/edging ok, I think, but I have to do a heavy test of it. It works ok with the basic_curve 60x60 block and I can't see a reason for it to fail on other resolutions. Only the automatic discard is lefting, and it is much easier than ...

Is good to hear all that :)

A couple of minor things comes to my mind right now...

-The program is a MDI application, so multiple editors can be opened at same into the application workspace.

-The program, as you can see in the first screenshot, is named "Texture Tool for MTM and MTM2", not ...

I want to change the word "streak" by "extend".

English is not my main language so I want to know your opinion.

I think "Swap/Extend" are more meaningful than "Wrap/Streak".

-When slicing 60/240 blocks, the user must choose between "swap/extend". One or the other will be used to fill the edges ...

In fact there is no limit, only your system resources, of course. I'm considering a max of 256 blocks, and 256x256 tiles per block. In the case of 256x256 pixel tiles... we are talking of 64K*64K*256 bytes size, which is 1 GB. Setting that limit we are dealing with the max amount of system resources ...

Here you can see how tiles are manually discarded using the "Discard Tile" popup menu.

<img src=http://personal.telefonica.terra.es/web/nanobot/scrprg04.jpg>

Also, I gave priority to "Save Unique Repetitions" since you told me it will be more frecuent. It is the default action now for automatic ...

Yes, I was sure it is not always about terrain textures. What I really wanted to know is what slice60 does instead of wrapping... thx, Phineus, for telling me the concept of "streaking". I would have tested Slice60 by myself and check the results, but it's faster to ask here... hehe :p Ok, I'll ...

These are screenshots of the program. I can change anything you want so don't cry if you don't see what you want, just let me know.


First of all, the user goes to the menu and selects "Open Texture Block in Slice Editor":

<img src=http://personal.telefonica.terra.es/web/nanobot/scrprg01.jpg ...

At least, the program will generate a log file containing all names and stuff everytime you slice.

Talking about Slice60...what sense does it make to turn it off the wrap internal edges feature? The edges of the final 64x64 tiles must be filled with something... what sense does it makes to leave ...

Please tell me more about .txp files. I learn fast but there are lots of things I'm still missing, talking about mtm2 in general.

lol the darn Guest is me :)

Heh, thx, Phineus. I also think they will be useful tools. For now, I'll be working in the slicer/edger. The 1st beta version will be linked here as soon as I have it tested. A few days will be enough.

If somebody have any suggestions he should speak soon because I'm already coding, and I *hate ...

Yes, absolutely that's what I meant. It is not really hard... just reading pixels from each images and placing them in the right positions of the final tile collection. I have to think more about it but I'm pretty sure of what I'm saying. The user will have some parameters to tweak so different ...

I agree with you, now that I know what it is about. Even if the use of 256ers has severe limitations we still need a 256 slicer/edger. I already started coding it.

Next thing will be a tool to automate transitions, taking two 60x60 or 240x240 seamless textures and generating the whole set of ...

hmmm... I don't understand some things. You mean a tile which is always seamless no matter what sides are in touch? dern... I still don't understand lol

I understand what rotation is and I have played with it in Traxx, I understand that using rotated textures can reduce the amount of textures ...

Ok. Thanks to rocketalces for the 64 maximum. 256 textures are 64 KB long. 64KB x 64 = 4MB. It was normal to assume that limitation when the game engine was developed. Now, my video card has 128 MB of fast-like-hell memory, and my system mem is 512 GB of fast DDR RAM, and it's not the best PC ...

Ok. The first thing that comes to my mind is about graph formats. This is what I think:

-The program will accept 8 bit BMPs or RAW/ACT files containing blocks and it will generate collections of single RAW/ACT pairs secuentialy named with a prefix given by the user.

-It will work with both 64 and ...

I just read a lot of interesting things in the links of above... like ususal on this forum :)
I'll try to assimilate it all before start spreading my newb opinions...

But there's one thing I want to ask now.
I've read about the need of a 256 slicer. I guess slice is not currently a problem with ...

Yes, it was lag the thing I was afraid of when I posted this. Is not easy to make my computer lag with mtm2, but I guess other ppl are used to it. The first time I saw mtm2 it was almost unplayable due to lag on that computer.

A simple testing of massive using of 256 textures is easy to do ...

By the way... is good to be new with ppl like Phineus around.

When using 256 textures I'll take care for the pod file size not to be very large. 256 texturs are 16 times bigger than 64 ones. I hope it won't be a problem. If it is then I'll mix 256 and 64 textures. Right?

Thank you Phineus, that's what I wanted to hear. 256 textures looks much better so I'll use them as much as I can. These are screenshot samples of 256 textures I'm working on:

http://personal.telefonica.terra.es/web/nanobot/screenshot.jpg
http://personal.telefonica.terra.es/web/nanobot/screenshot2 ...