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

[James.Denholm]

Hey Japa, you mentioned a few pages back you're the only active dev. Why is that? People just busy at the moment?

everybody's busy. me too now

Awww, so this is the end for Stonesence development? Sure is a pity, you guys did awesome though.

Wow, that's a jump.

For most volunteer-based coding project, it's not. If all the devs lose interest, it's usually more common for a project to just cease development, since by the time new people are brought online, the community itself has moved on.

For example, 31.10 is still not supported. The community is moving on.

Jeez, mate, give them some time to catch up. They aren't your personal coding monkeys, you know.

Keep your pants on, allright?

[Star Guarded]

Yeah, seriously. They can take all the time they want to. I appreciate that they use their free time to give us a fantastic application. No one is "moving on" or whatever. I was only asking because it would have sucked if he had meant the other developers had stopped working on it, but that they're just busy is good news.

[MP2E]

So a project is dead instantly because the volunteers are busy for a little bit? Wow. Ridiculous. :| Look at all the time, code, and resources that have been put into this project? I don't see it "dying" any time soon. Even if the developers did quit on it I'm sure a few months later someone new would jump on board and bring it up to date

[Rose]

So a project is dead instantly because the volunteers are busy for a little bit? Wow. Ridiculous. :| Look at all the time, code, and resources that have been put into this project? I don't see it "dying" any time soon. Even if the developers did quit on it I'm sure a few months later someone new would jump on board and bring it up to date

hey, that's what happened in my case.

[shibdib]

So a project is dead instantly because the volunteers are busy for a little bit? Wow. Ridiculous. :| Look at all the time, code, and resources that have been put into this project? I don't see it "dying" any time soon. Even if the developers did quit on it I'm sure a few months later someone new would jump on board and bring it up to date

Just because something has alot of time in it doesnt mean it cant die.. if obsidian ever gets working this will disappear. Your more likely to see some1 make a completely new project instead of picking up an old one as they get the glory.

[James.Denholm]

Just because something has alot of time in it doesnt mean it cant die.. if obsidian ever gets working this will disappear. Your more likely to see some1 make a completely new project instead of picking up an old one as they get the glory.

I don't want to take the flamebait here, really, but...

Just... No.

[Greiger]

if it helps anything the memory.xml for runesmith seems to work just fine in stonesense for version .10.

It's not a real update of course, but it would get it working.

[Symbiode]

if it helps anything the memory.xml for runesmith seems to work just fine in stonesense for version .10.

It's not a real update of course, but it would get it working.

I tried to replace the Memory.xml with the one from Runesmith, but it still got stuck at 'connecting to df'. Did you modify anything else to get it to work?

[Greiger]

Well it's the graphics version.  So I don't think it would work with legacy.   And I actually just copied the entries for runesmith's .09 and .10 xml entries (right above the linux penguin) and pasted it into stonesenses' xml.

It should be the exact same thing to just copy the whole file.  But if it's not working maybe I'm wrong.

I took this from the runesmith memory .xml

Spoiler (click to show/hide)

Code: [Select]

    <Entry version="v0.31.09" os="windows" id="0.31.09" base="0.31.08" rebase="0xD028" > rebase="0xD030"
        <!-- TODO: fix creature offsets -->
        <!-- TODO: small offsets added all over the place, investigate -->
        <String name="md5">1a85839ab03df082974dc5629d3fbc26</String>
        <HexValue name="pe_timestamp">0x4C3897C0</HexValue>
        <Address name="cursor_xyz">0xaff2d8</Address>       
        <Address name="language_vector">0x16D33CC</Address>
        <Address name="translation_vector">0x16D33FC</Address>
        <Offset name="word_table">0x4c</Offset>

        Creatures
        =========
        <Address name="creature_vector">0x168E73C</Address>
        <Address name="dwarf_race_index">0x014b9f1c</Address>     
        <Offset name="creature_soulskill_vector">0X1F4</Offset>
        <Offset name="creature_physical">0x4AC</Offset>       
        <Offset name="creature_appearance_vector">0x64c</Offset> <!-- Maybe slightly wrong -->
        <Offset name="creature_artifact_name">0x71c</Offset>
        <Offset name="creature_labors">0x7Bc</Offset>
        <Offset name="creature_soul_vector">0x0788</Offset>
        <Offset name="creature_default_soul">0x07A0</Offset>
        <Offset name="creature_happiness">0x87c</Offset>
    </Entry>
    <Entry version="v0.31.10" os="windows" id="0.31.10" base="0.31.09">
        <String name="md5">349d1ad6eda7b6c5e87f8e4726a0999a</String>
        <HexValue name="pe_timestamp">0x4C398089</HexValue>
    </Entry>

 And it goes right above the linux penguin in stonesense's .xml file right after the last </entry>  in the windows block. 

That should get it working with the graphics version.  Remember I didn't find these values, the guys at Runesmith, Therapist, and DFHack did from what I understand.

P.S. Also note that these values are just a random thing I decided to try that happened to work.  I haven't come across any problems but note that these values have not been fully tested in stonesense.  I'm not on the team and only have dabbling programming skill.  If anyone wants me to take these down, just give me a holler in PM or here.  And I'll remove them as soon as I see the message, and I apologize in advance.

