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
Can't read Aseprite v1.3.5 (beta) file format #1082
Comments
Same problem here, can't work anymore with Aseprite 1.3.5 and Ldtk 1.5.3 |
For the workaround, now that the main Steam release is the 1.3.5 version, you can change which version you want installed by right clicking on Aseprite in your library, choosing "Properties" -> "Betas" -> "V1.3 - Previous Aseprite 1.3" to rollback to 1.3.2. |
I had a similar error trying to use tilemaps (#479). As soon as I changed my layer from a tilemap to a standard layer, LDtk v1.5.3 seemed to work with Aseprite v1.3.5. Tile positions and IDs appear to be consistent within Aseprite so long as one doesn't delete or move them. Unfortunately, the Aseprite "packed" output doesn't appear to be ordered by ID so I'm unsure if it's stable. It may be possible to write an Aseprite script to generate a stable PNG output that LDtk can read. |
Exporting by rows optionally with a fixed width appears stable. |
This should be fixed with this commit I made in I requested a merge to the official version: miriti/ase#4 |
Seem like aseprite devs just removed this beta from the steam version. RIP |
Aseprite 1.3.5 support was fixed here: miriti/ase@9e15258 It will be part of LDtk next fix |
Platform: Microsoft Windows [Version 10.0.22621.3155]
LDtk Version: 1.5.3-64bits (build 473703)
Aseprite Version: v1.3.5 (This is the v1.3 Beta version on Steam)
Problem Description:
When creating a new tileset from an Asprite file saved with Aseprite v1.3.5, LDtk fails to read the file.
Steps to Reproduce:
Test files: ldtk_aseprite.zip
tileset_v132.aseprite
- A file saved with Aseprite v1.3.2 that imports successfullytileset_v135.aseprite
- A file saved with Aseprite v1.3.5 that shows the above errorWorkaround:
Reverting to Aseprite v1.3.2 and re-saving the file allows it to import.
There is no extra information in the log that I could find related to the problem:
The text was updated successfully, but these errors were encountered: