Print

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

[Waladil]

Um... Problem?
When I run dfhack with .24, I'm getting one of two errors, depending on what I use.
Either "memory object not set: type offset key /string/MSVC/buffer" and I get that when I use attachtest, expbench, flows, lair, liquids, pause, position, prospector, reveal, suspend, unstuck, and vdig.
Anything else with "stop responding"

Using DF v.24 on a Windows 7 x64 (that MAY be the problem?) machine.

Did some more looking. I got the modified memory.xml from that guy a few posts ago, and that didn't work. Also, tried .25, also no go. Same problems for all (except that I was having other issues on .24 w/ therapist that have been resolved)

[lorb]

Some toolsare not working on my Debian machine .
I installed dfhack from the ubuntu32bit package which worked fine.
But some tools do not work, some do.
dfattachtest and dfsuspend work fine.
dfflows also works fine, and dfveinlook is properly working.

Errors i get from:
dfprospector: symbol lookup error: dfprospector: undefined symbol: _ZN6DFHack4Maps17ReadLocalFeaturesERSt3mapINS_10planecoordESt6vectorIPNS_9t_featureESaIS5_EESt4lessIS2_ESaISt4pairIKS2_S7_EEE
and:
dfliquids: symbol lookup error: dfliquids: undefined symbol: _ZN6DFHack7Context11getPositionEv

ideas? would be glad if someone could lead me to a diagnosis whats going wrong here
ps: i have limited skills in (c++) programming, if that helps

-edit: DF is version 31.19

[peterix]

Um... Problem?
When I run dfhack with .24, I'm getting one of two errors, depending on what I use.
Either "memory object not set: type offset key /string/MSVC/buffer" and I get that when I use attachtest, expbench, flows, lair, liquids, pause, position, prospector, reveal, suspend, unstuck, and vdig.
Anything else with "stop responding"

Using DF v.24 on a Windows 7 x64 (that MAY be the problem?) machine.

Did some more looking. I got the modified memory.xml from that guy a few posts ago, and that didn't work. Also, tried .25, also no go. Same problems for all (except that I was having other issues on .24 w/ therapist that have been resolved)

Interesting. I've only seen that happening for people running DFHack on wine/osx and wine/linux and blamed it on wine... I use the same version of Windows to build the thing, so that can't be the problem. I'll have to investigate this for real, but here's what I suspect: something is broken in the xml reader library I'm using.

ideas? would be glad if someone could lead me to a diagnosis whats going wrong here

Build system fail. Looks like it didn't pick up the changes properly and some parts didn't get rebuilt. The Ubuntu machines are VirtualBox VMs connecting a share with all my programming stuff from the host. Looks like there's something wrong with that vbox share, probably doesn't preserve some metadata or something like that.

[danaris]

Um... Problem?
When I run dfhack with .24, I'm getting one of two errors, depending on what I use.
Either "memory object not set: type offset key /string/MSVC/buffer" and I get that when I use attachtest, expbench, flows, lair, liquids, pause, position, prospector, reveal, suspend, unstuck, and vdig.
Anything else with "stop responding"

Using DF v.24 on a Windows 7 x64 (that MAY be the problem?) machine.

Did some more looking. I got the modified memory.xml from that guy a few posts ago, and that didn't work. Also, tried .25, also no go. Same problems for all (except that I was having other issues on .24 w/ therapist that have been resolved)

Interesting. I've only seen that happening for people running DFHack on wine/osx and wine/linux and blamed it on wine... I use the same version of Windows to build the thing, so that can't be the problem. I'll have to investigate this for real, but here's what I suspect: something is broken in the xml reader library I'm using.

You use 64-bit Windows?

I think my Wine is 64-bit (my machine certainly is), so if you're building on 32-bit, that could be (part of) the problem...

[EmperorJon]

I'm just wondering, I ran reveal and closed the window without unrevealing, and now... if I reveal and unreveal I can't unreveal... so I'm stuck revealed?

[Grax]

I'm just wondering, I ran reveal and closed the window without unrevealing, and now... if I reveal and unreveal I can't unreveal... so I'm stuck revealed?

Yes.

[EmperorJon]

Nooo... ...oooooo

 

[Grax]

Nooo... ...oooooo

 

This is the case when third party utilities just adds some unpredictable FUN. 

[peterix]

Nooo... ...oooooo
 

This is the case when third party utilities just adds some unpredictable FUN. 

Not unpredictable. The thing did its job exactly as it was told. Unfortunately, there's no magic 'fix it' button. I guess I could spend some time writing such a magical 'fix it' button, if I had the time.

But for now I'll replace "Close to keep the map revealed." with "Close to keep the map revealed FOREVER." in future versions of the reveal tool, just to make things clearer. It's a pity I can't make that red easily, because I'd definitely do that if I could. But that would involve me writing a cross-platform terminal output wrapper that can do that...

[Grax]

Nooo... ...oooooo
 

This is the case when third party utilities just adds some unpredictable FUN. 

Not unpredictable. The thing did its job exactly as it was told.

I meant unpredictable for those who don't read manuals.

*but now i suddenly understand that i did the same facepalm long time ago when i used the revealer first time* 

[Quietust]

Not unpredictable. The thing did its job exactly as it was told. Unfortunately, there's no magic 'fix it' button. I guess I could spend some time writing such a magical 'fix it' button, if I had the time.

I seem to recall that the old Dtil utility for 40d had an "unreveal" option, though I don't recall exactly how it worked - one possibility would be to unreveal the entire map, then pick a suitable "open" location (e.g. the top of the sky) and then flood-fill outward, stopping only at natural walls (excluding those made of ice) and solid floors (i.e. everything but down stairs, up/down stairs, and open space).

[thewonderidiot]

Wouldn't really work with caverns and the magma sea. The real way to do it would just make dfreveal dump its previous revealed tile info to a file just to be safe.

EDIT: I guess we could also set unused occupancy flags on revealed tiles, assuming there are.

[Makbeth]

Nooo... ...oooooo

 

lol, there's one of these every month it seems.

[uristmcdorf]

Dont know if that was asked (dont really want to read all those 72 pages) but here it is. When i create obsidian and dug it out afterwards i cant make anything out of those stones. Worked just fine in previous versions, is there a way around this?

And i i use created magma for dumping - it wont melt anything. Just noticed that too

[Cotes]

Nooo... ...oooooo

 

People, this is what saving is for.

And i i use created magma for dumping - it wont melt anything. Just noticed that too

Is temperature on? Are the items you try to melt magma-safe?