Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mifki]

Soon I'll start working on updating TWBT for 0.43.05. It will be 64bit only I think as I'm not keen to find offsets for and support twice more versions.

[lethosor]

Oh, I didn't remember that it didn't support 0.43.05 yet. Will update that thread.

[jecowa]

Soon I'll start working on updating TWBT for 0.43.05. It will be 64bit only I think as I'm not keen to find offsets for and support twice more versions.

That's really good to know. Thanks for the info!

Oh, I didn't remember that it didn't support 0.43.05 yet. Will update that thread.

I'm still not completely sure that they aren't compatible. He sounds pretty confident that it works.

[lethosor]

Here are the patches it uses for 0.43.03. It can't work with 0.43.05 without a 0.43.05 section (which isn't there).

[Pvt. Pirate]

Soon I'll start working on updating TWBT for 0.43.05. It will be 64bit only I think as I'm not keen to find offsets for and support twice more versions.

So this means i really need my new Hardware and win7 the sooner the better
i understand and respect your decision though.

[Warmist]

can anyone check/knows if this is right? for win64

Code: [Select]

<global-address name='twbt_render_map' value='0x1408170b0'/>
Edit: i was stupid...

Edit: it's correct btw

[Meph]

Hey,

Any chance for more override options, or is it limited by internal DF tile-types?

Like different sprites for walls/floors depending on material. Wood/Stone/Gem/Metal.

Or body-parts (CORPSEPIECES) or meat, depending on part, like this:

Spoiler (click to show/hide)

Or caste-specific creatures graphics, for male/female sprites?

Or vermins? They are creatures, but the way DF handles their graphics, they can only use tiles from the original tileset, not creature sprites like all the other creatures. That makes it really tricky to give a sprite to all of them.

There are also text-only things ingame, like the sneaking indicator, animal tracks, depot-accessability, or low/medium/high traffic zones. Things that are essentially part of the UI, but displayed on the map.

I ask because I'm working on this tileset and I'm stumbling upon more and more little things that could be improved, if TWBT would allow it.

[Warmist]

Hey,
<...>

A few years later Meph: here's a 2gb of sprites to cover ALL possible things in DF

[jecowa]

It was inevitable.

[Meph]

Nah... the 40.000 profession sprites for all animal-men just take ~36mb once they are done.

See, I have a template with all the weapons, armors, items, professions, and I just need to copy the animal-man sprite underneath. Here the kestrel man as example:

Spoiler (click to show/hide)

Edit: Oh, and another question... TWBT know the position of the tiles it has to override, does it? Could it check neighbouring tiles, so that something like this can be done?

Spoiler (click to show/hide)

or to be more precise: Like this:

Spoiler (click to show/hide)

[Snafu]

AAARRGH! My eyes!

Please change the background of that last from shocking pink!

[jecowa]

Transparent is pretty good. Most stuff looks good against the forum's grey-colored backgrounds.

[Snafu]

Transparent is pretty good. Most stuff looks good against the forum's grey-colored backgrounds.

Sry; can't find how to set that as default b/g in FFx 50.00.. I am in no way a webpage programmer/scripter

[Fleeting Frames]

"Shocking pink" is used as transparent mask color for applications where transparent images wouldn't work because nothing is ever that color. Was common in 90s game sprites, I think.

This shock image serves just as a tiling example, though. Both DF and FFx support transparency - the image backdrop actually is shocking pink. Thankfully, it is behind a spoiler, so you can just remain unspoiled.

[mifki]

Meph,

Currently TWBT is limited by tiletypes present in DF. I'm not even sure what there is what is not, there are definitely different types for some floor/wall materials but you'd better look yourself. The same for other stuff - mostly for performance reasons. For example building overrides require to specify tile number, building ID and building type because I naturally have tile number, look up overrides for it, then check all matching buildings from world.buildings.other[id] (that's why I need ID so that I don't check ALL buildings), compare their types and then find the one located on the current tile. Of course I can also check materials, neighbour tiles and whatnot, but that would require accessing more data structures, which can be slow, especially for complex tilesets that require updating all tiles each frame ("twbt redraw_all" option).

However, if you missed it, some time ago I started to work on a new version in which I was going to implement building/item rendering "the native way" (by interposing their rendering vmethods). This is faster and should allow to implement any custom building-specific logic (e.g. different tiles for locked/unlocked doors), and also a support for animated building/item images was planned. However I suspended the development because while being a great idea, it was a difficult for me to implement - one of the problems is that if I replace the default building rendering vmethod, I need to replicate all the existing rendering logic (like different tiles for door materials, animated machines, building construction stages, etc.), and tileset authors will need to provide tiles for all the situations. I'm neither sure I'm aware of all the logic that needs to be re-implemented, nor able to get all the required tiles myself.

If you're willing/able to help with these two problems, I can continue to work on that version again.

(I think the "text-only" things you mentioned are hardcoded, so there's not much I can do.)