TileCutter 0.3d.1

[Timothy]

TileCutter v.0.3d.1

For helpful information on using TileCutter, please see its page on the Simutrans Wiki.

Download:
>> TileCutter-v0.3d.zip << - 0.3d Main package
>> TileCutter-v0.3d.1-Binary.zip << - 0.3d.1 Binary

(You need to download both the above things, then replace TileCutter.exe in the 0.3d package with the TileCutter.exe from the 0.3d.1 zip. This is to save you having to re-download a 7meg zip file )

This version brings some new features and fixes a couple of bugs I noticed while working on them. Hopefully now the translation system ought to work fairly well (new format for the translation files though, template is attached). The plan is to use SimuTranslator for the translation. This also brings updates pertaining to climates (winter buildings will be in the next release hopefully). There will likely be one more 0.3x series release to finalise translation, add makeobj integration and add winter building support, then I'm going to work on re-coding much of it so I can add all the cool features I want to... That may well take a while, so if you have found any bugs that aren't fixed please tell me so I can fix them before the re-code

New in 0.3d.1:
FIX: Bug in cutting routine moving everything down by one pixel
FIX: Monuments/Curiosities improperly handled in dat output (GUI still a little buggy here, but will fix that in the next major release)

New in 0.3d:
ADD: Export dat file only option added to menu
ADD: Can move cutting mask in paksize increments (use "Fine" control to switch back to pixel-increments)
ADD: Support for "needs_ground" flag
ADD: Can define climates building will appear in
FIX: Input/Output goods for factories now saved correctly
FIX: Level info indicator now translatable
CHANGE: Translation now done via more Simutrans-like system, hopefully compatible with SimuTranslator
ADD: Auto-translation string finding script (TileCutterTranslator) to simplify work of maintaining the base translation file
FIX: Disabled Makeobj-related things (for now)

For more information about that this does, see this thread.

Please post bug reports for this version in this thread! I'm sure it's full of bugs, so please do tell me about them so I can fix them!

[mobo]

Hi Timothy!

I recently downloaded your tilecutter v0.3. I didn't need it before but now that i'm working on some 2x2 parks it would be very handy for me. But i encountered some problems:

png things

1. It cut one line of pixels off at the bottom and aligned the rest 1 px lower (so threre was one line missing at the top). I tried using the offset buttons but i couldn't push the source pic up only down

2. It created some colorful line at the top of the png

dat things

3. it created wrong image paths in the dat: "BackImage[0][0][0][0][0]=..\tc\tilecutter\TileCutter-v0.0.0"

4. the parameter "build_time=x" can only be set for mon but not for cur buildings (should be the other way, there are no out of city monuments i think). In fact this determines whether the pak gets built in a city when population="x" or somewhere outside the city when it's omitted. That's how it used to work, maybe this has changed now that"location=" is available, but setting my park to "location=city" didn't work as one would expect, it still appeared in the countryside.

Number 1 is my actual problem. Hope it's not just a user-fault, but i didn't find out how to avoid/use properly.

Attachments are: dino is source png, dino2tc is the result i got from tilecutter, and dino2 is how it should have looked (selfmade)

[kierongreen]

Points 1 and 2 sound linked to me - colourful line is most likely random data because there is no source image at this point, due to it being 1 pixel down.

[mobo]

Hm, might be. But since the whole workspace is in blue (231,255,255 - transparent color) i would expect that missing parts get filled up with that.

But i don't really know.

[Timothy]

Thankyou for your report mobo, I'll look into this, the coloured line is indeed most likely caused by it trying to copy the image from a place it shouldn't be (has been reported before, but is quite a sporadic bug...) The other things shouldn't be too hard to fix, watch this space...

[Timothy]

1. It cut one line of pixels off at the bottom and aligned the rest 1 px lower (so threre was one line missing at the top). I tried using the offset buttons but i couldn't push the source pic up only down

This is now fixed, was caused by a rogue -1 which shouldn't really have been there at all, I'm surprised I didn't spot that before.

2. It created some colorful line at the top of the png

Related to the above bug, shouldn't happen anymore now.

3. it created wrong image paths in the dat: "BackImage[0][0][0][0][0]=..\tc\tilecutter\TileCutter-v0.0.0"

4. the parameter "build_time=x" can only be set for mon but not for cur buildings (should be the other way, there are no out of city monuments i think). In fact this determines whether the pak gets built in a city when population="x" or somewhere outside the city when it's omitted. That's how it used to work, maybe this has changed now that"location=" is available, but setting my park to "location=city" didn't work as one would expect, it still appeared in the countryside.

For the .dat bug, could you give me some more information (where the png and dat were being outputted and the full dat file it outputted).

Only city curiosities should be able to set the build_time flag, but you are right this needs updating. Will also be fixed in the next minor release.
Posted on: February 03, 2007, 11:45:04 AMNew version is up, see the first post!

[mobo]

For the .dat bug, could you give me some more information (where the png and dat were being outputted and the full dat file it outputted).


Posted on: February 03, 2007, 11:45:04 AMNew version is up, see the first post!

Well... I got a folder C:\simusources with a subfolder "park" there the dats and pngs were saved. The programme itself is in c:\simusources\tc\+ some subfolder that was created when extracting (you can see it 9in the wrong img line, the folder had a . (dot) in it's name. The last part behind the dot was replaced by the row and coloumn index (so it was treted like the png extension).

Hope this helps

[Timothy]

Hmm, probably caused by the routine for finding relative paths between files messing up with a directory that has a "." in it, will be fixed in the forthcoming 0.4 release most likely as I'll be re-writing that (rather shoddy) part of the code to make it easier to port to other platforms.

Incidentally, here's a screenshot of the development thus far...

[prissi]

It would be great, if there is a button "cut" which just cut the image. I did not suceed in cutting an image

[Timothy]

You need to use the "export" option from the menu to output the cut image, adding a button to do this would definitely be simpler though.

[prissi]

Well, do I need to make a dat too, even if I just want a cut? Because both export stuff did not generate anything respective was greyed out. (There wasn't so much options, that I did not tried them all.)

[mobo]

You need to define the export files and paths first, below the image area, then you can export dat and png or only png(cut).

Maybe that's the problem?!

[Ozone]

huh? I use  What could I do?
Posted on: May 14, 2007, 09:32:16 AMOk, forget it!
I've found it

[Tomas]

Version 0.4 looks good! When you release this version

[Timothy]

Soon, though it's version 5 now, should be ready in a week or two now.

[ayuroom]

Soon, though it's version 5 now, should be ready in a week or two now.

What a long wait...one and a half year!!

[Tags:]

The International Simutrans Forum > Projects and Web Resources > Various Projects (Moderator: Isaac.Eiland-Hall) > Topic: TileCutter 0.3d.1