Hi everyone

[Dracus]

After trying to find a replacement for SEV and finding Armada would not run correctly at all, I found distant worlds. bought all three. The game seems fun at the moment; even setting the raiders to low, the armada popping up behind my borders over one of my planets early game really kicked me good.

I like the game so far, but wish that the gas clouds would not show up in the mining list once a mine exist there, be it my mine or another race. It should be a list of last known, that way if a mine is distroyed it still does not show up unless you re-scout or send a construction crew there. Since they show up in the list, I have the game repeatly trying to send construction crews there just to turn back.

Also I think the game has a memory leak: after a number of re-loads, re-starts, or a few hours the game crashes and I have to launch it again.

[Bingeling]

There is something nasty about reloading games. I exit DW before switching to another save.

I am not sure about that constructor issue. Are they chased away by wildlife?

[Grisha]

I've also noted the weirdness with reloads. It does seem to work best if you clear out of the entire game first before attempting a second reload.

[ehsumrell1]

Guys, I believe Elliot will have this fixed in the soon to be released 1.7.0.2 update. [:)]

[Dracus]

thank you for responding, The ships go to a gas cloud cause you do not see a mine there, they find a mine from another race there and move off. Then later they head back to that gas cloud again just to find that same mine is still there.

[Bingeling]

It is strange, and not common. Usually the AI "instinctively" knows if there is a mine on a planet or not. Maybe tell the constructor to "stop" then automate it again to reset its stupid head?