Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Terrain intermittently not visible, but does calculate correctly (v10) #123

Open
dineshm72 opened this issue Jan 1, 2023 · 1 comment

Comments

@dineshm72
Copy link

Describe the bug
Terrain which is added is not visible when a token is selected, or when a token is being dragged, regardless of the setting of "toggle terrain always displayed" or the "Show on drag" setting. If you keep clicking and dragging around, eventually the terrain may show up briefly, but then it will disappear again too. With multiple players and tokens, some will see it at times and others won't.

However, the terrain itself appears to be working, because the correct movement calcs are made when moving through the difficult terrain (using related mods).

Tested with just FTC, libWrapper, socketsettings, Enhanced Terrain Layer, Drag Rule, DnD5e Drag Ruler Integration, and Terrain Ruler.

To Reproduce
Steps to reproduce the behavior:
Create a terrain. (I set mine to water environment.)
Click on nearby token. No terrain is visible.
Drag token. No terrain is visible, but the movement calculation will be correct over the terrain.
Adjust the "toggle terrain always displayed" and "show on drag" settings. No change in the above behavior.

Expected behavior
Terrain should always be visible if toggle terrain always displayed is on. Or when dragging, if show on drag is on.

Screenshots
view on terrain layer:
image

view on token layer, no token selected:
image

view on token layer, token selected:
image

Please complete as much of the following information as possible:

  • Chrome
  • v10.291
  • D&D5e 2.0.3
  • Module version 10.6
  • Are there any errors in the console [e.g. press F12 and look for red text] - "A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received", but not sure it's relevant
  • Have you tried using Find the Culprit to make sure it isn't a module interaction. - yes
@dineshm72
Copy link
Author

Tried with both newly added terrain and terrain which was converted from v9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant