Null Reference Exception on CS 2 load

[Novocastrian]

Hello,

Using v 1.4.7 of the Extra Lib mod, the game just crashed on the main screen after loading from another crash.

Error

NullReferenceException

Object reference not set to an instance of an object

NullReferenceException: Object reference not set to an instance of an object
at Colossal.Logging.UnityLogger.Internal_WriteStream (UnityEngine.Object context, Colossal.Logging.Level level, System.String format, System.Exception exception, System.IO.TextWriter stdStream) [0x0001f] in <ce885119459940bfa261d06fa84b46f4>:0 
at Colossal.Logging.CustomLogHandler.PostProcessFormat (UnityEngine.LogType logType, Colossal.Logging.Level level, UnityEngine.Object context, System.String format, Colossal.Logging.ILog log, System.Exception exception) [0x000d3] in <ce885119459940bfa261d06fa84b46f4>:0 
at Colossal.Logging.CustomLogHandler.LogFormat (UnityEngine.LogType logType, UnityEngine.Object context, System.String format, System.Object[] args) [0x0005e] in <ce885119459940bfa261d06fa84b46f4>:0 
Colossal.Logging.CustomLogHandler:LogException(Exception, Object)
Colossal.Logging.CustomLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:LogFormat(LogType, String, Object[])
Colossal.Logging.UnityLogger:Log(Level, String, Exception)
Colossal.Logging.UnityLogger:Info(Object)
ExtraLib.Debugger.Logger:Info(Object) (at C:\Users\TritonSupreme\Documents\__Code\ExtraLib\MOD\Debugger\Logger.cs:26)
ExtraAssetsImporter.OldImporters.DecalsImporter:GetRenderPrefab(String, String) (at E:\__CODE\ExtraAssetsImporter\MOD\OldImporters\DecalsImporter.cs:561)
ExtraAssetsImporter.OldImporters.<CreateCustomDecals>d__5:MoveNext() (at E:\__CODE\ExtraAssetsImporter\MOD\OldImporters\DecalsImporter.cs:159)
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)

Screenshots

The Help & Logs -> Save logs to file zip is attached.
LogReport_26-05-09_22-03.zip

[AlphaGaming7780]

Hey, thanks for reaching out.

Good news: this error is completely harmless. It doesn’t affect your game in any way. It comes from a long‑standing issue in the game’s own logging system that has been there since launch.

Why is ExtraAssetImporter mentioned in the log?
Simply because EAI logs a lot of information. Since it writes more entries than most mods, it’s statistically more likely to appear when the game’s logger glitches.

What can you do to fix it?
Unfortunately, nothing, there’s no real fix since the problem comes from the game’s internal logger. The important part is that it’s harmless and can safely be ignored.

As soon as you see the first line of the stack trace starting with:
at Colossal.Logging.UnityLogger.Internal_WriteStream
you can be sure the game’s logging system just had a momentary hiccup, and nothing else.