Strange crash

[bartomanboy]

I seem to get this error all the time after loading my savegame for a while.
I have no idea what it is, but it's kindof sad, since I can't continue my game as the error pops up at a certain time in-game.
A picture is added. The game version is Distant Worlds: Legends 1.7.0.6
I can upload the savegame somewhere if necessary.

[bartomanboy]

Just downloaded the 1.7.0.7 beta version and loaded the savegame. Which resulted in the same error.

[Kayoz]

You should ftp upload the offending save game file.

[bartomanboy]

Savegame has been uploaded to the server under the name of "Strange crash bartomanboy December 29 (1.7.0.6 & 1.7.0.7).dwg"

P.S. The crashdump


Distant Worlds - Crash Dump - 1.7.0.6

21:10:05 Thursday, December 29, 2011


System.NullReferenceException: Object reference not set to an instance of an object.
at DistantWorlds.Types.Empire.TakeOwnershipOfColony(Habitat colony, Empire newEmpire, Boolean destroyBases, Boolean destroyTroops)
at DistantWorlds.Types.Habitat.ResolveInvasionBattles(TimeSpan timePassed, Galaxy galaxy)
at DistantWorlds.Types.Habitat.DoTasks(DateTime time)
at DistantWorlds.Main.ophylqQI7sSgmeeKuqI(Object , DateTime )
at DistantWorlds.Main.dh3xvtC4jT(DateTime , Int64 , BuiltObjectList , Boolean )
at DistantWorlds.Main.ProgramLoop()


--- COMPLETE ---

[bartomanboy]

Just had the same error after playing a long time... In a newly started game. The savegame and error details can be posted, just send me a message.

[tomjoolz]

I'm getting the same crash in all of my games. Seems to happen whenever an ai empire goes down at the hands of another ai empire.

This sucks.

[bartomanboy]

You know what, I'm happy. Because I'm not the only one... lol
Soso, it's time to fix this, guys.

[Wyldwraith]

Getting the error myself. Dunno what more to do personally.
This is a critical issue, as it renders the game completely unplayable...
Hope they come up with a fix soon. These GxHab crashes are beyond old at this point.

[elliotg]

Thanks for the report and savegame. This is fixed in the upcoming 1.7.0.9 update