llSetPos movement not completing?

I'm having trouble with a door that uses llSetPos to move. It's part of a linkset and moves between two fixed positions without any rotation.

Problem is, the doors often (but not always) move most of the distance, pause, then move the rest of the distance, and sometimes they don't move that last bit. So, the door closes almost all the way but leaves a gap.

Anyone seen this? Any clues if it's fix-able?

That's SVC-1945. The workaround is to force a full update, with toggling a pair of llSetText values one of the popular ways.

I don't think it's SVC-1945. It's not an attachment, and it does move. It just doesn't always move enough, and sometimes it does complete its movement but not right away.

It's not only attachments, I have to use the exact same workaround on some doors.

Viktoria, do you have sliding doors with this problem, and are they linked?

I just tried making another change at the same time as the movement (I made a random color change) and it appeared to fix the problem, but didn't. From a reasonably close camera angle the movement seemed to become reliable, but from further away it got worse. From 30m away I can see a gap in a sliding door. It's that bad. When you zoom in it snaps shut.

Movement is happening in two phases: first the prim moves almost into place, then it pauses, and then it completes its movement. Only, it doesn't always complete its movement.

This doesn't happen to doors that aren't linked to anything. It only happens in linked sets.

I've added a comment to SVC-1945

Regression is an ugly word. It happens far too much.

/esc

Yeah, the glitch can show up on lots of things that move child prims, and it doesn't seem to be even limited to llSetPos, rotation changes can take a while to become apparent too. I've seen this on such simple things as plywood cubes, so there doesn't even seem to be any requirement for special shapes or placements to tickle the bug.

For common in-world examples that specifically involve child doors on buildings, you'll see this a lot on Ace's and Park Life prefabs. Those are not defective builds, several months ago they all worked fine. (Some people don't seem to notice this bug much if at all, but it you are experiencing it, this is a good variety of samples to look at.)