0002928: Crash on site selection in rectangular world

Notes
(0011711) Footkerchief (manager) 2010-08-11 02:15	Reminder sent to: starver Does this crash also produce "Midmap effective coordinate check out of bounds" in the errorlog?

(0011744) starver (reporter) 2010-08-12 08:49	There's nothing relevant in "errorlog.txt". To be precise, the only contents (from a previous, active, fortress) are pathing failures in Dwarf Mode that never noticeably perturbed me at the time.) Just to add the extra details, though, it's on the 43rd "west" key from initial starting position "longitude" on the map (at least it was when I tried it just now, and multiple times; regardless of which latitude I might have also shuffled to from the game-given default site roughly half-way up/down the somewhat squashed-and-stretched global map but somewhere around the first quintile from the left of it.) Appears to happen (my guess is) exactly when the middle-map display would stop scrolling left-to-right (i.e. leaving "X" at centre) and X would instead move towards the LHS upon it. (No problem going to extreme N, E or S. X shuffles right up to the RHS, top and bottom edges, with no problem.) I don't know if it relates to my observation that the site-map "X" (during Fortress play) doesn't line-up with where it is. i.e. you can (except, probably, at a small 'sweet spot' in the centre) see the shading of "planned designiation action" on the site-map off to one side. That's not a problem, though, and never causes a crash. Just an observation that seems to have a similar (though perhaps opposite) conversion problem when it comes to returning positions within an array limit. Can't say the background issue of 0001680 isn't related, of course. And I took the 0001859 behaviour as perfectly normal (world-sized view /has/ to stretch and skew, or else display in letterbox format, in such extremes as this). Thought it strange that Ringworld is only as wide the usual max-sized maps are both wide and tall, strange that it fails. It's probably also not as simplas as it being that on squarer maps an error of mixing up X and Y limits doesn't show up. Sorry too many words for little further enlightenment.

(0011760) starver (reporter) 2010-08-13 06:49	Probably final update, with additional info from some tests I should have carried out earlier, but only just got around to doing: I supplemented the original generated world ("Sn–nstrasp: The Oracular Planet") that was reported, by a second Ringworld from the same basic params[1] and a Vertical Ringworld version with the opposite extreme stretching but otherwise identical config. (Random seeds.) No crashing when heading to limits. I then put TOP's seeds[3] into both RINGWORLD and RINGWORLDV[ertical] generators (not expecting to get the-same-world-but-sideways, with the latter but maybe getting some similar features at an extremity) and no crashes on any of the extremities. No crashes. I actually did two RINGWORLDS [horizontal] with the original TOP seeds[4]. The output histories and sites_and_pops matched exactly (visually compared, only, but thoroughly so) with each other, as did the basic exported map, but there were some differences in the data/save areas[5] and no crashes encounted. If I had had more time, I would have transplanted the changed files around the various save folders to see what depended on each other and what might be the crash-inducing part. From the beginning, I've been working on the premise that this isn't a big problem, just an anomaly, and now it looks like I can safely ignore it and use /the same world/ anyway... [1] Zilirthur: The Eternal Universes [SEED:1269168925] [HISTORY_SEED:1259649055] [NAME_SEED:3530880022] [CREATURE_SEED:920544468] [2] Kenomonra: The Future World [SEED:1894815437] [HISTORY_SEED:2708407036] [NAME_SEED:2079204638] [CREATURE_SEED:2837223958] also: [DIM:17:257] [3] Sn–nstrasp: The Oracular Planet (obviously: same seeds for everything) [SEED:722245426] [HISTORY_SEED:3095621144] [NAME_SEED:2906513740] [CREATURE_SEED:3049399164] [4] Except I typoed the entry of the NAME_SEED, for one, getting a world named "Usnuspstrasp: The Ageless Planet", instead, but /everything/ else (i.e. worldgenned (e.g. site, civ, faction and creature names in the histories) the same. I don't know if the NAME_SEED only affect the world name, or how much this might have caused fluctuations in the savefiles. [5] feature-X-Y.dat files: Crashing version = 1-1, 1-2, 2-1 and 2-2; 1st non-crashing = 1-3 and 1-4, instead; 2nd non-crashing = 1-1, 3-1, 4-1, instead; Various unit-#.dat files had differing lengths. The world.dat files had different sizes (6,886,098, 6,885,838 and a figure I didn't remember to note for The Ageless Planet). I highly suspect that somewhere in there is the problem.

Issue History
Date Modified	Username	Field	Change
2010-08-02 06:02	starver	New Issue
2010-08-02 07:52	Footkerchief	Relationship added	related to 0001859
2010-08-11 02:15	Footkerchief	Relationship added	related to 0001680
2010-08-11 02:15	Footkerchief	Note Added: 0011711
2010-08-12 08:49	starver	Note Added: 0011744
2010-08-13 06:49	starver	Note Added: 0011760
2010-08-22 09:02	Footkerchief	Relationship added	parent of 0003084
2010-08-22 09:02	Footkerchief	Relationship added	parent of 0003035
2010-08-22 09:03	Footkerchief	Summary	Crash on site selection => Crash on site selection: msvcr90.dll, offset 0006c955
2010-08-22 09:03	Footkerchief	Relationship added	related to 0002754
2010-08-22 21:19	Footkerchief	Relationship replaced	related to 0003035
2014-07-27 12:36	Footkerchief	Summary	Crash on site selection: msvcr90.dll, offset 0006c955 => Crash on site selection in rectangular world