Objective Marker Chips cause errors when ran on the first few ticks of a room

Bug Reports In-Game (Circuits, Logic, Building Blocks)
1

What device/platform are you having the problem on?

PC

Were you alone or with other players?

Alone

How often does the issue occur?

Everytime

Room Name

AwakenFields

Subroom Name

DevRoom

Reproduction Steps

  1. Have a circuit graph that modifies a list of objective markers that gets run on the first few ticks of a room loading (You can do this consistently with the update event)
  2. Save/Reload the room
  3. Errors should occur in the log file, but not be listed at all in the log screen

Description

Error looks something like this: Exception: [18:58:11] [66065] [1585.0487] [Exception] [Unity | Error] Object reference not set to an instance of an object.
at RecRoom.Core.Creation.ObjectiveMarker.UGCObjectiveMarkerHUDElement.GetCurrentDistance () [0x00000] in <00000000000000000000000000000000>:0

Discovered this while on my adventure to figure out why events were freezing up, and found some errors that aren’t getting logged here. Turns out objective markers aren’t initialized on the first few ticks of a room getting loaded, and can cause some errors and circuits to stop executing. Might start using the player logs to find the errors now lol