Print

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

Higher speed, no problems

Higher speed, problems

Same speed, no problems

Same speed, problems

Lower speed, no problems

Lower speed, problems

[assimilateur]

Two known causes of exceptionally bad performance are a) pet-locked doors and b) having a very high item count on your map.

I can rule out a) in my case, and I don't know how much would be a very high item count, so I can't comment on b). I had around 10k stone in that fort. My industries were pretty underdeveloped, so I don't think I had what would count as a high number of other items.

[Footkerchief]

10,000 is probably enough to cause a noticeable drop, although I doubt getting rid of them will yield any miracles.  I think the favored way to get rid of them is to temporarily mod the stone's boiling point to just below room temperature (whatever that is).  Note that you'll need temperature turned on for this to work, and it may cause spontaneous collapse of buildings, workshops, etc. (although constructions will be unaffected).

[assimilateur]

If I understand this correctly, then what it boils down to is that you pretty much have to cut down on producing... anything if numbers as low as 10,000 are enough to make this game slow down. I mean, I can get rid of those stones by dumping them in magma or doing that modding trick you suggested, but I'm going to get another 10k of new items soon enough if I produce ammo, furniture, bags, clothing, surplus food, etc.

[Footkerchief]

Yes, cutting down on gratuitous production couldn't hurt.  Beyond that, well, 10,000 will still perform better than 20,000.

[assimilateur]

Yes, cutting down on gratuitous production couldn't hurt.  Beyond that, well, 10,000 will still perform better than 20,000.

That's the thing. I'd never thought of furniture or ammo production as gratuitous, seeing how you do need a lot of those no matter what. 

[Greiger]

As far as I can tell that's a problem inherent to Dwarf Fortress itself and has nothing to do with the graphics.

I imagine the new version will actually across the board reduce framerates considering all the new details added, even after Toady does the pathfinding optimizations I'm doubtful that it would run as fast as this version does.

Baughn's work could very well be all that keeps 50% of the community from leaving due to unplayable FPS. After all, we won't know what the new frames are like until we get are grubby little hands on the .exe.  If you got excellent frames before, awesome, as long as the 40D# stuff doesn't hurt your frames compared to standard I don't really see a problem. 

Besides, it has that fancy zooming feature now.  That's spiffy. And the possibility of transparency in tilesets is nice too, even though I don't see much difference with those myself currently, it sets ground for more to be done with it in the future.  There's also the not having to mess around with calculations for gridsizes anymore.  Even though that cunfuzzled me at first, I like it now.

[Footkerchief]

I imagine the new version will actually across the board reduce framerates considering all the new details added, even after Toady does the pathfinding optimizations I'm doubtful that it would run as fast as this version does.

Even if it does, all of the supposedly FPS-destroying features he's adding can be modded out.  I expect we'll see some attempts at high-performance mods that re-simplify creature bodies and remove the expanded underground via worldgen params.

[Shurhaian]

Adding more detail is not necessarily synonymous with poorer performance, mind. The real question is how often those details need to be checked.

I won't doubt there'll be some drop, but I don't know that it'll be all THAT major.

[Sizik]

Not really a bug but an inconsistency I noticed: You say that you can switch between zoom modes by clicking the mouse wheel, but that feature is by default bound to Ctrl-F10, not the mouse wheel.

[CobaltKobold]

I believe all the mouse actions are hardcoded and therefore won't be in the config screens, regrettably.

[Baughn]

They are /right now/, actually. Somewhere in there.

Okay. 40d17 is coming up; I've sent the last major patch to Toady, though it may still be a while.

Big changes:

- Three new display modes: 2D, 2DASYNC and 2DHW, none of which use opengl. Not as fast, but reliable and work without a 3d accelerator.
- New sound system (openal); means more reliable sound on linux.
- Rewritten input system (a-freakin'-gain), hopefully this time there will be no more problems. A number of minor improvements in how input is handled.
- No macro system. I didn't rewrite that, because I'm plotting to make a better one. It'll be back, eventually; meanwhile autohotkey should work (and if it doesn't, tell me and I'll fix it).

Overall, this may be the last d-series release. There are probably minor glitches left, but there should be nobody left unable to play it.

[quinnr]

Yay! 

I like the new modes, should be helpful to those w/o OpenGL. and the other stuff is nice too.

[kurokikaze]

Oooh, cool

[assimilateur]

- New sound system (openal); means more reliable sound on linux.

I thought the only sound in this game was one track played on classical guitar, or am I missing something here? I ask this, because I can't fathom how that could be so complicated as to be unreliable for some people.

[Baughn]

Sound on linux is, in fact, a rather.. dicey proposition.

Things vary a lot between distributions, and they expect to recompile all programs to fit.

Wait, sound? No, /binary distribution/ is a dicey proposition.