You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bug
Using a custom ring (not any of the options included in the module) results in all tokens being scaled down to about a half of their size (closer to 0.55)
See for example the default Foundry ring:
The Chasarooni AV ring:
My custom AV ring:
** Some context**
The custom ring and background images are both 2048x2048 (no other size is accepted). Changing the custom ring settings has no impact (as expected). Changing the ring to a non-custom one results in the token displaying correctly and vice-versa: in other words, the display issue is specific to the custom ring and does not persist when I stop using the custom ring.
The effect is observed in two different games running on different machines both running Foundry v12.331 with different versions of the PF2e system (6.8.1 and 6.2.2).
Token settings are default as imported from the compendium browser:
The text was updated successfully, but these errors were encountered:
The bug
Using a custom ring (not any of the options included in the module) results in all tokens being scaled down to about a half of their size (closer to 0.55)
See for example the default Foundry ring:
The Chasarooni AV ring:
My custom AV ring:
** Some context**
The custom ring and background images are both 2048x2048 (no other size is accepted). Changing the custom ring settings has no impact (as expected). Changing the ring to a non-custom one results in the token displaying correctly and vice-versa: in other words, the display issue is specific to the custom ring and does not persist when I stop using the custom ring.
The effect is observed in two different games running on different machines both running Foundry v12.331 with different versions of the PF2e system (6.8.1 and 6.2.2).
Token settings are default as imported from the compendium browser:
The text was updated successfully, but these errors were encountered: