Issue: UNKNOWN VARIABLE SYSR_ELECTRICCHARGE

[theonegalen]

Here's a new problem: out of the blue, tonight, after working just fine last night and every night before, raster prop monitor computer stopped acknowledging the existence of the system resource variables. This, of course, had wide-ranging and devastating effects. The issue persisted with nothing but RPM, ASET, Squad, module manager, and my configs loaded.

Output_log.txt:

https://drive.google.com/file/d/1VFZhtaia3qfWYXRIm1TMsuaXggcow875/view?usp=drivesdk

[MOARdV]

I'm going to venture a guess it's related to this error:

OverflowException: Value too large.
  at System.Byte.Parse (System.String s, NumberStyles style, IFormatProvider provider) [0x00000] in <filename unknown>:0 
  at System.Byte.Parse (System.String s) [0x00000] in <filename unknown>:0 
  at ConfigNode.ParseColor32 (System.String vectorString) [0x00000] in <filename unknown>:0 
  at JSI.RPMShaderLoader+<LoadRasterPropMonitorValues>d__0.MoveNext () [0x00000] in <filename unknown>:0 
  at UnityEngine.SetupCoroutine.InvokeMoveNext (IEnumerator enumerator, IntPtr returnValueAddress) [0x00000] in <filename unknown>:0 

It looks like a custom color somewhere has a value of 256 or higher (or maybe a negative value) for one of its channels. Unfortunately, since I didn't know I needed to trap those sort of errors, I don't have any additional info. If you've changed or added custom colors recently, you might ensure the values are all in the range of 0 to 255. Otherwise, you'd need to search other files to find where the offending value is.

[theonegalen]

Ok! That actually narrows it down a lot.

[theonegalen]

Can you believe it? Hours of frustration because I typo'd a transparency number.