cleansweaper broken?

[lalala]

Runs to one end of the base, cleans one patch of dirt, leaves 10 dirty tiles around, runs to the opposite side of the base, cleans a dirt, ignores the 10 around, runs back again, all the time.

There are some patches it just never gets clean, they always dirty. There is no restriction to the area and they have access to it - no locked doors. They are set to work.

They used to work in another game before. I guess new bug or some condition changed that is unclear to me that cause them to not properly doing their job.


*update* now its just wandering as if there was no more job to do, but the designated clean area is dirty, but accessible and allowed... I suspect maybe the clean area mod isn't working properly anymore? But it worked just a game before. And it was after the last visible update...

[lalala]

Cleansweaper is not a mod, its biotech DLC mech.

[Narrowmind]

Ah, my mistake. Hadn't gotten to that bit yet.

[Limdood]

IIRC, dirt/blood/vomit/filth has to be on the ground for a minimum amount of time before it is eligible to clean. So if you follow a pawn around, and pause -> try to force clean a mess he made right after he made it, it won't be an option. Is it possible that the cleansweeper is occasionally cleaning the only valid "old enough" mess on a high-traffic, freshly dirtied area?

If it isn't that, are you running mods? there have been more than a few hiccups with mods in this last update, since it is still 1.4 and so 1.4 mods are still flagged as current. I know there was already an issue with Vanilla expanded framework that was affecting a few things that they fixed, but required a manual unsub, wait, and resub to force the new update into effect. You might try that with any larger mods or work/mech related mods you've got. Should take only a few minutes. If you take a few more, you can check the comments on each mod and see if there are any bug reports/complaints relevant to your issue.

AFAIK, the cleansweepers SHOULD clean just like anything else. By grabbing the nearest valid, unreserved mess and cleaning it. It's possible, though quite unlikely, that the messes left aren't valid. It's also possible, though again unlikely, that a different cleansweeper or pawn has already reserved those messes and is en route (I'm not sure, its possible that messes might be reserved in batches....so if a group gets reserved, but a new mess appears or becomes valid while the first pawn is en route, the sweeper might get there, clean the new mess, and leave before the first pawn arrives). So if it isn't either of those issues, and the cleansweeper is controlled, allowed, and has access (which you said it does), then its likely a mod issue or bug.

[lalala]

Thanks everyone.

I figured out the reason. Limdood's hint about not cleanable tiles for some time helped. Because that caused me to check back whether this is the case and I realized I was fooled by exactly that to think more than there is....

So there were tiles I checked they were dirty when mouse-over them. But I did not check every single one and they looked similar, so I thought its dirt, but they were not. But because the cleansweaper did not clean the tiles that were actually dirty near by, I thought he is not cleaning the many others too. But he did not clean the few dirty because for the reason Limedood explained (to fresh).

But after he said that I checked back and realized by right clicking ALL of them, not just few, not all the patches were actually dirt and those that were actually dirt not cleaned were to fresh. There is a certain working / schedule pattern that causes this weird chain of here dirt and there dirt, but some is to fresh to clean all of it....

*kabush!*