Print

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

[budthespud]

Did the system requirements go way up all of a sudden after 40d?

So I was excited to finally go back to DF after a year or so hiatus from the game, and thought I'd try out the Bisasam 16x16 tileset since it looked so pretty in screenshots. But to my dismay, I was unable to get through embark without it hanging and the program eventually closing.

So I decided to try returning to the old curses800x600 tileset, and successfully embarking, but left with a huge drop in FPS. Around a frame every 2 seconds. Could it be my old 1280x1024 monitor? I usually had around 40-50FPS on embark on 40d, if I recall.

What am I doing wrong?

[Bricks]

Have you tried both the SDL and Legacy versions?

[budthespud]

I didn't know there was a difference! I did the SDL version.  Whats the Legacy version?

[Dakk]

Did you try changing the print mode on init.txt? The default is a stable but rather slow mode on some machines, might wanna change to partial.

Oddly I noticed a slighly FPS increase from .17 to .18 .

[OperatorPants]

I thought the switch from 40d to .31 had a killer FPS drop? Or was that ever fixed? Or did I imagine the whole thing?

[Dakk]

I thought the switch from 40d to .31 had a killer FPS drop? Or was that ever fixed? Or did I imagine the whole thing?

Again, oddly enough, I barely noticed any drop from 40d to 31. on my laptop.

[janglur]

The answer is, it's all voodoo.

Every map/world is vastly different, and will always perform differently.  This causes wild notions about version differences.

.16 did improve world generation speed considerably, as Toady has stated.  Any other perceived speed improvements are purely coincidental.


Offer void in Canada.

[lastofthelight]

The drop was so huge for me I had to forgoe my usual river colonization sites, and reduce the underworld layers from 3 to 2. That fixed it....but I'm hoping it goes away.

[budthespud]

Well, I solved the FPS problem, but another has reared its head.

Is the bisasam tileset bugged? Because whenever I try to use the 16x16 set it gives me a black screened DF upon startup. I did manage to make it work before. My monitor can accept 1280x1024 maximum resolution, and it says that it has to have a minimum horizontal of 1280, so it should work.


[WINDOWEDX:1280]
[WINDOWEDY:400]
[FONT:bisasam_16x16.png]

That's how I have it in my init.txt, having saved the image in data/art folder.

[Dakk]

The reason to why I didn't notice the FPS drop may be because I started assigning DF to only one of my cores as soon as I started using the new version, so the improvement in FPS may have had masked the drop.

[budthespud]

So much for trying to go back to Mike Mayday's tileset, since it fails to work with the current version. The init remains unchanged so even when I overwrite the files with the Mayday http://github.com/rofl0r/df-mayday patches here, it does nothing. I am unsure which files need to be in the GRAPHICS section of the init.txt file for the graphics to work. I could just download the 31.14 Mayday DF, but that wouldn't be the fully-updated DF. Sigh. It didn't seem this difficult to get tiles working a year ago.

[breadbocks]

The answer is, it's all voodoo.

Every map/world is vastly different, and will always perform differently.  This causes wild notions about version differences.

.16 did improve world generation speed considerably, as Toady has stated.  Any other perceived speed improvements are purely coincidental.


Offer void in Canada.

Pretty much this. I gained FPS from 40d to 31.

[Larry421]

Well, I solved the FPS problem, but another has reared its head.

Is the bisasam tileset bugged? Because whenever I try to use the 16x16 set it gives me a black screened DF upon startup. I did manage to make it work before. My monitor can accept 1280x1024 maximum resolution, and it says that it has to have a minimum horizontal of 1280, so it should work.


[WINDOWEDX:1280]
[WINDOWEDY:400]
[FONT:bisasam_16x16.png]

That's how I have it in my init.txt, having saved the image in data/art folder.

If you're using the SDL, just set them to 0x0.
Use the mouse wheel to zoom in and out, also the window is resize-able now.

[Thief^]

The reason to why I didn't notice the FPS drop may be because I started assigning DF to only one of my cores as soon as I started using the new version, so the improvement in FPS may have had masked the drop.

Alternatively neither made any difference at all.

[budthespud]

Thanks for the advice and help everyone, I got bisasam working and the zoomable SDL stuff is a real treat, now I can zoom out and view everything going on without much difficulty! And the FPS is fine now too.

I do have one linguering question though, is it possible yet to edit out aquifers, or at least lessen their frequency on a custom map? I am wary of messing with the settings to find out, so I am hoping someone has figured this out.