Jump to content

Recommended Posts

Posted (edited)
prefix	A crash occurred during the last session on 19/02/2026 19:00:09. A bug report zip file has been generated.
dateTime	2026-02-19-19h00
trigger	UnhandledException
message	NullReferenceException : A fatal error occurred during Update[] - Exception occurred during handling of [ 1698 Project Queue - File d’attente d’ingénierie, 131 Engineering Project - Blindage Protecteur [Common.Components.UnlockedStateMachineComponent] ] for controller engineering_project_available_row_component[Clone] of type AvailableProjectRowController - Object reference not set to an instance of an object - Exception occurred during handling of [ 1698 Project Queue - File d’attente d’ingénierie, 131 Engineering Project - Blindage Protecteur [Common.Components.UnlockedStateMachineComponent] ] for controller engineering_project_available_row_component[Clone] of type AvailableProjectRowController - Object reference not set to an instance of an object

 

 

bug_report_2026-02-19-19h00_st_7.1.0_unhandled_exception_0.zip

Edited by Damon
Posted
21 hours ago, Damon said:
prefix	A crash occurred during the last session on 19/02/2026 19:00:09. A bug report zip file has been generated.
dateTime	2026-02-19-19h00
trigger	UnhandledException
message	NullReferenceException : A fatal error occurred during Update[] - Exception occurred during handling of [ 1698 Project Queue - File d’attente d’ingénierie, 131 Engineering Project - Blindage Protecteur [Common.Components.UnlockedStateMachineComponent] ] for controller engineering_project_available_row_component[Clone] of type AvailableProjectRowController - Object reference not set to an instance of an object - Exception occurred during handling of [ 1698 Project Queue - File d’attente d’ingénierie, 131 Engineering Project - Blindage Protecteur [Common.Components.UnlockedStateMachineComponent] ] for controller engineering_project_available_row_component[Clone] of type AvailableProjectRowController - Object reference not set to an instance of an object

 

 

bug_report_2026-02-19-19h00_st_7.1.0_unhandled_exception_0.zip 5.57 MB · 0 downloads

Thanks for the bug report! We'll look into it

  • Like 1
Posted

I hit this crash to desktop as well in v7.2.0

 

In case this helps reproduce it, here's what had happened & what I did

  1. initial state: engineering screen was showing incorrect numbers for armour counts (disagreeing with the actual armour counts). not sure if this is necessary to trigger the crash  (reported that issue as its own bug)
  2. i opened armoury screen, unassigned all soldiers from dropship, then i assigned one soldier to dropship, and unassigned their armour
  3. then from armoury screen i opened the unassigned soldiers tab & applied an armour to the loadout of one of the unassigned soldiers
  4. then i wanted to check the engineering screen armour counts to see if they'd changed
  5. i clicked to open the engineering screen, game crashed to desktop

 

F11 bug report zip with initial state from before the crash (showing incorrect armour counts in the engineering screen):

bug_report_2026-02-21-16h29_st_7.2.0_user_f11_1.zip

Crash report zip

bug_report_2026-02-21-16h35_st_7.2.0_unhandled_exception_2.zip

Posted
On 2/21/2026 at 1:55 PM, fusion-waffle said:

I hit this crash to desktop as well in v7.2.0

 

In case this helps reproduce it, here's what had happened & what I did

  1. initial state: engineering screen was showing incorrect numbers for armour counts (disagreeing with the actual armour counts). not sure if this is necessary to trigger the crash  (reported that issue as its own bug)
  2. i opened armoury screen, unassigned all soldiers from dropship, then i assigned one soldier to dropship, and unassigned their armour
  3. then from armoury screen i opened the unassigned soldiers tab & applied an armour to the loadout of one of the unassigned soldiers
  4. then i wanted to check the engineering screen armour counts to see if they'd changed
  5. i clicked to open the engineering screen, game crashed to desktop

 

F11 bug report zip with initial state from before the crash (showing incorrect armour counts in the engineering screen):

bug_report_2026-02-21-16h29_st_7.2.0_user_f11_1.zip 6.04 MB · 0 downloads

Crash report zip

bug_report_2026-02-21-16h35_st_7.2.0_unhandled_exception_2.zip 5.62 MB · 0 downloads

Thanks for the report! We're currently looking into fixing the bug, but we'll take note of your repro steps in case we need more cases

  • Like 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...