Bay 12 Games Forum

Really man, graphics tilesets get bad, and then you get used to it, and then only the small minority of players that use that tileset understand what everything is.  Rays look like levers, for one thing.  Sometimes even levers don't look like levers, or look the same in both positions.  Then there are sections of bridges looking like trees without leaves, and then O's that look to much like fancy pillars.

Conclusion: use ASCII or a graphics/ASCII hybrid (like PTTGV5) that looks enough like the original that most people can read it.  Then your problem is solved.

Graphics sets are okay though (don't use 'em meself), because they only work for creatures and don't affect anything else.

You see, the great thing about tile sets like Mayday's is that they actually resemble the object the ascii charecter was supposed to represent.   Indeed, the exact OPPOSITE is true.  Anyone can tell that a picture of a chair is a chair.  I can show a screenshot of my game with Mayday's stuff modded in to anyone and they can get a grasp of what's going on there.

I still can't read that abortion that is the pure extended ascii dwarf fortress vanilla.

Almost certainly you've cooked your plants, which has devastated your seed supply. Go to the stocks screen and scroll to seeds to see what you have; if you only have, say, 3 plump helmet spawn, then that would explain why you're having problems there. Go easy on the cooking; it's best used for the plants that have an intermediary processing step, like sweet pods and quarry bushes. The intermediary step gets you seeds, then you can cook the results.

Of course, one can always add an extra step for plump helmets by first brewing them and then cooking the wine that's produced.

That's what I do anyway.

Here's a really great location.  If you extend it one down you can have HFS too.

I'm wondering because I'm starting a new fortress and I want giant 40-60 foot pillars lining the entrance to my mountain home, but I can't be sure of how many Z levels these need to span in order to really be that tall.

Here's an idea of how it will look at the base level.


That entrance hall will be copied over each z-level until I reach the hight I'm looking for.  I'll engrave all of the walls on each z-level before finally channeling out all of the floors except for the bottom.   All of that stuff behind the entrance hall will be space for defenders to fire from in the event of a siege.  My drawbridge to completely seperate my fortress from the outside world will be inside of the fort itself so as to not mar the appearance of my entryway.

On my main computer I actually have two seperate "installs" of dwarf fortress.  If I ever need to play around with reveal I copy one save over to both games, open reveal for one of them and then play the actual game with the other.  If I need to reference where the rock is it's pretty easy to just check and see where stuff will be.

Right. With a good GPU (an 8800GTS, say), DF already spends roughly 0% of its time doing graphics. An 80% decrease in time spent there, then, doesn't amount to much.

However, it also does quite a lot of per-frame work that isn't part of the opengl code per se. The more I can move into a separate thread of that, the better.

This change isn't for the benefit of those with modern to semimodern GPU's.  It's for those with integrated GPU's, like those in most laptops.

I personally saw a massive improvement using 40d+9 on my laptop over standard 40d.

Spreading the graphics processing over to my CPU's other core allows my first core to concentrate wholly on rendering the underlying game that we don't see, and that means more computational power is available for the real bottleneck, calculating pathfinding, temps, and flow.

Of course.  I gave you (and Sinergistic and Mayday) credit for all the stuff that went in my compilation of them in the tileset.  That's kinda the whole point of the last post I made.

I'm not sure why exactly Legolord was getting upset about that.  It's not like I was posting a separate image set for dwarfs or animals.  I was just making changes to the tileset as originally posted in this topic.

That's very silly.  Multithreading isn't the best way to speed up video.  I think the d# series proves that; there's other ways of improving performance that haven't been more than glanced at yet.  Multithreading is a huge, enormous deal that would require a lot of code rewriting.

Not so with the graphics.  Almost all of the graphical processing is entirely independent of all other graphics processing.  The bit of grass up there doesn't need to know anything at all about the bit of sand over there by the creek.

Now, when you're talking about multithreading the game engine underneith the graphical engine... that's another story.  There's a huge number of interdependances that are impacted by multithreaded processing.  You can't start calculating how much longer your dwarf has until he drowns under water until the game has found out how deep the water is first