[A20] NullReferenceException and Electric Fence Posts

[Thunderbolt-GER]

Hello everyone,

PREFACE

I clean game data with the launcher on every major alpha release and did another clean before A20.5 (b2) stable, so it is unlikely that some obsolety leftovers are the cause.
We also wipe the dedicated server and start a fresh, new map with every major alpha release and we only install the stable releases.

THE BUG

I noticed the bug that opens the console and spams NullReferenceException errors because of electric fence posts is still there in alpha 20.5 (b2) stable.
It happened to me one day, when i was passing a players base on our dedicated server. I managed to enable DM and teleport away about a few 100 meters, by clicking on the map to teleport. So when i was far enough from that base, the errors stopped in the console and i could continue playing normally.

I also have one BM Base with 6 Electric Fence Posts connected in a chain, 2 trip wires connected to a dart trap which is chained to 5 more dart traps. All powered by a generator with 6 engines. (No solar involved)

When i tested the base for the first time, the console opened and spammed NullReferenceException errors as soon as the first zombie ran into the electric fence posts.

After killing all Zombies by spamming the F1 key and trying to aim+shoot and with the help of my Junkturret, the errors stopped as soon as no zombie was triggering the electric fence posts anymore.

So i rewired all electricity in my base, as i have read this tip a few times to fix this bug, but after rewiring the problem still occured in the same way. So i never did a bloodmoon in this base, because of this error.

Yesterday, i showed this base to another player and strangly i did NOT get any NullReferenceException errors, but the other player did!

A few 100 meters besides this base, i have another base with electric fence posts, were the NullReferenceException errors never occured (same electricity setup, but only with 4 instead 6 dart traps)

As far as i know, the FunPimps were never able to reproduce this error until now.

Does anyone else still get this error sometimes in A20 ? I had this bug happing since A17, if i remember correctly.

 

[Star69]

I never get errors. We have a square compound roughly 25 x 25 blocks and run one electric fence around the perimeter and never had any issues during horde night. We also run interior and exterior lights too. Oh and I have a single light bulb on the electric fence circuit mounted above the door. We know that when the light is on, so is the electric fence

 

[Beelzybub]

the FunPimps were never able to reproduce this error until now.

What steps do I take to reproduce this error?

 

[Jugginator]

There's an open ticket for this bug, but useful information you found there too.

 

[Thunderbolt-GER]

What steps do I take to reproduce this error?

If i knew how to repro, i would have created a real ticket. It seems pretty random to me, so i can not figure out exactly when or how it happens.

 

There's an open ticket for this bug, but useful information you found there too.

Oh, i did not see the ticket, i was assuming it was closed, since it could never be reproduced, since nobody found a way to repro it yet

 

[Jugginator]

Oh, i did not see the ticket, i was assuming it was closed, since it could never be reproduced, since nobody found a way to repro it yet

The ticket is internal. Correct, haven't been able to reproduce it at will. I do have a game save with the issue though, which is attached to the ticket for debugging.

 

[Thunderbolt-GER]

The ticket is internal. Correct, haven't been able to reproduce it at will. I do have a game save with the issue though, which is attached to the ticket for debugging.

Oh, that is good to know. Thank you for the info
Just wanted to make sure this issue will not be forgotten, because if it happens it is a complete gamebreaker

So, GOGOGO FUNPIMPS, you can do it

 

[Jugginator]

If you do have a reliable method of reproducing it, it could be useful to have though.

 

[Thunderbolt-GER]

If you do have a reliable method of reproducing it, it could be useful to have though.

Unfortunately i don't. It really seems to happen pretty randomly, so i don't even can make out the slightest indicator

I just remember right now, that somewhere in the past, when i had this bug, i also picked up all electric fence posts, placed them again and rewired, which did not fix the problem either.
I think it usually works again, when rejoining the server, but not always.
So pretty hard to find a pattern.

 

[peilo]

hi all.

i had this bug sometimes too in the previous alphas.

(different setups from bm-bases)

a few days ago it appears again to me in alpha 20.5 stable.

imo i have this probs only in bases with electric fences sometimes.

(with and without trip wire posts) *remember*

 

[peilo]

hi all.

i had this bug sometimes too in the previous alphas.

(different setups from bm-bases)

a few days ago it appears again to me in alpha 20.5 stable.

imo i have this probs only in bases with electric fences sometimes.

(with and without trip wire posts) *remember*

