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

[Untelligent]

Alright, I tried a slightly smaller resolution and it works fine now.

One oddity I found: I have the default option set to show 50 z-levels, but when I start it up it only shows 30 or so; I can increase the z-levels shown after it starts via the keyboard command, so it's not that important, but I thought it was odd.

It also doesn't appear to be showing as much xy space as it should; this may be because it's extending the viewing distance below the viewing window instead of further out, but I wouldn't know.



Obligatory fortress pics:

Spoiler (click to show/hide)

[Greiger]

>_> <_<

I could make something pretty like that... I just don't wanna show you all up is all...  Yea... that's it.

...

How do all of you people have the patience for this stuff?  I'm perfectly happy if I get a castle that looks reasonably like a castle between all the goblin, orc and megabeast attacks.

[N3X15]

Fresh compile from SVN crashes on startup.

Code: [Select]

Unable to load image terrain/blocks.png

File simply doesn't exist.  I looked.

Ubuntu Karmic 9.10.

[Untelligent]

I'm perfectly happy if I get a castle that looks reasonably like a castle between all the goblin, orc and megabeast attacks.

Surviving long enough that the goblins run out of goblins helps in that regard. My fortress is more than thirty years old and I don't think I've been attacked at all in the last ten or so. On my fourth page of artifacts, too.

[kaypy]

Hey, if you're building under linux, why do you care about having to compile your own version for custom sprites? You have to compile your own version anyway...

Consider that I'd need to compile one version per tileset and tell me how this isn't more inconvenient.

Furthermore, if you need to grab/compile a new version for each different tileset type, it makes it far less likely for people to use fringe tilesets.

Only for wacky-sized tilesets. So its one version per tile-shape you want. Since at the moment there are a reasonable amount of tiles for one tile-shape, I dont see an issue.

Code: [Select]

Unable to load image terrain/blocks.png


Sorry. I forgot to commit a file when I merged in the terrain config. Peterix fixed it about an hour back. (thanks, Peterix)

Alright, I tried a slightly smaller resolution and it works fine now.

Yay!

One oddity I found: I have the default option set to show 50 z-levels, but when I start it up it only shows 30 or so; I can increase the z-levels shown after it starts via the keyboard command, so it's not that important, but I thought it was odd.

Yeah it clips the input to 'sensible' values. We forgot to take into account forts not necessarily being sensible 8-)

It also doesn't appear to be showing as much xy space as it should; this may be because it's extending the viewing distance below the viewing window instead of further out, but I wouldn't know.

The next release should have a config option to move the screen back a specified amount rather than just a boolean 'move it back' option. If I can talk Jonask into it, I could even make it on-the-fly changeable...

[CobaltKobold]

Hey, if you're building under linux, why do you care about having to compile your own version for custom sprites? You have to compile your own version anyway...

Consider that I'd need to compile one version per tileset and tell me how this isn't more inconvenient.

Furthermore, if you need to grab/compile a new version for each different tileset type, it makes it far less likely for people to use fringe tilesets.

Only for wacky-sized tilesets. So its one version per tile-shape you want. Since at the moment there are a reasonable amount of tiles for one tile-shape, I dont see an issue.

Present Stonesense: Thickfloors are a separate tilekind? I really don't understand how the tiles are arranged, t hough I understand that it's treating the "floor" area as one thing 4px deep and the "wall" area as another(like DF construction) 32px deep, with widths of 32px.
Old stonesense: A wall and the floor are in the same cube with no separator. 32x32. Acts like DF viewing in that fashion (a tile can be floor, wall+floor, or neither.)

These strike me as things that should be easily shifted from defines to variables (though you might want to add some checks for robustness). The shape...well, could be either way really. Mayday's would appear to only require a. a different tileset and b. a different alignment of tiles- (and, c. disabling/altering of a few things that are shape-dependent elsewhere- the tile-edgeline for instance, last I looked at the source.)

Tilesize and floor thickness at least- whether the alternate/separate floor tile exists may require more intrusion than those two variables.

My tileset concept is 16x16 nofloorthick, anyway. Its present form works all right for mockups, if you manage to avoid the hundreds of things that won't work well with same tile.

Spoiler: I've been busy. (click to show/hide)

select all black and make transparent (manually tweak to not grab the partially-dug tile and the dig-selected tile), run the gimp script I wrote, fill transparency of new thing with magenta yields:


Post-processing west ballista:

Alternate (incomplete) iso tileset for world in similar vein

Exported 'smaller' map put through the usual process:
   [TITLE:SMALLER]
   [SEED:2212473528]
   [HISTORY_SEED:1424869200]
   [NAME_SEED:1988579304]

The dwarf fortress is near the East, there's a goblin fort in the South. Unfortunately some forest tiles use the same tile as "large elvenhame" so I can't tell you which of them that is.

