Print

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

[Salkryn]

64-bit DF!?

*endless screaming*

[LordFreezer]

Windows Defender is reporting DwarMockup-1.2.0.exe as malware.  It says it detected item: Trojan:Win32/Rundas!plock.

Likely a false positive

[Salkryn]

Windows Defender is reporting DwarMockup-1.2.0.exe as malware.  It says it detected item: Trojan:Win32/Rundas!plock.

Likely a false positive

Yeah, that happens fairly often with DF and DF add-ons, particularly when there's been a big update.

[PeridexisErrant]

Is the LNP going to be released for the 64bit version at some stage?

I have pretty limited knowledge as far as what goes on behind the scenes, but I'll hazard a guess and say that dfhack amongst numerous other things will probably need to see some huge changes prior to this ?

64-bit DF!?

*endless screaming*

I would like to go 64-bit as soon as possible, which is likely to depend on DFHack.  That means waiting 2-3 months, I suspect... but hopefully less!

[Benjamin the Rogue]

So with the release of 0.43.05 I imagine it's going to be a while until LNP gets another release? I'm a layman when it comes to this sort of stuff, but I don't imagine taking mod files built for a 32-bit game to a 64-bit game is very simple.

[Sheila]

Thanks for all your hard work! 

[Dirst]

So with the release of 0.43.05 I imagine it's going to be a while until LNP gets another release? I'm a layman when it comes to this sort of stuff, but I don't imagine taking mod files built for a 32-bit game to a 64-bit game is very simple.

Raws-based mods should be unaffected, and even most scripting would Just Work.  The hard part is updating the core DFHack, which may have knock-on effects for plugins.

[Akhier the Dragon hearted]

Some plugin authors are going to have to dive into API hell.

[Snafu]

Some plugin authors are going to have to dive into API hell.

Hmm.. not sure if this is relevant but I still can't get workflow limits to work properly

DFHack enabled; Workflow enabled, but Alt-W doesn't bring up an auto (limit/produce) in the GUI What am I missing?

[lethosor]

DFHack enabled; Workflow enabled, but Alt-W doesn't bring up an auto (limit/produce) in the GUI What am I missing?

PE took out that shortcut, I think. Are you on 0.43.03? You might not need workflow for much anymore, although you should still be able to use it.


Regarding DFHack updates: the API shouldn't change much, and hopefully not in an incompatible way, so scripts and plugins would be affected about the same (hopefully not much, besides whatever structure changes there are in newer versions - we've already found a couple). Just to clarify, the DFHack people maintain all the plugins (and scripts) shipped with DFHack. Plugins are actually easier to update than scripts, because they will fail to compile at all if they use things that changed in any way, so we have to get them to compile in order to ship DFHack. With scripts, we don't notice issues until we run them, so things that break can go unnoticed sometimes.

[Snafu]

DFHack enabled; Workflow enabled, but Alt-W doesn't bring up an auto (limit/produce) in the GUI What am I missing?

PE took out that shortcut, I think. Are you on 0.43.03? You might not need workflow for much anymore, although you should still be able to use it.

OK tks. Workflow still works as expected, mostly, but the limits GUI shortcut was really useful & I can't seem to see a substitute

v0.43.03, yes, for confirmation

[lethosor]

You can just re-add the keybinding lines to dfhack.init:

Code: [Select]

keybinding add Alt-W@dwarfmode/QueryBuilding/Some/Workshop/Job gui/workflow
keybinding add Alt-W@overallstatus "gui/workflow status"


[Benjamin the Rogue]

So with the release of 0.43.05 I imagine it's going to be a while until LNP gets another release? I'm a layman when it comes to this sort of stuff, but I don't imagine taking mod files built for a 32-bit game to a 64-bit game is very simple.

Raws-based mods should be unaffected, and even most scripting would Just Work.  The hard part is updating the core DFHack, which may have knock-on effects for plugins.

DFHack enabled; Workflow enabled, but Alt-W doesn't bring up an auto (limit/produce) in the GUI What am I missing?

PE took out that shortcut, I think. Are you on 0.43.03? You might not need workflow for much anymore, although you should still be able to use it.


Regarding DFHack updates: the API shouldn't change much, and hopefully not in an incompatible way, so scripts and plugins would be affected about the same (hopefully not much, besides whatever structure changes there are in newer versions - we've already found a couple). Just to clarify, the DFHack people maintain all the plugins (and scripts) shipped with DFHack. Plugins are actually easier to update than scripts, because they will fail to compile at all if they use things that changed in any way, so we have to get them to compile in order to ship DFHack. With scripts, we don't notice issues until we run them, so things that break can go unnoticed sometimes.

Thanks. I don't know how any of this works, but that doesn't mean I'm not curious about the work that goes into it.

[Dirst]

Regarding DFHack updates: the API shouldn't change much, and hopefully not in an incompatible way, so scripts and plugins would be affected about the same (hopefully not much, besides whatever structure changes there are in newer versions - we've already found a couple). Just to clarify, the DFHack people maintain all the plugins (and scripts) shipped with DFHack. Plugins are actually easier to update than scripts, because they will fail to compile at all if they use things that changed in any way, so we have to get them to compile in order to ship DFHack. With scripts, we don't notice issues until we run them, so things that break can go unnoticed sometimes.

For anyone who's curious, the biggest unplanned changes for scripts are what are called anon attributes.  That's some fiddly bit inside the game data that is of a known size and location, but no one knows what it does.  Sometimes a modder will notice for example that a script only works when a particular anon is set to "1".  You can't depend on the fact that anon_4 is still going to be anon_4 in the next version.

Short of an incredibly bloated version control system, there's just no way to know when a script that touches an anon is going to break.  I think that's a bit more likely during the switch to 64 bits, but definitely not a sure thing.

[lethosor]

Well, I meant any structure changes. Like if df.tile_type.TREE or something goes away (which it did in 0.40), we'll catch all plugins that use that right away and be able to update them, while we'd have no idea about scripts until we look through them. I guess anon fields could be included in that too, but structure changes in general were the main issue I was talking about.

I think that's a bit more likely during the switch to 64 bits, but definitely not a sure thing.

What's more likely to break? Scripts using anon fields? I doubt Toady made many structure changes in 0.43.04/05, since those were mainly compiler/build system changes.