btw: i had this bug with windows 7 in the past and now with linux mint 20.3 too. i speak only from different servers, because of i never used e-fences in a single player game during the last 2 or 3 years. maybe this infos will help...? big thx for 7 days and stay healthy

 

[Torthan]

It happens for me too.

Situation - playing a co-op game hosted on someone else's computer. 

Electric fences are located at our horde base, hooked to a switch.

Land claim is mine, my partner set up the fences.   Other electrical at the base include spotlights, auto turrets (shotgun and SMG), and blade traps.

The following is the log excerpt from last night when it occurred most recently.

2022-08-06T00:28:51 16894.310 INF Time: 280.17m FPS: 29.40 Heap: 6783.0MB Max: 6862.3MB Chunks: 243 CGO: 167 Ply: 2 Zom: 0 Ent: 3 (71) Items: 0 CO: 1 RSS: 5416.4MB
2022-08-06T00:29:21 16924.346 INF Time: 280.67m FPS: 23.84 Heap: 6801.2MB Max: 6862.3MB Chunks: 243 CGO: 167 Ply: 2 Zom: 0 Ent: 3 (71) Items: 0 CO: 1 RSS: 5402.8MB
NullReferenceException: Object reference not set to an instance of an object
  at ElectricWireController.DamageSelf (System.Single damage) [0x000dc] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.touched (UnityEngine.Collider collider) [0x0019f] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.Update () [0x000b4] in <6a01347f98174dbdb41cb4a4eedf5af7>:0

NullReferenceException: Object reference not set to an instance of an object
  at ElectricWireController.DamageSelf (System.Single damage) [0x000dc] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.touched (UnityEngine.Collider collider) [0x0019f] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.Update () [0x000b4] in <6a01347f98174dbdb41cb4a4eedf5af7>:0

NullReferenceException: Object reference not set to an instance of an object
  at ElectricWireController.DamageSelf (System.Single damage) [0x000dc] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.touched (UnityEngine.Collider collider) [0x0019f] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.Update () [0x000b4] in <6a01347f98174dbdb41cb4a4eedf5af7>:0

NullReferenceException: Object reference not set to an instance of an object
  at ElectricWireController.DamageSelf (System.Single damage) [0x000dc] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.touched (UnityEngine.Collider collider) [0x0019f] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.Update () [0x000b4] in <6a01347f98174dbdb41cb4a4eedf5af7>:0

NullReferenceException: Object reference not set to an instance of an object
  at ElectricWireController.DamageSelf (System.Single damage) [0x000dc] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.touched (UnityEngine.Collider collider) [0x0019f] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.Update () [0x000b4] in <6a01347f98174dbdb41cb4a4eedf5af7>:0

NullReferenceException: Object reference not set to an instance of an object
  at ElectricWireController.DamageSelf (System.Single damage) [0x000dc] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.touched (UnityEngine.Collider collider) [0x0019f] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.Update () [0x000b4] in <6a01347f98174dbdb41cb4a4eedf5af7>:0

NullReferenceException: Object reference not set to an instance of an object
  at ElectricWireController.DamageSelf (System.Single damage) [0x000dc] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.touched (UnityEngine.Collider collider) [0x0019f] in <6a01347f98174dbdb41cb4a4eedf5af7>:0
  at ElectricWireController.Update () [0x000b4] in <6a01347f98174dbdb41cb4a4eedf5af7>:0

2022-08-06T00:29:51 16954.366 INF Time: 281.17m FPS: 25.40 Heap: 6832.5MB Max: 6862.3MB Chunks: 243 CGO: 167 Ply: 2 Zom: 0 Ent: 2 (71) Items: 0 CO: 1 RSS: 5423.2MB

Hope this helps!

It occurs for both of us.

Until it's fixed is there a way to disable the debug console altogether so it doesn't pop up in the meantime?

 

[NiteVIper]

I have something similar to that happening to me when im trying to load into the game and is at the creating character screen, i havent played on pc in a long time so thats a new one to me

Edit: Added a screenshot of whats happening to me( sorry if its posted in the wrong section)



Please make your own post and include a log file on pastebin.com please, thanks! @NiteVIper

-Jugginator

 

[Toneyst]

I fond the same issue in 20.6 (B9) 
some cable is error , some cable is not I will test one by one before using it.
Some one in party not face NullReferenceException Some one is face it.

 

My Log Log File 
Password : 7daytodie