Slow Token Movement

[pindercarl]

Since you have seen this on different maps and the GPU usage seems reasonable, I would check any extensions you have running. My suspicion is that the slow down is caused by an extension that affects tokens, or perhaps is linked to the combat tracker.

[JohnD]

I have noticed the following:

- if a token that is moving has the default lantern light source applied to it, movement is extremely slow even if there are no other light sources on the map. It seems like FG is redrawing the visibility at each 1/4 square of movement for not only the moving token, but indeed every other token on the map as well. The token literally chugs at 1/4 of a square at a time.
- if I approve more than one token to move at the same time, and one of the tokens has said lantern light source applied to it, all tokens approved for movement are extremely slow, regardless of whether or not the 2nd token has a light source or not.
- if I approve a token to move that doesn't have a light source applied to it, the token zips across the map to it's intended location. This can be right before the token(s) in the first two points are approved to move, or indeed right after they have finished moving.
- environmental light sources (i.e. not applied to a token) seem to make no impact to the movement one way or the other.
- if the map is broken up into multiple areas (i.e. the main floor of a building and the basement and 2nd floor are beside it on the same map, and you have tokens on multiple floors, movement for all tokens is extremely slow.

Edit: this is with tokens locked.

YMMV and all that.

Edit 2: I have started when working with maps that contain more than one "floor" on them, in addition to the LoS on walls, whatever, I put a LoS box around the whole section. Anecdotally this seems to have helped, but by no means is it conclusive in my eyes. I also add VISMAX: 75 to all CT actors with normal sight and up that to 90 for those with exceptional sight like elves.

[pindercarl]

I have noticed the following:

- if a token that is moving has the default lantern light source applied to it, movement is extremely slow even if there are no other light sources on the map. It seems like FG is redrawing the visibility at each 1/4 square of movement for not only the moving token, but indeed every other token on the map as well. The token literally chugs at 1/4 of a square at a time.
- if I approve more than one token to move at the same time, and one of the tokens has said lantern light source applied to it, all tokens approved for movement are extremely slow, regardless of whether or not the 2nd token has a light source or not.
- if I approve a token to move that doesn't have a light source applied to it, the token zips across the map to it's intended location. This can be right before the token(s) in the first two points are approved to move, or indeed right after they have finished moving.
- environmental light sources (i.e. not applied to a token) seem to make no impact to the movement one way or the other.
- if the map is broken up into multiple areas (i.e. the main floor of a building and the basement and 2nd floor are beside it on the same map, and you have tokens on multiple floors, movement for all tokens is extremely slow.

Edit: this is with tokens locked.

YMMV and all that.

Edit 2: I have started when working with maps that contain more than one "floor" on them, in addition to the LoS on walls, whatever, I put a LoS box around the whole section. Anecdotally this seems to have helped, but by no means is it conclusive in my eyes. I also add VISMAX: 75 to all CT actors with normal sight and up that to 90 for those with exceptional sight like elves.

In their last post, the OP said they were having the issue without LOS and lighting. However, given your observations, I'll take a look at the lantern scenario. There should be very little additional overhead for a token with LOS carrying a light source.

[Aramis Dante]

I have had a problem with this as well. I have some players overseas so I thought it might be just that. It is not consistent, usually when I try to move more than one token at a time.

[uMike]

So things have been running smoothly for a couple weeks now with the games I've run and played in not having any slow movement issues at all. Until tonight when I ran my Skull & Shackles game. The map in use had several of the Paizo flip tiles used to build it and I had put a cloud fx layer on it. Tokens were locked the whole time and no LOS or lighting in use. We had slow movement almost immediately, and it got worse every time a token moved. Closing the map and reopening it resets the problem for the person who reopened the map and they get to watch the movement degrade again. One player in this instance reported his GPU hitting 85 percent, so maybe that was it but we still don't know what caused that. I turned off the cloud fx but that didn't seem to change anything.

The degradation of token movement feels like a memory leak while the map is open, but I've yet to isolate the cause. And if the problem was another player's GPU load, would closing and reopening a map on a separate client be able to reset the issue for that client?

[Moon Wizard]

Did you try turning off the cloud FX layer to see if that was causing any issues?

Regards,
JPG

[uMike]

Yes, I removed the cloud fx layer and nothing changed. We still saw the degradation at roughly the same rate.

[Moon Wizard]

Can you provide a zipped up copy of your campaign, and the name of the Image record that was causing the issue?

Regards,
JPG

[uMike]

Should I post it here or is there a better place to send my zipped campaign?

[Moon Wizard]

You can post the link here; or send in to Support via the link at the top. It's up to you.
If you post here, then others can look at as well if they have time to look.

Regards,
JPG