Crash Report

Post bug reports and ask for support here.

Moderators: elliotg, Icemania

Post Reply
sanderz
Posts: 866
Joined: Thu Jan 08, 2009 2:39 pm
Location: Devon, England

Crash Report

Post by sanderz »

Game crashed - was just scrolling out zoom i think

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: distantworlds.exe
Problem Signature 02: 1.9.5.0
Problem Signature 03: 5000a574
Problem Signature 04: mscorlib
Problem Signature 05: 4.0.30319.18444
Problem Signature 06: 52717edc
Problem Signature 07: 24d
Problem Signature 08: 18
Problem Signature 09: System.ArgumentOutOfRange
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
User avatar
elliotg
Posts: 3848
Joined: Mon Sep 10, 2007 9:32 am

RE: Crash Report

Post by elliotg »

Thanks for the report sanderz

Can you please check for a DW_CrashDump.txt file at the following location:
C:\Users\[YOURUSERNAME]\AppData\Roaming\Code Force Limited\Distant Worlds\1.9.5.0\
(replace [YOURUSERNAME] in the path above with your windows account name)

Please post the contents here.

Thanks
Elliot
sanderz
Posts: 866
Joined: Thu Jan 08, 2009 2:39 pm
Location: Devon, England

RE: Crash Report

Post by sanderz »

here you go.....

Distant Worlds - Crash Dump - 1.9.5.0

08:46:13 25 May 2014


System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at DistantWorlds.Types.ShipGroup.get_TotalOverallStrengthFactor()
at DistantWorlds.Types.Empire.IsShipGroupAvailableWithAttackStrength(ShipGroup shipGroup, BuiltObjectMissionPriority maximumPriority, Int32 overallStrength)
at DistantWorlds.Types.Empire.FindNearestAvailableFleet(Double x, Double y, BuiltObjectMissionPriority maximumPriority, Int32 overallStrength, FleetPosture posture, Boolean mustBeWithinFuelRange, Double fuelPortionMargin, Boolean mustBeAutomated, Boolean shouldBeSmallFleet, Boolean gatherPointMustBeBlank, Boolean mustBeWithinPostureRange, Int32 minimumTroopStrength, Int32 minimumBoardingStrength)
at DistantWorlds.Types.Empire.FindNearestAvailableFleet(Double x, Double y, BuiltObjectMissionPriority maximumPriority, Int32 overallStrength, FleetPosture posture, Boolean mustBeWithinFuelRange, Double fuelPortionMargin, Boolean mustBeAutomated, Boolean shouldBeSmallFleet, Boolean gatherPointMustBeBlank, Boolean mustBeWithinPostureRange, Int32 minimumTroopStrength)
at DistantWorlds.Types.Empire.FindNearestAvailableFleet(Double x, Double y, BuiltObjectMissionPriority maximumPriority, Int32 overallStrength, FleetPosture posture, Boolean mustBeWithinFuelRange, Double fuelPortionMargin, Boolean mustBeAutomated, Boolean shouldBeSmallFleet, Boolean gatherPointMustBeBlank, Boolean mustBeWithinPostureRange)
at DistantWorlds.Types.Empire.ReviewDefensiveFleetLocations()
at DistantWorlds.Types.Empire.DoTasksPirates()
at DistantWorlds.Types.Empire.DoTasks()
at DistantWorlds.Main.FdBUFMiRsEsr6rPG3GV(Object )
at DistantWorlds.Main.PY4TnI0la2(Object )


--- COMPLETE ---
User avatar
elliotg
Posts: 3848
Joined: Mon Sep 10, 2007 9:32 am

RE: Crash Report

Post by elliotg »

Thanks for that extra detail sanderz.

We'll fix this bug in the first update for DW Universe, which will be available in a few days.

Hopefully you can continue your game from a previous savegame. If you reload and continue, this error probably will not occur again. It's related to thread-timing (if you know what that is [:)]), and thus is pretty rare and doesn't reproduce reliably.

Sorry for that
Elliot
sanderz
Posts: 866
Joined: Thu Jan 08, 2009 2:39 pm
Location: Devon, England

RE: Crash Report

Post by sanderz »

ORIGINAL: elliotg

Thanks for that extra detail sanderz.

We'll fix this bug in the first update for DW Universe, which will be available in a few days.

Hopefully you can continue your game from a previous savegame. If you reload and continue, this error probably will not occur again. It's related to thread-timing (if you know what that is [:)]), and thus is pretty rare and doesn't reproduce reliably.

Sorry for that
Elliot

thanks for the update, look forward to the fix

had a recent save so no problem

cheers
Post Reply

Return to “Tech Support”