Print

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

[Sean Mirrsen]

From an outsider perspective, it strikes as might having something to do with how quickly stuff is getting added/changed. Tilesets are outdated before they're finished, no?

That's certainly a part of it, and also the simple fact that while we might include a few of the more popular tilesets in the download, none of the tilesets are actually "official", but are supported by individual forum users. As for overall tileset compatibility improvements being slow, it's a combination of most of our devs playing with ASCII instead of tiles, many of them using console versions because they run faster on Linux (which most of our main devs use a form of), and because UI code is a pain to write.

That's just the thing, too. The another thing, as it were. The thing I am trying to add solves exactly that. A "default" tile page, so that tilesets don't need to be updated, and can use default ASCII graphics that match the tileset in style - like Dwarf Fortress does - for anything that the tileset does not itself define.

[scrdest]

From an outsider perspective, it strikes as might having something to do with how quickly stuff is getting added/changed. Tilesets are outdated before they're finished, no?

That's certainly a part of it, and also the simple fact that while we might include a few of the more popular tilesets in the download, none of the tilesets are actually "official", but are supported by individual forum users. As for overall tileset compatibility improvements being slow, it's a combination of most of our devs playing with ASCII instead of tiles, many of them using console versions because they run faster on Linux (which most of our main devs use a form of), and because UI code is a pain to write.

That's just the thing, too. The another thing, as it were. The thing I am trying to add solves exactly that. A "default" tile page, so that tilesets don't need to be updated, and can use default ASCII graphics that match the tileset in style - like Dwarf Fortress does - for anything that the tileset does not itself define.

I think there might be a small issue with that: the tilesets vary in resolution, ranging from 16x, through 24x, to 32x.

[Sean Mirrsen]

From an outsider perspective, it strikes as might having something to do with how quickly stuff is getting added/changed. Tilesets are outdated before they're finished, no?

That's certainly a part of it, and also the simple fact that while we might include a few of the more popular tilesets in the download, none of the tilesets are actually "official", but are supported by individual forum users. As for overall tileset compatibility improvements being slow, it's a combination of most of our devs playing with ASCII instead of tiles, many of them using console versions because they run faster on Linux (which most of our main devs use a form of), and because UI code is a pain to write.

That's just the thing, too. The another thing, as it were. The thing I am trying to add solves exactly that. A "default" tile page, so that tilesets don't need to be updated, and can use default ASCII graphics that match the tileset in style - like Dwarf Fortress does - for anything that the tileset does not itself define.

I think there might be a small issue with that: the tilesets vary in resolution, ranging from 16x, through 24x, to 32x.

So do Dwarf Fortress graphics sets. They just have tilesets to match. Here, it's even simpler as the tileset maker already works with the matching tile size.

[scrdest]

From an outsider perspective, it strikes as might having something to do with how quickly stuff is getting added/changed. Tilesets are outdated before they're finished, no?

That's certainly a part of it, and also the simple fact that while we might include a few of the more popular tilesets in the download, none of the tilesets are actually "official", but are supported by individual forum users. As for overall tileset compatibility improvements being slow, it's a combination of most of our devs playing with ASCII instead of tiles, many of them using console versions because they run faster on Linux (which most of our main devs use a form of), and because UI code is a pain to write.

That's just the thing, too. The another thing, as it were. The thing I am trying to add solves exactly that. A "default" tile page, so that tilesets don't need to be updated, and can use default ASCII graphics that match the tileset in style - like Dwarf Fortress does - for anything that the tileset does not itself define.

I think there might be a small issue with that: the tilesets vary in resolution, ranging from 16x, through 24x, to 32x.

So do Dwarf Fortress graphics sets. They just have tilesets to match. Here, it's even simpler as the tileset maker already works with the matching tile size.

Alright, then. Anyway, you might try to scavenge the ASCII that fits the tilesets from Deon's tileset, it already utilizes those partially.

[Akhier the Dragon hearted]

So did the compiling on windows with C::B thing get worked out? Cause I would be interested in that.

[Sean Mirrsen]

Yes, it did. I found the libraries I needed, though in all likelihood I won't be able to avoid the DLLs.

It's really rather straightforward, in retrospect. Just follow the guide on the forum (with the addendum for GetText et al), download SDL, SDL_ttf, and SDL_image dev kits and VC libraries, and use the existing project dependencies as a guideline.

[Akhier the Dragon hearted]

Simple tends to be one of the hardest things to find.

[Sean Mirrsen]

I can post a more detailed setup procedure if you really need it.

[Akhier the Dragon hearted]

   No, I was just commenting on how life tends to work. Rereading my post I can see it sounding like I was saying I couldn't figure it out.

[teoleo]

why not add the graphical Tiles also for the map?

[Sean Mirrsen]

Map, objects, anything. Graphical tiles exist for everything. The problem is that the tileset has to define and provide all of those tiles, or else anything that isn't defined shows up as "unknown".

[Akhier the Dragon hearted]

   Yeah, one of the biggest draw of developing with ASCII for graphics is that you don't have to worry about art. Its actually the biggest reason DF is in ASCII. Its hard to develop a constantly changing game if you have to wait for the art to catch up with every change. The only reason we have such nice graphical tilesets for DF is because it has such a big following and it has taken a good amount of time between released versions so the art can catch up. If I was to make a tileset for CataDDA I would be ignoring the experimental build until I had the most recent stable finished. It is amazing that CataDDA is developing so fast but it is very much a moving target for any one making a tileset.

[Mookzen]

Speaking of fast development, any news on the NPCs and the Z-levels ?

[i2amroy]

Speaking of fast development, any news on the NPCs and the Z-levels ?

There's been some advancement on NPC's, but not much. These things have sort of gone into a temporary limbo due to the disappearance of our hired full-time coder (Don't worry, we only paid him for the time he was here). IIRC GlyphGryph is working on setting up a potential bounty system with our remaining money, which will definitely include both of those things and should encourage some more work in those directions.

[Akhier the Dragon hearted]

   So I have a video up and the first 18 minutes is me going through how you determine your damage and to hit. If anyone that actually has a clue of about it wants to take a look and see if I messed up any of the details that would be good so I know I am not misinforming people. I should have it right as I went off of the code but things happen. The video is here. I try to make what is going on in the code understandable so hopefully it worked.