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] Conflict with Isometric Module #104

Open
hiddenkrypt opened this issue Sep 20, 2023 · 1 comment
Open

[BUG] Conflict with Isometric Module #104

hiddenkrypt opened this issue Sep 20, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@hiddenkrypt
Copy link

hiddenkrypt commented Sep 20, 2023

Setup

  • OS: server: Ubuntu 22.04.1
  • Browser: firefox
  • Module version: Lockview 1.5.8
  • Foundry version: 10 build 303
  • Gaming system & version: Lancer 1.6.1
  • Any other modules enabled: Grape Juice Isometrics 0.10.291.2, LibWrapper 1.12.13.0 (required by iso)

Describe the bug
With the isometric module active, create a new scene and enable isometric mode. Then activate the Lock View Module. Even without turning on any lock view features for the scene, the scene is affected and the grid is displayed at a strange angle.

Screenshots
How it should look, shown with lock view disabled/uninstalled:
image

How it looks with Lock view active but not set on the scene:
image

This might be related to the 0 degree rotation option, which seems to be new. I set it to 90 and it is rotating it that way after applying isometric transforms. Correct behavior probably should be to apply no rotation if it's not active, rather than rotating it "0 degrees", but I haven't looked into your code to determine if this is the actual cause yet. Just my suspicion.
image

Console Log
No console errors

Additional context
I'm an avid user of both of these modules and have been using them for the last year without problems. I just did a big update to bring everything up to date and ran into this problem.

@hiddenkrypt hiddenkrypt added the bug Something isn't working label Sep 20, 2023
@hiddenkrypt
Copy link
Author

I just tried installing older versions of Lock View and found the bug exists in 1.5.7 but not 1.5.5 (couldn't install 1.5.6, seems to be a dead update) For now I'll be using 1.5.5 until this gets fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant