ID:2195503
 
BYOND Version:511.1366
Operating System:Windows 7 Home Premium 64-bit
Web Browser:Chrome 55.0.2883.87
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:
So I set client.fps to 40 and call for mobs to follow me (walk_to(ref,trg)) at every 10 ticks, and they flick a lot! (This doesn't happen to me)

world
icon_size = 32
view="32x32"
fps = 20


Here are some gifs (sorry for poor quality):
Sideways

Diagonally


Expected Results:
Smooth, as it is without setting client.fps

Actual Results:
Flickering.

Does the problem occur:
Every time? Or how often? Every time
In other games? I assume so
In other user accounts? Yes
On other computers? I assume so

When does the problem NOT occur?
Happens every time :(

Workarounds:
None that I know of.

I can confirm that client.fps still has a bit of chop or clunk that only seems to happen to gliding objects periodically.
So to be clear here, the problem is that the pursuer isn't staying in sync with the pursued?
In response to Lummox JR
Yes
Okay, good to know. Assuming they're moving at the same time, there has to be something about the glide here that I'm missing. Any chance you could get this to happen in a simple test project?
In response to Lummox JR
I'll try sending you one in a few minutes.
In response to Lummox JR
Sent you a demo download link on PM.

Edit: If this could be adressed aswell (Mobs keep swaping locations wich eachother. Not sure why).
In response to NSBR
NSBR wrote:
Sent you a demo download link on PM.

Edit: If this could be adressed aswell (Mobs keep swaping locations wich eachother. Not sure why).

Am I the only one laughing out loud at this gif? Dude... the blue guy makes me feel sad
In response to Inutaishos
That's a representation of my life.
In response to NSBR
NSBR wrote:
That's a representation of my life.

We've all felt like blue or green people at some point in our lives.
In the demo, I see a lot of stuttering in the NPCs' movements if I'm not running; they're running themselves, which is generally causing their move routine to make them catch up to me quicker. If I change the running=1 line to running=M.running, that issue disappears, so I assume this is not part of the bug report.

The "swapping" isn't actually swapping; the mobs are simply finding other paths to the target that involve diagonal movements, and it's possible for those paths to cross. So no bug with that part.

What I am seeing, and this is gonna be a royal pain to diagnose, is that every now and then when I'm moving and they're moving after me, there's a "jump" where they all seem to fall out of sync with me. I'm not entirely convinced this isn't just an artifact of the weird NPC movement loop behavior; that NPCAI() routine coupled with NPCWALK() could simply be setting up a super weird timing scenario, since NPCWALK() doesn't maintain its own loop and NPCAI() sleeps for 1s every time.

So I'm seeing some jagged movement here, although I can't rule out some kind of timing sync issue caused by the movement logic. The next logical step is to add something that always tracks my position every time I move, in 1:1 sync, without any limitations on its own movement loop. If that gets out of sync with me, I'll know something is up.
In response to Lummox JR
Lummox Jr. wrote:
In the demo, I see a lot of stuttering in the NPCs' movements if I'm not running; they're running themselves, which is generally causing their move routine to make them catch up to me quicker. If I change the running=1 line to running=M.running, that issue disappears, so I assume this is not part of the bug report.

I changed the line like you said and I can still experience it. Here is another gif (I'm with running=0 on it)

As you can see, the mobs are still stuttering a little.

Lummox Jr. wrote:
The "swapping" isn't actually swapping; the mobs are simply finding other paths to the target that involve diagonal movements, and it's possible for those paths to cross. So no bug with that part.

But they're moving at the same time with the same speed to the same dir. I think this shouldn't be happening.
Edit: It seems to happen only when the mob and the usr are with different speeds and the mob reaches the min distance.

Lummox Jr. wrote:
What I am seeing, and this is gonna be a royal pain to diagnose, is that every now and then when I'm moving and they're moving after me, there's a "jump" where they all seem to fall out of sync with me. I'm not entirely convinced this isn't just an artifact of the weird NPC movement loop behavior; that NPCAI() routine coupled with NPCWALK() could simply be setting up a super weird timing scenario, since NPCWALK() doesn't maintain its own loop and NPCAI() sleeps for 1s every time.

I'm entirely sure it's not anything related to the movement loop since I've already tested it with different, big, time sleeps and with no loop at all.
JR, not Jr.
In response to Lummox JR
Lummox JR wrote:
JR, not Jr.

I literally laughed out loud reading this.
When I retested this with a change that forces other mobs to step in sync when I move, and removes their movement logic and restrictions entirely, the problem went away completely. That is, I made sure their moves were perfectly synced with mine, and as a result the glides were perfectly synced as well.

These are the specific changes, aside from commenting out all references to NPCAI and NPCWALK:
        // in atom/movable/Move():
if(istype(src,/mob/player) && next_move>world.time+0.001) return 0<

mob/player/Move(newloc,newdir)
. = ..()
if(.)
for(var/mob/M in orange(src))
step(M,newdir)

I'm quite certain now that if you hook up some output to this to say exactly when each mob moves, you'll have data that shows the glitches correspond to times when their moves did not happen at the same time as the mob they followed or at a consistent offset time.

However, here's where things get really interesting:

mob/player/Move(newloc,newdir)
. = ..()
if(.)
for(var/mob/M in orange(src))
spawn(world.tick_lag) step(M,newdir)

When spawn() is in play, the moves once again show a susceptibility to glitch out and go out of sync.

I think the next stage of testing will have to involve setting up a movement scheduler to see if I can eliminate any timing variables.
In response to Lummox JR
Any follow ups on this?
In response to Lummox JR
Still waiting on you :)