-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Save Game Board Image Does Nothing #133
Comments
Could you try it with all other modules disabled? Also let me know what game system you're using. |
That did it. 5e with about a hundred mods. Luckily one of them is Copy Environment. Core Version: 9.269 System: dnd5e 1.5.7 (Atropos) Modules: List generated with Forien's Copy Environment: https://github.com/League-of-Foundry-Developers/foundryvtt-forien-copy-environment |
Ok, since it is a module conflict, could you run Find the Culprit to see which module is the one causing the problem? |
Sure, in a couple weeks when I get back from Burning Man. :) |
Hi there, @flamewave000 I had this same issue. Did Find the Culprit and the module that was conflicting for me was Fog Manager. I got the exact same "Cannot read" error as OP. However, OP did not list Fog Manager as one of their modules so I guess they have a module that works similarly to Fog Manager. |
For me, at least, the culprit was the Enhanced Terrain Layer module. |
Describe the issue
Clicking the button has no visible effect, no dialog, no saved image.
To Reproduce
Steps to reproduce the behavior:
Click on the button.
Expected behavior
The dialog appears and I can save the canvas image.
Screenshots (Optional)
Looking at the error in the console, I think it's because I'm looking at a scene that isn't the active scene. But making that scene active didn't resolve the issue. Refreshing the window after that didn't either. Error appears to be the same. Thought maybe it was that the map didn't have a background image, but adding one changed nothing. Same error in the console.
The text was updated successfully, but these errors were encountered: