Animated 'Tokens' asset behavior?

[Laerun]

I have tried to add a token of an animated acid breath to be useable as a dragon's breath weapon.
However, this behavior does not work as expected. Once dragged to a map, the layer is no longer accessible in any mode.
Observations:
- Grabbable space or area is too small or tiny to interact with. (Like 1/10th of the space to grab token asset on a map from.)
- Some tokens DO NOT behave like a token layer.
- Not able to interact with some token asset in ANY image mode.
- Acid Breath Token's File format is a .webm file VP8 animated token.
- FG v 4.5.2
Attached Image.
- DnDe Rule set
-Fairly new campaign session.
- Does work with a standard PNG image as a token asset. (Too small of a 'grab' interaction area.)
Noticed issue at: YouTube Video Example: ---> https://www.youtube.com/live/zTvT5qm...cX0-BPS&t=3513

screenshot0070.png

Trying to achieve this.
screenshot0070.png

[Moon Wizard]

Since these assets are in your Tokens folder, they will be treated as "token" objects when dragged and dropped on the map. Can you not click on the object to select it like other tokens once added?
If not, we'll probably need copies of the graphics for testing to pass onto Carl.

Regards,
JPG

[Laerun]

Since these assets are in your Tokens folder, they will be treated as "token" objects when dragged and dropped on the map. Can you not click on the object to select it like other tokens once added?
If not, we'll probably need copies of the graphics for testing to pass onto Carl.

Regards,
JPG

The intent was to use the asset as a token. This is for more flexibility and for not needing to unlock the map and adding additional and unnecessary layers for a more temporary effect or spell token.

[Moon Wizard]

If you can't select and interact with it like other tokens, we're going to need copies of the graphics you are using to test with.

Regards,
JPG

[Laerun]

If you can't select and interact with it like other tokens, we're going to need copies of the graphics you are using to test with.

Regards,
JPG

Okay, here you go...
Swamp_Campaign_Records.zip

The asset is included along with the campaign folder and the Console Log.

[Moon Wizard]

Carl has provided me with a fix already based on a separate report that will be made available in an update on Tuesday that he believes will also address this one.

Regards,
JPG

[Laerun]

Carl has provided me with a fix already based on a separate report that will be made available in an update on Tuesday that he believes will also address this one.

Regards,
JPG

Cheers.

[Laerun]

Cheers.

Still broken. Token selection tool works, manually selection does not work on a map for the 3D Animated token, used as a Token.

With FG v4.5.3

- DnD5e rule set.
- Token Selection Mode works on a map.
- Manual selection of clicking on an animated token does not allow for selection.
- Attaching new/fresh campaign for testing.
- Screen Shots included in the image folder, 3D animated asset used is in the tokens folder.

[Maasq]

Hi

I came to report the same issue. I am using a webm VP8 animated token. When added from the NPC's token display, it is completely unselectable on the map. This is in a fresh campaign with no extensions loaded for testing purposes.
Baron toth on the Discord channel suggested he'd met the same issue and a workaround was changing to 2.5D view and then back. Sure enough, this fixed things and made the token selectable.

I have downloaded todays update, btw, and had read about the fix to the same or similar issue with animated tokens. It is either a second, related, issue or the fix didn't work for all graphics.

Cheers
Maasq

[Vass_Dts]

Also came to report the same and to add the following tidbit: if you use the token select toggle button and draw a rectangle, you get to select the token. But right clicking it still ignores that it's a token, so I can't delete it. It does get deleted with 'delete all tokens' however.

EDIT:
Also, forgot to mention something else that is probably related. Tokens with transparency are only selectable on the part that has actual pixels (not in the transparent/alpha channel area).
EDIT2: Can confirm that the workaround that @Maasq mentioned does indeed work.