Open dubiousgit opened 3 months ago
Happens if you 'tokenize' from the compendium browser, or 'automatically' as part of a DDB import.
Tried on v11 and v12 of Foundry, both the same.
I cannot replicate this, please provide:
I cannot replicate this, please provide:
* Exact Foundry and system versions you are using.
The Forge, D&D5e 3.3.1, Foundry v12 Stable (build 331) Done in Firefox (doubt this matters)
* Have you tried with just Tokenizer module enabled?
Yes, other than 'The Forge' which I can't disable, still happens:
* Detailed step by step to replicate
Import monsters with D&D importer.
Select 'Tokenize' on import, or do it post-import by right clicking in the compendium.
957 monsters, if it matters.
I should note that I also tried this on a brand new world, same thing happened.
@MrPrimate for the sake of completeness, this is on a new world (test4, not that it matters) with a single import, and auto-tokenize on import:
If you import with out the auto tokenize selected, does it create a token?
If you import with out the auto tokenize selected, does it create a token?
Yes, and the token looks fine (in that it's the default, square one).
I can also manually add a token with tokenizer fine, though obviously that would be labour intensive.
Only when importing and ticking that box, or right clicking on the compendium and 'auto tokenizing' does it cause the corrupted image.
I do make use of the multi-world 'game manager' feature on Forge, maybe this is causing some sort of confusion with the assets? They share an assets blob as far as I can tell.
I have logged into my Forge account and can't replicate this - you've not run out of space or anything in your Assets folder?
What are the paths set to for tokenizer and ddb importer for saving images?
I have logged into my Forge account and can't replicate this - you've not run out of space or anything in your Assets folder?
What are the paths set to for tokenizer and ddb importer for saving images?
It's a new account, still have several gigs of space.
Paths are the default, (see assets screenshot above).
Is your Forge set to the 'Game Manager' mode?
Note 'test' was the first one I created, ever, which worked.
I also tried saving as PNG in case it was something weird with webp, but the same thing happens.
I have logged into my Forge account and can't replicate this - you've not run out of space or anything in your Assets folder?
What are the paths set to for tokenizer and ddb importer for saving images?
It's a new account, still have several gigs of space.
Paths are the default, (see assets screenshot above).
Is your Forge set to the 'Game Manager' mode?
I want to see the paths in the settings, as forge has its own unique way of specifying paths.
@MrPrimate these?
Can you try using Chrome for me rather than Firefox?
@MrPrimate I don't have Chrome specifically installed but I can confirm it worked in a Chromium-based browser!
Not really sure what to do about this one as it was working fine, until it wasn't...
Whenever I 'tokenize' an image now, it corrupts as seen in the screenshot.
This doesn't happen if you manually fiddle with the token (the top one in the screenshot) and create it without the automation.