Game crash on select asteriod in interplanetary launcher

By Alexander Block

September 3, 2021

Branch: Preview Branch

Version: Windows

Fixed

Crash game if you select asteriod

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

ClusterMapScreen.UpdatePaths () (at C:/jenkins_workspace/workspace/Preview_Simgame_Windows/game/Assets/scripts/ui/ClusterMapScreen.cs:810)
ClusterMapScreen.UpdateVis (System.Object data) (at C:/jenkins_workspace/workspace/Preview_Simgame_Windows/game/Assets/scripts/ui/ClusterMapScreen.cs:599)
ClusterMapScreen.OnHoverHex (ClusterMapHex newHoverHex) (at C:/jenkins_workspace/workspace/Preview_Simgame_Windows/game/Assets/scripts/ui/ClusterMapScreen.cs:757)
ClusterMapHex.OnHover () (at C:/jenkins_workspace/workspace/Preview_Simgame_Windows/game/Assets/scripts/ui/ClusterMapHex.cs:151)
MultiToggle.OnPointerEnter (UnityEngine.EventSystems.PointerEventData eventData) (at C:/jenkins_workspace/workspace/Preview_Simgame_Windows/game/Assets/scripts/ui/Widgets/MultiToggle.cs:163)
UnityEngine.EventSystems.ExecuteEvents.Execute (UnityEngine.EventSystems.IPointerEnterHandler handler, UnityEngine.EventSystems.BaseEventData eventData) (at C:/jenkins_workspace/workspace/Preview_Simgame_Windows/game/Library/PackageCache/com.unity.ugui@1.0.0/Runtime/EventSystem/ExecuteEvents.cs:22)
UnityEngine.EventSystems.ExecuteEvents.Execute[T] (UnityEngine.GameObject target, UnityEngine.EventSystems.BaseEventData eventData, UnityEngine.EventSystems.ExecuteEvents+EventFunction`1[T1] functor) (at C:/jenkins_workspace/workspace/Preview_Simgame_Windows/game/Library/PackageCache/com.unity.ugui@1.0.0/Runtime/EventSystem/ExecuteEvents.cs:262)
UnityEngine.EventSystems.EventSystem:Update() (at C:/jenkins_workspace/workspace/Preview_Simgame_Windows/game/Library/PackageCache/com.unity.ugui@1.0.0/Runtime/EventSystem/EventSystem.cs:385)

Build: U35-477316-S

Июльское болото.sav

Steps to Reproduce

Load save, select asteriod in interplanetary launcher on Побегазон (third asteriod)

Followers 0

Go to bugs

User Feedback

3 Comments

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.