Unless you're getting errors in the log there isn't much I can do to investigate. You can try and see what mod is conflicting with mine if your modlist isn't too big.

Nah, for some reason it's not showing up in the log. Really weird. I was adding and removing mods and for some reason LightsOut is the one that brings out the error. I have another friend with a similar modlist I helped him with and your mod is working for him, so I'm guessing there are only a few mods I have that could be where the conflict is. I'll let you know if I find that.

I have ultrawide resolution, not sure that could be it. I just tried deleting all my inactive mods and still nothing and not sure what mod I am running that could cause that which my friend isn't. Hmm...

Wish I could help more. Doubt it has anything to do with your monitor’s resolution. My mod also doesn’t touch textures or affect rendering in any way, so it would be weird for it to cause an issue like this.

That's what I figured.....I presume it has to be some other mod that is fighting with this one. Thanks for your attention and I'll let you know if something comes to light.

Ditto to this, the entire screen is grey except for tooltips. Strangely enough, like OP mentioned, when pausing the game, all of the textures become visible again, but oncec the game is unpaused, then everything becomes grey again.

Also, even though this mod is tagged as "1.5" on the Workshop, it's still tagged as "1.4" within the game itself and says it's incompatible with the current version of Rimworld, even after completely uninstalling and reinstalling.

The only other mods I have active are "HugsLib", "Prepare Moderately", "Automatic Night Owl", "Allow Tool", "Ogre Stack", "TD Find Lib", "Everybody Gets One", "TD's Bug Fixes", and "TD Enhancement Pack", in that load order.

I have all DLCs active as well, if that matters.

It sounds like Steam didn’t update your version of the mod — it should report 1.5 compatibility.

When you launch the game, what version does LightsOut report in the log? 2023.2.18.0 was the last 1.4 version; the current 1.5 version is 2024.4.13.3.

If it still reports the 1.4 version you can unsubscribe/resubscribe to force Steam to update the mod.

I believe it did start with 2023 so that was most likely the case, yeah. I can't get the mod to update for whatever reason, even with unsubscribing / resubscribing / verifying game files both before and after un/resubscribing, but I don't think I'll be playing again until Fluffy's Colony Manager mod is working anyway so I'm sure this issue will be fixed by then.

Thanks for this mod though man, I've been using it since 1.3!

Wanted to resurrect this because the console log is still incredibly unhelpful but I'm fairly certain I found the incompatibility. Prepare Carefully, Prepare Moderately, and any intrusive mod that overwrites the base game code when you start the game will cause the grey screen problem. It doesn't always happen immediately, which has given me an unwarranted sense of security throughout my testing on numerous occasions, but it will eventually happen. I can't give any context as to what exactly causes the problem because my coding skills are null, I've just nailed the incompatibility down to these types of mods.

Do you have a log you can post for me to look through? I don’t know of any reason why those mods would conflict.

引用自 juanlopez2008：

Do you have a log you can post for me to look through? I don’t know of any reason why those mods would conflict.

Hey, I'm not the guy you just replied to, but I posted in this thread back in April about this mod having this issue; it's been fixed since then, I had to uninstall and reinstall Rimworld entirely and delete my Rimworld/Mods/ folder to have everything re-install properly and cleanly and that fixed this issue for me.

引用自 juanlopez2008：

Do you have a log you can post for me to look through? I don’t know of any reason why those mods would conflict.

Not on hand; I'll try to replicate the issue again later tonight after work.

i have an similiar error and for me i think its bc one of my pawns has the gene to never sleep that might be causing this error , i went to the debug log and i could confirm that it was this mod , this is the two logs that appear in the debug :

<color=orange>[LightsOut - Debug]</color> AllPawnsSleeping called on a null room
UnityEngine.StackTraceUtility:ExtractStackTrace ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Log.Error_Patch2 (string)
LightsOut.Common.DebugLogger:LogError (string,string)
LightsOut.Common.DebugLogger:Assert (bool,string,bool)
LightsOut.Common.DebugLogger:AssertFalse (bool,string,bool)
LightsOut.Common.Rooms:AllPawnsSleeping (Verse.Room,Verse.Pawn)
LightsOut.Common.Lights:ShouldTurnOffAllLights (Verse.Room,Verse.Pawn)
LightsOut.Patches.Power.PerformPendingShutoff:Prefix ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.TickManager.DoSingleTick_Patch4 (Verse.TickManager)
Verse.TickManager:TickManagerUpdate ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Game.UpdatePlay_Patch2 (Verse.Game)
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Root_Play.Update_Patch1 (Verse.Root_Play)

Root level exception in Update(): System.ArgumentNullException: Value cannot be null.
Parameter name: key
[Ref 3708EA9C] Duplicate stacktrace, see ref for original
UnityEngine.StackTraceUtility:ExtractStackTrace ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Log.Error_Patch2 (string)
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Root_Play.Update_Patch1 (Verse.Root_Play)

I’m not sure that has anything to do with genes, but that’s a good observation. PerformPendingShutoff is the code responsible for delaying turning off the lights when pawns change rooms.

Is this a chronic error, or just something that happens sporadically? Do you remember what was happening when the error came up — was it a raid, infestation, loading a save, etc…? Do you use a delay on the lights, or do you let them turn off immediately?

In any case, I just pushed an update that should prevent the crash moving forward.

I'd still like to know what scenario you were encountering it in, though.