Print

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

[Godlysockpuppet]

Ty Mep, and also, confirmed, Resizing the game in the preparing embark screen (were you pick items and  customizing Dwarves. Using the mouse wheel crashes the game.

Thats already been stated in the bugs section. Its related to rendermax

[Meph]

I should probably add some info about Rendermax to the manual.

[Billy Jack]

It appears that GUI settings are not persisting between sessions.  Harder Smelting for one.  Harder Smithing, Harder Mining, and More Foods are working.  Those are the only ones I toggle.

[Lowen]

Using masterwork 4a, ascii tileset with creature sprites, rendermax is on:

In dwarf mode, going to the hotkeys screen (H), pressing f3 to select the third hotkey and then N to name it, if I name it something like "Lvl1" pressing 1 results in what looks like a diagonal5 exploratory mining pattern drawn all over the screen with rendermax (it appears shaded and moves around with the view). Pressing 1 again crashes dwarf fortress.

[Putnam]

Getting a repeated error popping up in DFHack. Has "Checking unit#" then a number from 1 to 67. Then in red

"...terworkDF 4\Dwarf Fortress\hack\scripts/itemsyndrome.lua:328: Cannot read field vector<unit*>.-1: index out of bounds.
stack traceback:
             [C]: in function '_index'
             ...terworkDF 4\Dwarf Fortress\hack\scripts/itemsyndrome.lua:328: in function <...terworkDF 4\Dwarf Fortress\hack\scripts/itemsyndrome.lua:326>"

then the checking unit #1-67 again. Happens every few seconds while playing.

That debug option shouldn't be on...

[ElenaRoan]

Getting a repeated error popping up in DFHack. Has "Checking unit#" then a number from 1 to 67. Then in red

"...terworkDF 4\Dwarf Fortress\hack\scripts/itemsyndrome.lua:328: Cannot read field vector<unit*>.-1: index out of bounds.
stack traceback:
             [C]: in function '_index'
             ...terworkDF 4\Dwarf Fortress\hack\scripts/itemsyndrome.lua:328: in function <...terworkDF 4\Dwarf Fortress\hack\scripts/itemsyndrome.lua:326>"

then the checking unit #1-67 again. Happens every few seconds while playing.

That debug option shouldn't be on...

Ok. So how do I turn it off? I didn't do anything different than normal.  That was with 4 though, just starting with 4a.

[Putnam]

itemsyndrome debugoff

you should also replace itemsyndrome with the latest version here

[BoffoDorf]

I actually quite like the idea of all my workshops being box forts. 
However, building things with soap is....a little more disturbing.

Building workshops out of soap is a good way to ensure you keep a few bars ready for hospital use, though with work flow and Masterwork's flexibility, that's not so much an issue anymore.

[Meph]

Using masterwork 4a, ascii tileset with creature sprites, rendermax is on:

In dwarf mode, going to the hotkeys screen (H), pressing f3 to select the third hotkey and then N to name it, if I name it something like "Lvl1" pressing 1 results in what looks like a diagonal5 exploratory mining pattern drawn all over the screen with rendermax (it appears shaded and moves around with the view). Pressing 1 again crashes dwarf fortress.

Thats because the 1 is used for zoom, I should probably change that. Zooming is bad with Rendermax.

Putnam: It is the newest version of itemsyndrome (not the one you are testing atm, but the one in your modder scripts download) and I did not turn on any debugging.

[Ruan]

Scriptorium only writes the book "Stick them with the pointy end" - all write (book) reactions write specifically that book, rather than what they're supposed to.

Took me a second to realize it, as I actually happened to start with that book, then grew confused when I kept getting it again and again...

[Meph]

I will just find a hole to hide in, never to be heard from again, ok?

[Ruan]

Only if you arrange food, water, and internet/computer access so that you can continue working on Masterwork.   

Other than that, everything seems to be working fine, or at least I haven't seen anything else so far.

[Meph]

I tested the damn thing with books from a test-reaction, which spawns every book once. Never occured to me that I might have missed something so silly. Its a simple fix though and can be done to a running world. Guess this evening (local time) I will upload 4b. ^^ Save-compatible.

[Ruan]

Good to hear - I'm liking the way my current fort is shaping up.  Guess I'll finally head to sleep then.

Oh, right, one more thing - what labor is the Ore Processor under?  I thought it was Mining like it used to be, but apparently that's changed?  I must've missed it in the change log..

[RickRollYou2]

Spacefox tileset, not sure if other tilesets have the same problem

Spoiler (click to show/hide)

Unrecognized Inorganic Token: GREENWARE_PORCELAIN
Unrecognized Inorganic Token: GREENWARE_FIRECLAY
Unrecognized Inorganic Token: GREENWARE_CLAY
Unrecognized Inorganic Token: BONE_DRY_CLAY
Unrecognized Inorganic Token: BONE_DRY_PORCELAIN

This is (obviously) causing problems with every single reaction requiring these inorganics. Errorlog is very full

I thought turning Harder Mining off should leave stable warpstone still around?

Spoiler (click to show/hide)

Unrecognized Inorganic Token: WARPSTONE_SOLID

for everything requiring warpstone too. (I do know why though, your metatag for warpstone turns off the whole inorganic file (!NOWARP!OBJECT:INORGANIC])

Question: Has the option for castes been removed? The metatags still exist though, so...