Skip to content

Medical Circulation - NULL pointer to instance in variable 'm_ACE_Medical_BrainHitZone' #405

@Roflino

Description

@Roflino

Bug Report: Server Timeouts & ACE Null Pointer Exception Related to Loadouts

Summary:
We have been experiencing recurring server timeouts for an extended period. During investigation, this issue appears to be مرتبط with an ACE-related null pointer exception, likely triggered by certain character loadouts.

Description of the Issue:

While troubleshooting repeated server timeouts, I consistently encountered a NULL pointer to instance error related to ACE medical systems.

The issue occurs when interacting with factions in the Workbench, particularly when previewing or loading character loadouts.

Observed Error (Log Extract):

Virtual Machine Exception

Reason: NULL pointer to instance. Variable 'm_ACE_Medical_BrainHitZone'

Class: 'SCR_CharacterDamageManagerComponent'
Function: 'ACE_Medical_UpdateResilienceRegenScale'

Steps Taken to Investigate:

  • Began debugging due to repeated server timeouts
  • Identified recurring ACE-related null pointer errors
  • Attempted to reproduce the issue via scripting
  • Initially suspected ACE itself as the root cause
  • Noticed that errors appeared when starting scenarios and previewing loadouts
  • Investigated arsenal configurations

Key Findings:

The issue appears to be مرتبط with specific arsenal character prefabs, including:

Character_USSR_Rifleman.et
Character_USSR_SL.et
Character_USSR_MG.et
Character_USSR_Medic.et
Character_USSR_GL.et
Character_USSR_AT.et
Character_USSR_AR.et
Character_USSR_AAT.et

Additionally, other (including vanilla-based) characters can also trigger this issue when used in factions.

Further Testing:
Removed the entire arsenal setup
Observed that the error persisted in relation to loadout handling
Logs indicate the issue occurs during loadout preview and initialization
Specifically linked to ACE medical components during character initialization
Workaround / Temporary Solution:

As a workaround, I replaced the default system with BaconLoadout, which prevented the issue from occurring.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugRelease Notes: **FIXED:**

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions