Maniphest T190207

Adding "Light" Entities to Object Spawner creates excessive log output.
Awaiting internal Testing, NormalPublic
Actions

Description

When adding any "Light" for example, "WarheadStorageLight" to an object spawner file, the server constantly logs

NULL pointer to instance
Class:      'WarheadStorageLight'
Entity id:3049769

Function: 'EOnFrame'
Stack trace:
scripts/4_World/entities\scriptedlightbase\pointlightbase\warheadstoragelight.c:73

And so on. When unchecked, this creates log files that are potentially 100GB plus causing Nitrado to flag and lock the service in question.

The simple fix is to remove the crash logging in warheadstoragelight.c and just have silent failure (I have not actually reviewed the file in question).

Sorry for opening this can of worms and unleashing it on the DayZ community! :D :D but we want lights!

Details

Severity: None
Resolution: Open
Reproducibility: N/A
Operating System: Windows 7
Category: General

Event Timeline

JinieJ created this task.Wed, Mar 19, 7:53 PM

Geez changed the task status from New to Awaiting internal Testing.Thu, Mar 20, 12:24 PM

JinieJ updated the task description. (Show Details)Thu, Mar 20, 6:43 PM

Here is the simple fix, check m_Bunker exists before applying dimming behavior / low energy behavior. Edge cases!

		if (m_Bunker && m_Bunker.IsLowEnergy() && !m_IsLowEnergyDim)
		{
			m_IsLowEnergyDim = true;
			GetDimming().SwapConfig(1);
		}
		else if (m_Bunker&& !m_Bunker.IsLowEnergy() && m_IsLowEnergyDim)
		{
			m_IsLowEnergyDim = false;
			GetDimming().SwapConfig(0);
			UpdateLightSourceMaterial(LIGHT_MAT_ON);
		}

Apparently, this is also an issue with "Goat Light" though I have not investigated that.

Adding "Light" Entities to Object Spawner creates excessive log output. Awaiting internal Testing, NormalPublicActions

Description

Details

Event Timeline

Adding "Light" Entities to Object Spawner creates excessive log output.
Awaiting internal Testing, NormalPublic
Actions