Print

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

That's right

That is right

[therahedwig]

Multilevel trees! W00t!

In preparation of whatever toady's gonna come up with, I presume?

[Rose]

actually, no. just to make the current trees look better.

[dennislp3]

Well those palm trees look bad ass!

Do all sprites always show up in the same position?...cause you could add a tiny (tiny tiny) curve into the palm trees and have them generate in a random facing to increase the look of variety....

[Rose]

as it is right now, you can add a curve to the trunk, and it'll be on all the trees, but I'll work on getting the trees support random sprites (they do right now, actually, but it's not coordinated, so each section of the tree would be random independent of every other section, which may or may not look good, depending on the tree)

The reason I'm implementing these kind of trees is because in my personal head canon, the tree icons in DF are simply representations of the impassable trunk, with the rest of the tree being abstracted away because dorves aren't affected by it.

[dennislp3]

Thats true...at least until multi tile entities become possible..then we could have large 2x2 trees or whatever.

Keep up the good work! You guys have by far the best visualizer in my mind.

[Kogut]

Why part of palms are just trunk without anything else?
Is it possible to do sth with "green tile under tree and yellow around"

[dennislp3]

Part of the palms are cut off cause they are multi level...so if you look the cut off ones are on higher ground than the ones you see in full.

[DwarvesH]

Wow, really awesome. Makes me add support for desert landscapes and for multilevel trees .

Do we need to wait for 2.3 to try it out? I guess the only way to get my hands on it until then is to get it from SVN.

[Bellerophon]

Personally, I didn't like colours so bright as those in stonesense, so I wrote a little python script that reduces them all in one go (also lets you play with the overall contrast etc). Works fine except for Orthoclase, which has an RGB value of 248,487,133. As far as I can tell stonesense is using an RGB roughly equivalent to 248,225,133, but I have no idea how it's arriving at that. Doesn't really matter; I'm just changing it to 225 before I run the script, but it's leaving me curious.

[Rose]

there's a little-ish xml file that contains the rbg values for all materials in the game. the colors are hand-picked by me.

[Bellerophon]

there's a little-ish xml file that contains the rbg values for all materials in the game. the colors are hand-picked by me.

That's what I'm talking about. Colors_Stone_Mineral.xml - at least the one that ships with 2.2 - lists Orthoclase as <color red="248" green="487" blue="133">. Somehow Stonesense displays a colour more like (248,225,133).

[Rose]

487? what?

that's not meant to be that number.

and the values are capped at 255.

[Bellerophon]

487? what?

that's not meant to be that number.

and the values are capped at 255.

Yeah, wasn't sure what was going on; figured it wasn't capping to 255 'cos if you bring 487 down to 255 then it renders orthoclase as pale green. Unless maybe there's a second typo and it's checking if they're over 255 then setting values over it to 225.

[Rose]

the loaded numbers are passed directly to allegro, which converts them to floats.

487 was probably meant to be 187 or something. feel free to change it to whatever you wish. if you end up with better looking colors than the ones I put in there, we'll use yours instead of mine.

[Bellerophon]

487 was probably meant to be 187 or something. feel free to change it to whatever you wish. if you end up with better looking colors than the ones I put in there, we'll use yours instead of mine.

Oh, in mine I'm changing all of them, just as a personal thing. They're all gonna be much dimmer than the current version. (EDIT: Muahahahah! That's what you get for making my fortress absurdly technicolor, orthoclase, copper and bauxite!)

If you want to make the default number sane for 2.3, though, then changing the green value to 230 gives you the same shade as the 487 in the current XML. I'm guessing that's what allegro's sanity-checking it to. (187, incidentally, is full-on orange)