Matrix Games Forums

Default theme , after 4 hours of 4x speed gameplay I left running over night to see if the default crashes I loaded up the last save and tried to see if I could replicate but I could not. Attached is a dxdiag


Distant Worlds - Crash Dump - 1.9.5.1

4:45:27 AM Friday, June 06, 2014


System.InvalidOperationException: Object is currently in use elsewhere.
at System.Drawing.Image.get_RawFormat()
at System.Drawing.Graphics.IgnoreMetafileErrors(Image image, Int32& errorStatus)
at System.Drawing.Graphics.DrawImage(Image image, RectangleF destRect, RectangleF srcRect, GraphicsUnit srcUnit)
at DistantWorlds.Controls.MainView.CVx2BFfm9IxqymEnTT4U(Object , Object , RectangleF , RectangleF , GraphicsUnit )
at DistantWorlds.Controls.MainView.PrepareGalaxyBackdrop()
at DistantWorlds.Controls.MainView.rXIhcoHW8QE(Graphics , SpriteBatch , Texture2D )
at DistantWorlds.Controls.MainView.DrawMainViewXna()
at DistantWorlds.Main.ProgramLoop()


--- COMPLETE ---


While trying another test leaving it on for roughly 2 hours at 4x speed I encountered this error
GXBO (Again This is with default theme no modding at all)

---------------------------
Error
---------------------------
An error has occurred. Distant Worlds will now exit.

Details of the error are below:

Error Code: GxBO

System.NullReferenceException: Object reference not set to an instance of an object.

at DistantWorlds.Types.ConstructionQueue.ProcessSingleConstructionYard(ConstructionYard constructionYard, TimeSpan timePassed, Galaxy galaxy, BuiltObjectList completedBuiltObjects)

at DistantWorlds.Types.ConstructionQueue.DoConstruction(Galaxy galaxy, DateTime tempNow)

at DistantWorlds.Types.BuiltObject.IndustrialProcessing(Double timePassed, Galaxy galaxy, DateTime time)

at DistantWorlds.Types.BuiltObject.DoTasks(DateTime time, Int64 starDate, Boolean inView)

at DistantWorlds.Main.KxUKNt8LSqlc5g53w9o(Object , DateTime , Int64 , Boolean )

at DistantWorlds.Main.itXiV17f8y(DateTime , Int64 , BuiltObjectList , Boolean )

at DistantWorlds.Main.ProgramLoop()
---------------------------
OK
---------------------------

This is fixed in the next update (1.9.5.3)

Thanks
Elliot