0000346: Recently cut wood logs not usable - Dwarf Fortress Bug Tracker

(0000761)
DoctorZuber (reporter)
2010-04-03 20:14
edited on: 2010-04-03 20:15

had a dwarf been tasked to haul the log already? if it's in use by another dwarf it's not available to build with.

(0000762)
arcaner (reporter)
2010-04-03 20:16

Do you have a wood stockpile designated? If so there's a chance the logs have been tasked to the stockpile before you can request them for construction.

(0000763)
Footkerchief (manager)
2010-04-03 20:18

I'm guessing this is yet another duplicate of 0000018, pathing weirdness, but if there's another explanation...

(0000764)
Logical2u (manager)
2010-04-03 20:19
edited on: 2010-04-03 20:21

I don't have a wood stockpile. Forgot to mention that!

Edit: That being said, even I personally suspect it's an issue with the pathfinding not resolving new objects quickly enough.

(0000766)
dibujante (reporter)
2010-04-03 20:22

Since save&reload fixed it, it is probably a subset of our pathing problems. I have experienced this during bouts of poor pathfinding.

(0000768)
DoctorZuber (reporter)
2010-04-03 20:25

I think you're right footkerchief, I'd go ahead and child it off of the pathing thread unless someone proves something different is going on here.

(0000770)
Logical2u (manager)
2010-04-03 20:33

Whenever the trees grow back I'll try to replicate the issue. That being said, there were four logs that were 'invisible', and they were scattered across the map - so it seems like quite a long time had passed, in game.

However, since it probably IS a pathfinding bug, Footkerchief, could you child this off of the main pathing bug? I'll PM you on the forums if I get any more evidence relating to this particular issue.

(0000771)
Footkerchief (manager)
2010-04-03 20:38

Done. Child issues are still open, so you can keep adding notes here if you want (that would be preferable to PMs).

(0002958)
Logical2u (manager)
2010-04-11 20:24

So, the same fortress that I uploaded for Toady that led to the fix on bug 0000070 was the same fortress that had this bug in it. So hopefully the two were connected in some way and both will be fixed!

(0002963)
DoctorZuber (reporter)
2010-04-11 20:39

I figure I'll just wait and see what pathfinding behaviors crop up after 0.31.03. He fixed something. So one down, hopefully it'll be easier to make sense of the rest now.

(0003097)
Footkerchief (manager)
2010-04-12 12:36

This and other issues are being marked resolved because they fit the symptoms of the general pathing bug described by issues 0000018 and 0000070. If this issue represents an additional bug, it will most likely present different symptoms in 31.03, and a new report should be submitted.

Issue History
Date Modified	Username	Field	Change
2010-04-03 20:07	Logical2u	New Issue
2010-04-03 20:14	DoctorZuber	Note Added: 0000761
2010-04-03 20:15	DoctorZuber	Note Edited: 0000761	View Revisions
2010-04-03 20:16	arcaner	Note Added: 0000762
2010-04-03 20:18	Footkerchief	Note Added: 0000763
2010-04-03 20:19	Logical2u	Note Added: 0000764
2010-04-03 20:21	Logical2u	Note Edited: 0000764	View Revisions
2010-04-03 20:21	Logical2u	Issue Monitored: Logical2u
2010-04-03 20:22	dibujante	Note Added: 0000766
2010-04-03 20:25	DoctorZuber	Note Added: 0000768
2010-04-03 20:33	Logical2u	Note Added: 0000770
2010-04-03 20:33	Logical2u	Issue End Monitor: Logical2u
2010-04-03 20:37	Footkerchief	Relationship added	child of 0000018
2010-04-03 20:38	Footkerchief	Note Added: 0000771
2010-04-11 18:35	Footkerchief	Tag Attached: Still Present in 31.03?
2010-04-11 20:24	Logical2u	Note Added: 0002958
2010-04-11 20:39	DoctorZuber	Note Added: 0002963
2010-04-12 12:36	Footkerchief	Note Added: 0003097
2010-04-12 12:36	Footkerchief	Status	new => resolved
2010-04-12 12:36	Footkerchief	Fixed in Version	=> 0.31.03
2010-04-12 12:36	Footkerchief	Resolution	open => fixed
2010-04-12 12:36	Footkerchief	Assigned To	=> Footkerchief
2010-04-12 12:40	Footkerchief	Status	resolved => assigned
2010-04-12 12:40	Footkerchief	Assigned To	Footkerchief => Toady One
2010-04-12 12:41	Footkerchief	Status	assigned => resolved
2010-04-12 13:12	Footkerchief	Status	resolved => assigned
2010-04-12 13:13	Footkerchief	Status	assigned => resolved
2010-04-12 13:13	Footkerchief	Fixed in Version	0.31.03 =>
2010-04-12 13:13	Footkerchief	Resolution	fixed => duplicate
2010-06-04 10:06	Footkerchief	Tag Renamed	Still Present in 31.03? => Fixed in 31.03?
2010-06-09 06:46	Toady One	Status	resolved => closed
2010-12-11 08:59	Dwarfu	Tag Detached: Fixed in 31.03?

Notes
(0000761) DoctorZuber (reporter) 2010-04-03 20:14 edited on: 2010-04-03 20:15	had a dwarf been tasked to haul the log already? if it's in use by another dwarf it's not available to build with.

(0000762) arcaner (reporter) 2010-04-03 20:16	Do you have a wood stockpile designated? If so there's a chance the logs have been tasked to the stockpile before you can request them for construction.

(0000763) Footkerchief (manager) 2010-04-03 20:18	I'm guessing this is yet another duplicate of 0000018, pathing weirdness, but if there's another explanation...

(0000764) Logical2u (manager) 2010-04-03 20:19 edited on: 2010-04-03 20:21	I don't have a wood stockpile. Forgot to mention that! Edit: That being said, even I personally suspect it's an issue with the pathfinding not resolving new objects quickly enough.

(0000766) dibujante (reporter) 2010-04-03 20:22	Since save&reload fixed it, it is probably a subset of our pathing problems. I have experienced this during bouts of poor pathfinding.

(0000768) DoctorZuber (reporter) 2010-04-03 20:25	I think you're right footkerchief, I'd go ahead and child it off of the pathing thread unless someone proves something different is going on here.

(0000770) Logical2u (manager) 2010-04-03 20:33	Whenever the trees grow back I'll try to replicate the issue. That being said, there were four logs that were 'invisible', and they were scattered across the map - so it seems like quite a long time had passed, in game. However, since it probably IS a pathfinding bug, Footkerchief, could you child this off of the main pathing bug? I'll PM you on the forums if I get any more evidence relating to this particular issue.

(0000771) Footkerchief (manager) 2010-04-03 20:38	Done. Child issues are still open, so you can keep adding notes here if you want (that would be preferable to PMs).

(0002958) Logical2u (manager) 2010-04-11 20:24	So, the same fortress that I uploaded for Toady that led to the fix on bug 0000070 was the same fortress that had this bug in it. So hopefully the two were connected in some way and both will be fixed!

(0002963) DoctorZuber (reporter) 2010-04-11 20:39	I figure I'll just wait and see what pathfinding behaviors crop up after 0.31.03. He fixed something. So one down, hopefully it'll be easier to make sense of the rest now.

(0003097) Footkerchief (manager) 2010-04-12 12:36	This and other issues are being marked resolved because they fit the symptoms of the general pathing bug described by issues 0000018 and 0000070. If this issue represents an additional bug, it will most likely present different symptoms in 31.03, and a new report should be submitted.