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

[DwarvesH]

@DwarvesH: Awesome to see your project coming along so nicely!

Thank you!

Thanks to some of Jadael's stone graphics I am trying some really crazy things with stone tiles and layers. It is good to know that for now I don't have to worry about graphics and just code!

I have a question: how fast is Stonesense at rendering? My experience with it is slow but still very usable. Probably seems slower because of the way it periodically reads DF memory. I was wondering about the top rendering speed under ideal conditions, on a good machine where Stonesense gets along great with the hardware. Or at least average FPS that people are getting.

[Rose]

stonesense is rather slow, at the moment. I kinda went for looks rather than speed, and there's a lot that can be optimised still.

if you enable debug mode in the init.txt, you can see the drawtimes.

[DwarvesH]

stonesense is rather slow, at the moment. I kinda went for looks rather than speed, and there's a lot that can be optimised still.

if you enable debug mode in the init.txt, you can see the drawtimes.

Hmmm, 144ms on a machine that does not like 2D OpenGL. That is almost 7 FPS. Are you using Allegro with OpenGL hardware acceleration? I have 10-13 FPS on the same machine with my engine and OpenGL. But I have 70 FPS with software rendering. DirectX is comparable. I am rendering 300x300x40 maps.

Indeed, you seem to have a performance bottleneck here. But it is OK if you want to focus on looks. There is no need for blazing speed if you have the refresh speed set to 0.2 seconds. Accurate representation of DF maps is far more important.

[lemonpieman]

How do I get stonesense to work in .18? when i try to use stonesense all i get is the "connecting to df" message

[taodih]

How do I get stonesense to work in .18? when i try to use stonesense all i get is the "connecting to df" message

Read through some previous posts..

anyway , you can't for now , seemingy DFhack person is unavailable t'ill februari so it's only a partial 31.18 version, 31.16 does work fine.
I reverted back to 31.16 just because of it.

[Rose]

you can view fortresses withan updated memory.xml, but no creatures.

[lemonpieman]

How do I get stonesense to work in .18? when i try to use stonesense all i get is the "connecting to df" message

Read through some previous posts..

This is a 300 page thread.

[Rose]

From the opening post, the one you presumably got stonesense from:

If stuff's not working

Spoiler (click to show/hide)

If you are unable to connect to DF, before doing anything else, try updating to the latest Memory.xml file. This is a direct link to the latest version known to be compatible with Stonesense. Stonesense Slate 2.2 should be DF31.16 compatible.

If the application fails to launch (version 2.1 only) ("The application failed to initialize properly (0xc0150002)"), you might be missing some runtimes. This should really only happen if Windows update hasn't run in ages or for any other reason is many years outdated. You can try downloading the Visual Studio runtimes from Microsoft:
Microsoft Visual C++ 2005 Redistributable Package (2.6MB)
Microsoft Visual C++ 2005 SP1 Redistributable Package (2.6MB)
NB! Some people have noted that the second package works better from this source, put up by McBeer:
http://www.easy-share.com/1912193426/vcredist_x86.zip (unofficial, but seems to work for A LOT of problems)

Ubuntu 10.10 problems
In Ubuntu 10.10 ("Maverick Meerkat") by default disables the ability of one program to read the memory of another. This is will stop Stonesense and any other DF tool from working. Please see this thread for a suggested workaround. Thank you rmunn for bringing this to our attention.

From the previous page, the one you presumably should have read through before reaching the post button

the dfhack guy is busy till February, so there will likeley be no updates till then.

@linchowlewy: Yeah it's a DFHack issue, and there's not much we can do about it but wait.

@DwarvesH: Awesome to see your project coming along so nicely!

@Truean: Thanks for the heads up, I think I got em fixed.

[taodih]

How do I get stonesense to work in .18? when i try to use stonesense all i get is the "connecting to df" message

Read through some previous posts..

This is a 300 page thread.

on the page you posted your answer is found

Spoiler (click to show/hide)

Ah, well thats the problem. It appears i am running .18 oh well, how long will it be till they are available? because i can't wait to see my cow farm brought to life

It's apparently a DFHack issue, and Stonesense used that. They can't access the creatures because they are handled differently in the new version.
I know, my explanation is a bit sketchy, maybe others know more? (It might also be a good idea to add a detailed explanation in the opening post, since it's getting asked every few posts.)
I went over to the DFHack thread but can't find a sign of them even discussing the issue. Though probably, they are aware of it.

Meanwhile, I'm hoping for better gems (and ores?), as discussed a few pages back.
Is that on the roadmap?

[EDIT]... I'm rude today x.x sorry bout that , prolly not enough sleep.

[Jadael]

stonesense is rather slow, at the moment. I kinda went for looks rather than speed, and there's a lot that can be optimised still.

if you enable debug mode in the init.txt, you can see the drawtimes.

Hmmm, 144ms on a machine that does not like 2D OpenGL. That is almost 7 FPS. Are you using Allegro with OpenGL hardware acceleration? I have 10-13 FPS on the same machine with my engine and OpenGL. But I have 70 FPS with software rendering. DirectX is comparable. I am rendering 300x300x40 maps.

Indeed, you seem to have a performance bottleneck here. But it is OK if you want to focus on looks. There is no need for blazing speed if you have the refresh speed set to 0.2 seconds. Accurate representation of DF maps is far more important.

Well, some extra speed wouldn't HURT. I have a framerate way slower then it refreshes. It's kind of annoying trying to use Stonesense because it doesn't buffer keystrokes, I have to just hold it so it recognizes them at the frame update.

[Rose]

It buffers some keystrokes, but not all.

I specifically didn't buffer the arrow keys, because I don't want a display that runs away even after you release the keys.

[Jadael]

Ah, well does it buffer everything else? That's actually ideal, I've just been assuming I need to hold everything.

[Reese]

It buffers some keystrokes, but not all.

I specifically didn't buffer the arrow keys, because I don't want a display that runs away even after you release the keys.

Could you make it buffer a single arrow key press and throw out any extra presses? that way I could press once for precision movement and holding would not cause the display to run away after.

[Jadael]

Or count how many presses have happened and move by that amount; or keep the current behavior if you press and hold.

[Truean]

I just laugh at the unintended benefits of people not reading the thread. We effectively have a sticky for stonesense, because everyone will keep posing and asking for updates, compatibility for .18, etc.

I'm perfectly ok with this and this post disappearing somewhere on the 300s section of this page.