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
I'm not sure this isn't by design, but when GM Vision is turned on with one token selected, it will show another token as hatched/not visible, even if the token should be heard/imprecise.
Example below. Selected token has 30ft blindsight, 60ft hearing. A token 40ft away shows as hatched when GM Vision is on, but shows as imprecise when it is off.
Since with the imprecise targeting you can't actually tell what the token is, perhaps this is a purposeful decision. But it seems weird that GM Vision actually hides info that would otherwise be apparent (that the token actually is imprecisely visible to the selected token).
GM vision on
GM vision off
Perhaps both the token and the imprecise overlay would be a reasonable signifier with GM Vision on if token is only imprecisely visible.
The text was updated successfully, but these errors were encountered:
I'm not sure this isn't by design, but when GM Vision is turned on with one token selected, it will show another token as hatched/not visible, even if the token should be heard/imprecise.
Example below. Selected token has 30ft blindsight, 60ft hearing. A token 40ft away shows as hatched when GM Vision is on, but shows as imprecise when it is off.
Since with the imprecise targeting you can't actually tell what the token is, perhaps this is a purposeful decision. But it seems weird that GM Vision actually hides info that would otherwise be apparent (that the token actually is imprecisely visible to the selected token).
GM vision on
GM vision off
Perhaps both the token and the imprecise overlay would be a reasonable signifier with GM Vision on if token is only imprecisely visible.
The text was updated successfully, but these errors were encountered: