Could this be because the slight randomization of the nebula object positions sometimes puts those nebulae very close to each other and thus triggers the two-objects-same-space bug that has cropped up elsewhere in Artemis lately to give those Assert failures? (The bug being that if you put a second object too close to an existing object, it can sometimes cause the existing object to be "bumped" quite a ways away due to some sort of a mistake in the pushing algorithm. If the second object is *really* close to the first object sometimes that can mean it gets bumped all the way off the map thus triggering the assert failures complaining that pos.x or pos.z are out of bounds. The closer the second object is to the first object, the farther the bump. I had this problem all the time on version 1.651 but it seems to have died down on version 1.652.
[Last edited May 22, 2012 07:21:02]