same

me too
Could not regenerate layer DubsCentralHeating.SectionLayer_HeatingPipeOverlay: System.NullReferenceException: Object reference not set to an instance of an object
at DubsCentralHeating.PlumbingNet+<AllTileNets>d__22.MoveNext () [0x0009a] in <b8359cc4833c48838c1e239a6bcf9a45>:0
at System.Linq.Enumerable+WhereEnumerableIterator`1[TSource].MoveNext () [0x0004e] in <351e49e2a5bf4fd6beabb458ce2255f3>:0
at DubsCentralHeating.SectionLayer_PipeOverlay.Regenerate () [0x000c2] in <b8359cc4833c48838c1e239a6bcf9a45>:0
at Verse.Section.RegenerateAllLayers () [0x00023] in <81af9f8a18324e17b286924a43555a7c>:0
UnityEngine.StackTraceUtility:ExtractStackTrace ()
(wrapper dynamic-method) Verse.Log:Verse.Log.Error_Patch3 (string)
Verse.Section:RegenerateAllLayers ()
Verse.MapDrawer:RegenerateEverythingNow ()
Verse.Map:<FinalizeInit>b__143_0 ()
RimThreaded.LongEventHandler_Patch:ExecuteToExecuteWhenFinished ()
(wrapper dynamic-method) Verse.LongEventHandler:Verse.LongEventHandler.ExecuteToExecuteWhenFinished_Patch1 ()
Verse.LongEventHandler:UpdateCurrentSynchronousEvent (bool&)
Verse.LongEventHandler:LongEventsUpdate (bool&)
(wrapper dynamic-method) Verse.Root:Verse.Root.Update_Patch1 (Verse.Root)
Verse.Root_Play:Update ()

same here

this causes a lag everytime something is built

Also having this exact same bug.

So we all have the same bug. So what? Does Dubwise look over this or is someone reported or what ? I dont get the point of this stuff.

I got the same bug earlier. Not sure if Dubwise actually looks at these things.

is this fixed now?

I had the same bug, removing the performance optimizer mod fixed it

@TheGizmo which performance mod?

Getting the same bug, was there any fixes? I don't have any performance mods

Looks like I can claim this bug too. My guess is another mod's messing with it, but it'll take a little testing to see if I can find what.

Okay, after some testing, slotting this mod as early as possible in the load list seems to have fixed whatever was going on. I can't guarantee it'll work for everyone, but putzing around with the load order seems to be a fix in at least one case.

Originally posted by Luke:

So we all have the same bug. So what? Does Dubwise look over this or is someone reported or what ? I dont get the point of this stuff.

People report bugs in order to make developers aware of them. They do this in the hopes that the developer will fix the bug. Good developers value good bug reports because they can't find every bug themselves, or there would never be any bugs in the first place.

If you're specifically asking why everyone is corroborating the report, this is done to communicate that this is a major bug affecting many people, and likely a problem with the mod itself, not a conflict or load order issue. Many bugs will only ever affect a small number of people and most of those are caused by user error, so chiming in and making it known that many people are experiencing this conveys to the developer that it should be a high priority.

Finally, if you're asking why they made a discussion instead of a comment, that's a good question, since afaik comments notify the creator whereas discussions being created don't. My assumption would be that the log probably exceeds the comment character limit.

In any case this is all a moot point because this mod has not been updated in months. Unfortunately it seems the developer has abandoned it, or is at least is currently neglecting it, because many of the most recent comments reporting memory leaks have gotten no reply despite being a few months old at this point. I'm guessing this is probably because Dub is focusing on the main Bad Hygiene mod, which contains this. Shame too since I was looking forward to using this, but I don't really wanna deal with bathrooms and plumbing. Always thought putting 50 space heaters around my base was really dumb but alas.

Whilst helpful, the comment your replying to is 2 years old and I got a notification for it so maybe the mod owner does too.