Re:Dwarf Fortress: Ten hours with the most inscrutable video...
by gchpaco on Monday February 25, 2013 @06:37AM
(#5278425)
Current hypothesis on the forums is that he uses some simplistic variant of A*; in extreme situations everything pathfinds to everything else once a tick in a totally serial program. The player base sometimes resorts to weird hacks and layouts to reduce the branching complexity of the path finding, but ultimately the more loose stone and objects you have to pathfind off and the more things you have pathfinding the worse everything gets. You don't even have to have a large number of dwarves for it to crop up; sheep are capable of bringing your machine to its knees if you don't ruthlessly cull them, or notoriously the catsplosion problem.
[ Parent
| on HN ]
Re:Dwarf Fortress: Ten hours with the most inscrutable video...
by gnarbarian on Monday February 25, 2013 @07:17AM
(#5278552)
I would love to see a bunch of hard hitting engineers focus on optimizing DF with multithreading and GPGPU stuff. It would probably require a full rewrite. Having some experience with AI and pyopencl physics simulations I have no doubt that DF could be many orders of magnitude faster and capable of sooooo much more. That's really where my angst stems from.
Re:Dwarf Fortress: Ten hours with the most inscrutable video...
by eru on Tuesday February 26, 2013 @12:49AM
(#5284209)
> [...] focus on optimizing DF with multithreading and GPGPU stuff.
You should probably start with algorithmic improvements.
Re:Dwarf Fortress: Ten hours with the most inscrutable video...
by gnarbarian on Tuesday February 26, 2013 @01:52PM
(#5287564)
It could go either way IMO, GPGPUs are super great for naively simulating a bunch of different blocks in parallel.
Re:Dwarf Fortress: Ten hours with the most inscrutable video...
by kunil on Monday February 25, 2013 @06:57AM
(#5278498)
Last time I played it, it wasn't that bad. It was like a year ago, before that minecart updates. People are exaggerating a bit or performance went worse?