Jump to content

Manual iron warp delivery crashes game


TheTT
  • Branch: Preview Branch Version: Windows Fixed

DxDiag.txt
The games crashes when the warp gates receives the same material after a moment of not receiving anything. 

 

Tested with oil and iron ore. 

 


Here is the data;  


 

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

WarpConduitReceiver.CanTransferFromSender () (at C:/jenkins_workspace/workspace/SimGame_Windows/game/Assets/scripts/game/Buildings/WarpConduitReceiver.cs:208)
WarpConduitReceiver+States.<InitializeStates>b__3_4 (WarpConduitReceiver+StatesInstance smi, System.Single dt) (at C:/jenkins_workspace/workspace/SimGame_Windows/game/Assets/scripts/game/Buildings/WarpConduitReceiver.cs:161)
BucketUpdater`1[DataType].Update (DataType data, System.Single dt) (at C:/jenkins_workspace/workspace/SimGame_Windows/game/Assets/Plugins/Klei/util/StateMachineUpdater.cs:96)
UpdateBucketWithUpdater`1[DataType].Update (System.Single dt) (at C:/jenkins_workspace/workspace/SimGame_Windows/game/Assets/Plugins/Klei/util/StateMachineUpdater.cs:79)
StateMachineUpdater+BucketGroup.AdvanceOneSubTick (System.Single dt) (at C:/jenkins_workspace/workspace/SimGame_Windows/game/Assets/Plugins/Klei/util/StateMachineUpdater.cs:152)
StateMachineUpdater.AdvanceOneSimSubTick () (at C:/jenkins_workspace/workspace/SimGame_Windows/game/Assets/Plugins/Klei/util/StateMachineUpdater.cs:244)
Game.SimEveryTick (System.Single dt) (at C:/jenkins_workspace/workspace/SimGame_Windows/game/Assets/scripts/game/Game.cs:1368)
Game.Update () (at C:/jenkins_workspace/workspace/SimGame_Windows/game/Assets/scripts/game/Game.cs:1344)

 


Steps to Reproduce

I have isolated the bug or at least to a fixed point. 

If you load the attached auto save and load the The Doomed Friends Cycle 272.sav
You will encounter the bug after 5 seconds from pressing play. You can still do stuff in the few seconds until 

 

 

 

 

DxDiag.txt

The Doomed Friends.rar




User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.

There are no comments to display.



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...