Good news: check-structures-sanity passed on linux64 (as part of trying to debug the above issue) so I think we can put up at least a beta release fairly soon for 0.47.05 here. Granted, the one structures change we've made would only have been caught on linux32, so there's not a guarantee that everything is perfect yet.
Yay, glad to hear good things came.
As for this: first off, thanks for the detailed report! A couple questions:
- Is it consistently reproducible if you look in the same spot in the same world? If so, could you upload the save and report an issue on GitHub? If the save is small enough, you might be able to attach it on GitHub while reporting it there.
- Have you made any mods / changes to the raws? I'm not sure if this would affect prospect, but it might.
Sorry for the delay - I was using CLA graphics which did make some changes to the raws so I wanted to rule that out (it didn't make a difference).
Also the save uses my custom worldgen and I had hoped to reproduce from a vanilla worldgen but the difficulty of finding 'any' single occurence diamonds got the better of my after trying a couple of times in two hour plus sessions. Not that it should make a difference - mentioned for completeness.
Yes it is consistent to the same spot in the same world.
Github issue created.
I uploaded the pre-embark save separately
on dffd (linked in above report).
If top left of map is (1,1) and embark rectangle is default 4x4 then
(1,25) with embark rectangle bottom right corner (diamond_blue 894 diamond_fy 128)
(65,41) with embark rectangle top left corner (diamond_blue 1287 diamond_fy 307)
(14,35) with embark rectangle centred (diamond_blue 704 diamond_fy 128)
are all locations to reproduce the issue (there are others...).
Numbers are a bit different to above since I was originally using a 3x3 embark rectangle as part of my personal init edits.