onTokenHover Errors

[carrierpl]

Since the implementation of the new token hover, I've seen issues where everyone connected to the session will see the following stacktrace:

Handler error:[string "CoreRPG:scripts/manager_actor_display.lua"]:501: attempt to index local 'cImage' (a userdata value) [string "CoreRPG:scripts/manage_actor_display.lua"]:501: in function <[string "CoreRPG:scripts/manager_actor_display.lua"]:497>

I'm not sure if this is a bad value being stored in the database, but the fix has been to restart the client, which seems to help for a little while. This seems to affect the GM and all connected clients, becoming worse as the session goes on. If anyone has a proper fix for this that would be greatly appreciated as it brings up the debug console constantly.

[Moon Wizard]

I'm not seeing this in my local campaigns.

Do you have a campaign where this occurs that you can zip up and provide?
Can you make sure that you are not running any extensions?

Regards,
JPG

[SteveStewart332]

I am seeing the same thing in multiple campaigns, as are my players. I am running a bunch of extensions - I will try and spend a bit of time running them down, but usually if there is an issue with the extension, it is quoted in the error message (I think, but absolutely not an expert!). It doesn't seem to happen straight away, but appears after a couple of hours of play.

[LordEntrails]

I am seeing the same thing in multiple campaigns, as are my players. I am running a bunch of extensions - I will try and spend a bit of time running them down, but usually if there is an issue with the extension, it is quoted in the error message (I think, but absolutely not an expert!). It doesn't seem to happen straight away, but appears after a couple of hours of play.

If you Compile Logs after the errors start occurring, it will help us track down the extension. The extension names are often not listed, but the function/file/graphic that causes the error will be and that often gives a clue as to the extension it is related to.

[Olmac1]

Having the same issue with my campaign.

[LordEntrails]

Having the same issue with my campaign.

Do the same thing, create a new campaign and use NO extensions. Test. Does the issue happen?
If not, go back to your campaign, disable all extensions and see if it happens.
If not, then enable sets of your extensions until you find which extension(s) are causing the problem. Then let the extension developer know.

[Moon Wizard]

@SteveStewart332, @Olmac1,

As mentioned in post #2, if you have a campaign that exhibits this issue, please disable all extensions; if it still occurs, please have the GM provide a zipped up copy of the campaign folder so I can recreate the issue locally.

Regards,
JPG

[Fingersome]

I'm also having this problem, and it seems to me it must be to do with one of the (many) extensions I use in my games. The error is hard to replicate as I'm not sure what triggers it, but it seems to be related to adding new creatures to initiative, or else having npcs roll initiative... annoyingly, I'm reasonably certain that removing all the extensions will solve this, but actually narrowing down which extension is causing the error is turning out to be a massive pain.

[Olmac1]

I'm also having this problem, and it seems to me it must be to do with one of the (many) extensions I use in my games. The error is hard to replicate as I'm not sure what triggers it, but it seems to be related to adding new creatures to initiative, or else having npcs roll initiative... annoyingly, I'm reasonably certain that removing all the extensions will solve this, but actually narrowing down which extension is causing the error is turning out to be a massive pain.

Yes, this is a terrible one to track down which extension it would be. On the bright side, my last session the error did not come up. It was believed to be either one of two things. One of Mad Nomads extension which he fixed by removing it from core, or a conflict with an extension that we used to mark token height. We did not realize that Fantasy Grounds put in their own method of doing the exact same thing. I had disabled the extension I was using as it was the only one I used that reacted with the token.

[Fingersome]

I ran a session on Sunday that had the kibosh put on it by this bug making things unplayable. I ran an un-modified version of the same campaign to see if I could proc the error, but it hasn't happened yet, so I'm leaning toward it just being caused by the Natural Selection extension. Especially since I can now reliably proc the bug using the following steps:

1- Open a map with tokens stacked on top of each other
2- Select one of the tokens, to open the token selection menu popup
3- Close the window
4- Reopen the window and hover over any token

Presto.