#Token Nameplates Issues

1 messages · Page 1 of 1 (latest)

mortal zephyr
#

Blammo.
I do appreciate you being willing to help troubleshoot cause, uh.
"It crashes the canvas entirely" is not a good thing XD

summer dove
#

Absolutely my pleasure hahaha and I can see how that can be concerning lol

#

This is the broken canvas

#

And you can see that by hovering and dragging the token multiple times, the nameplate vanishes after a while, and switching scenes breaks everything.

#

I tried with canvas fade turned off and it does the same

#

Also, the issue with the rendering happens on a fresh world with just Token Nameplates active

#

I can't see if the broken canvas happens on a fresh world because I can't actually make the nameplate appear to see if it's causing issues (because I can't render the settings).

#

And just tested my 5e game and the same thing is happening, even the displaced nameplate

image.png
mortal zephyr
#

Well the first one is a trivial sort of fix, it turns out I just neglected to configure a template partial for the global configuration application
You should still be able to configure nameplate settings per token though, but that's a lot less convenient and not a great alternative

summer dove
#

This started after I updated to 13.351 btw

summer dove
mortal zephyr
#

The nameplate being displaced is ... hrm. I probably should change the default anchor point and sidestep that whole confusion point

summer dove
#

Interestingly though. I displaces the Nameplate that already existed before I updated, but a new one works normally:

image.png
#

I think I found the bad combo that cause things to implode

mortal zephyr
#

Did you update the module itself as part of updating Foundry?
Cause a module update last week added some ability to change how nameplates are positioned, so I suspect the old ones are just missing that data and the module isn't handling it gracefully like it should.
I'll add that to my to-do list for this week

summer dove
#

I did!

mortal zephyr
summer dove
#

The module itself is not throwing any errors

#

But it's causing Token Nameplates to implode

mortal zephyr
#

My guess, considering it's a stack size exceeded, is that they're both causing the other to refresh itself just ... infinitely

summer dove
#

But it is causing major freezes

#

Daggerheart HUD doesn't throw errors, but TN does, for some reason.

#

Which is likely why my 5e game is not breaking the canvas since the interaction doesn't exist there

#

This is the extent of my tech knowledge hahaha is there anything else that I can provide that might help?

mortal zephyr
#

And just to be certain, you've tried it without the Daggerheart HUD module active?

summer dove
#

Yup, I did. No slowdowns or anything of the sort. The only issue I found with fresh world + TN was the rendering of the settings outside of the token editor.

#

The errors just happen once I introduce Daggerheart HUD in the mix

mortal zephyr
#

Ok, so that seems pretty definitive that there's something in the interaction between the two.
I'm trying to replicate it on my end and not seeing it, which is going to make things tricky XD

The other two bits will be pretty trivial to fix, and I have some ideas I want to implement that should improve performance anyway, which I think will at least be in the right direction in regards to actually, you know, not crashing the canvas like that.

summer dove
#

Hahaha fair enough. Also, if it makes any difference, I'm using the Foundry desktop application. I haven't tested it on a browser. I don't even know if that would matter tbf e.e

mortal zephyr
#

I wouldn't expect it to

summer dove
#

I see! If I can send you any more evidence or screenshots, let me know. I could also send you an invite to the world at some point so maybe you can see what's going on

mortal zephyr
summer dove