[tobias]

Been lurking this thread for a looong time now, finally decided to post a suggestion.

For interchangeable tilesets (probably more easily added sooner than later; less to change), I'd suggest a tilesets folder with subfolders for each configuration. Each folder can name images however it pleases, and then the xml files will either have standardized names, or maybe stonesense just loads all files ending in xml; I'll leave that up to your discretion. These files state which image files they're referring to for their image indexing and index the objects, like in the current xml files.

For making mini-mods to tilesets feasible, I'd suggest making a setting in the config that gives an interface for loading multiple tilesets. It starts by loading the first in the list, then loads the next one, overwriting anything previously defined by old tilesets with ones in the new set, that way any images not specified in the new set won't be displayed as blanks in the viewer, and it's easier to change, say, only the trap graphics, and have them usable without inserting the trap graphic into a dozen other tilesets, so everyone can have them with the tileset they prefer.

As an example of how stonesense would load the tilesets...

Spoiler (click to show/hide)

Sarting up? Oh boy, time to display some Dwarf Fortress!
I'll load up the "Default" tileset that defines all objects and has images for them, just to make sure nothing is left blank.
Now I'll check the configuration file to see if there's anything else I should load.
I see the user has added a tileset to the configuration, I'll load it.
This tileset also has all objects, that's fine, I'll just replace all instances of the old graphics with the new ones.
Hmm, another tileset.
I'll add this tileset.. This one is a mini-tileset defining only water graphics. I'll go in and change all the graphics this talks about to the new ones specified here.
Another tileset. Ho hum.
This one only changes the kitten graphic. How minimal. I'll just update that index..
That's it! Guess I'll move on to other configuration options now.

Sorry for the long-windedness.

EDIT: Oh, and I failed to specify, tilesets would be referred to in the configuration file by their folder name.

[jonask84]

Been lurking this thread for a looong time now, finally decided to post a suggestion.

For interchangeable tilesets (probably more easily added sooner than later; less to change), I'd suggest a tilesets folder with subfolders for each configuration. Each folder can name images however it pleases, and then the xml files will either have standardized names, or maybe stonesense just loads all files ending in xml; I'll leave that up to your discretion. These files state which image files they're referring to for their image indexing and index the objects, like in the current xml files.

For making mini-mods to tilesets feasible, I'd suggest making a setting in the config that gives an interface for loading multiple tilesets. It starts by loading the first in the list, then loads the next one, overwriting anything previously defined by old tilesets with ones in the new set, that way any images not specified in the new set won't be displayed as blanks in the viewer, and it's easier to change, say, only the trap graphics, and have them usable without inserting the trap graphic into a dozen other tilesets, so everyone can have them with the tileset they prefer.

As an example of how stonesense would load the tilesets...

Spoiler (click to show/hide)

Sarting up? Oh boy, time to display some Dwarf Fortress!
I'll load up the "Default" tileset that defines all objects and has images for them, just to make sure nothing is left blank.
Now I'll check the configuration file to see if there's anything else I should load.
I see the user has added a tileset to the configuration, I'll load it.
This tileset also has all objects, that's fine, I'll just replace all instances of the old graphics with the new ones.
Hmm, another tileset.
I'll add this tileset.. This one is a mini-tileset defining only water graphics. I'll go in and change all the graphics this talks about to the new ones specified here.
Another tileset. Ho hum.
This one only changes the kitten graphic. How minimal. I'll just update that index..
That's it! Guess I'll move on to other configuration options now.

Sorry for the long-windedness.

EDIT: Oh, and I failed to specify, tilesets would be referred to in the configuration file by their folder name.

Hey tobias! thanks for the input!

We're working on a system just like that (or at least very similar), but you raise some very valid points in there we're gonna make sure works okay.

We're gonna be using index files, so the user can specify the load order (folder names would be alphabetically) which prevents the situation where for instance the kitten mini-mod is loaded first, and then replaced by a more generic mod later. An index file let's the user customize load orders.

[winner]

Stonesense Granite.

because our wishes are granite?

[Ixoran]

Puns, The highest for of humor... hehe

[Osmosis Jones]

Gneiss one.

[Christes]

Holy schist, this thread is mica me sick.

[Julius Clonkus]

I really like this. It's awesome to not have 3D, but isometric tiles as an alternative to symbols.

Also:

Holy schist, this thread is mica me sick.

Sig'd.

[Footkerchief]

There's too much off-topic talc in here.  I chalk it up to a lack of updates.

[Winterbrass]

There's too much off-topic talc in here.  I chalk it up to a lack of updates.

But of quartzite's gonna get off-topic. Too much gabbro. Needs to be more to-the-point, even at the risk of being chert.