P.S. #2  You may want to back up your old memory.xml.  These values seem to work for some, and not others.

[Joishi]

adding that code into the spot you mentioned worked for me!!  (But I started with the .08 memory.xml file from the file depot AND I'm using the SDL version)

Thanks!

[Ivar360]

adding that code into the spot you mentioned worked for me!!  (But I started with the .08 memory.xml file from the file depot AND I'm using the SDL version)

Thanks!

After downloading the .08 xml file and copying the code mine works too

[Thoth]

Worked for me now to try to get the adamantine spire to output, any suggestions on what settings other than software and 2k odd z segmentsize_z to try to grab the whole 2072z tall spire?

[As Always]

For some reason, still isn't working for me. I have SDL .10, Stonesense, and the .08 Memory.xml file. I copy that code into the .xml, using wordpad, right next to the last Windows </Entry>, and the same problem still occurs as before - a black box pops up upon running, sits there for 10-15 seconds, then crashes with no error message. In the report file, all I get is

Stonesense launched
Using allegro version 4.9.20 r0
4096 works.

Once for each time I run it. Any help? I'd like to take a look at my most current fort in Stonesense, haha.

[Trigonous]

Adding that code also gives me a crash right after I press F9 to connect.  It says "connecting to DF" for a few seconds (no flashing) then crashes.  I'm using Windows 7 64 bit.

[Greiger]

Hm... unfortunately I can't really help with it crashing.  I only have a general idea on how to read xml, only enough to have figured out where these entries go really, and haven't even seen any of the stonesense code.  I only know a few lines of any real programming languige, (thus dabbling) and probably wouldn't be able to figure it out even if I looked.

All I can think of is maybe the tokens being placed in the wrong spot, though these forums tend to be pretty good at that kind of thing.  Here's more of my own memory.xml (includes the .08 data and linux penguin.) in case there is any misunderstanding with the location instructions.  The .9 and .10 entries are bold It seem to need them both as they appear to use previous versions as a base even though stonesense probably wouldn't work properly on .09 even with these entries judging from the comments.

Spoiler (click to show/hide)

    </Entry><Entry version="v0.31.08" os="windows" id="0.31.08" base="0.31.06" rebase="0x1000"><String name="md5">a83e6b21307cf41fb54c315fa40dec86</String><HexValue name="pe_timestamp">0x4c1d69fe</HexValue><Address name="cursor_xyz">0xaf22d8</Address>
[addresses]
translation_vector      = 0x016c53dc
language_vector         = 0x016c53ac
creature_vector         = 0x0168071c
dwarf_race_index        = 0x014abef4
    </Entry>
    <Entry version="v0.31.09" os="windows" id="0.31.09" base="0.31.08" rebase="0xD028" > rebase="0xD030"
        <!-- TODO: fix creature offsets -->
        <!-- TODO: small offsets added all over the place, investigate -->
        <String name="md5">1a85839ab03df082974dc5629d3fbc26</String>
        <HexValue name="pe_timestamp">0x4C3897C0</HexValue>
        <Address name="cursor_xyz">0xaff2d8</Address>       
        <Address name="language_vector">0x16D33CC</Address>
        <Address name="translation_vector">0x16D33FC</Address>
        <Offset name="word_table">0x4c</Offset>

        Creatures
        =========
        <Address name="creature_vector">0x168E73C</Address>
        <Address name="dwarf_race_index">0x014b9f1c</Address>     
        <Offset name="creature_soulskill_vector">0X1F4</Offset>
        <Offset name="creature_physical">0x4AC</Offset>       
        <Offset name="creature_appearance_vector">0x64c</Offset> <!-- Maybe slightly wrong -->
        <Offset name="creature_artifact_name">0x71c</Offset>
        <Offset name="creature_labors">0x7Bc</Offset>
        <Offset name="creature_soul_vector">0x0788</Offset>
        <Offset name="creature_default_soul">0x07A0</Offset>
        <Offset name="creature_happiness">0x87c</Offset>
    </Entry>
    <Entry version="v0.31.10" os="windows" id="0.31.10" base="0.31.09">
        <String name="md5">349d1ad6eda7b6c5e87f8e4726a0999a</String>
        <HexValue name="pe_timestamp">0x4C398089</HexValue>
    </Entry>
   

                            .-"""-.
                           '       \
                          |,.  ,-.  |   _________________________
                          |()L( ()| |   \                        \
                          |,'  `".| |   /_  Argh !!!              \
                          |.___.',| `     \________________________\
                         .j `--"' `  `.
                        / '        '   \
                       / /          `   `.
                      / /            `    .
                     / /              l   |
                    . ,   L I N U X   |   |
                    ,"`.             .|   |
                 _.'   ``.          | `..-'l
                |       `.`,        |      `.
                |         `.    __.j         )
                |__        |--""___|      ,-'
                   `"--...,+""""   `._,.-'
   
   
    <!-- Windows logo by Microsoft --><!-- Tux logo by the Linux guys --><Entry version="linux-offsets-2010" os="all" id="linux-offsets-2010" base="meta-2010">

That's really all I can think of. 

And yea, as others said you will need the entries for .08 as well (I had mistakenly assumed they came with the last release).  I don't recall exactly where I got the .08 numbers shown here, but I assume I pulled them from the file on the depot.