2D Toolkit > Releases

2D Toolkit 2.5.8.12 BETA (Updated 9 Apr)

(1/3) > >>

unikronsoftware:
BETA3 RELEASE - Unity 2018.3.7 required for this release
After reworking this numerous times, this is progressing in the right direction.

Keep in mind this is still a beta! Make backups before updating.

Fixed issues

* Edit functionality has been now fixed! Moved to 2D Toolkit / Edit menu.
* Font commit moved to menu, now works as expected
* Fixed issues with ui component prefabs not saving
Known issues

* Sometimes sprites don't update in the viewport, but will be sorted when the scene is re-opened

zblack:
I'm trying out the 2.5.8.12b2 build with Unity 2018.3.9f1. Sprite collections are committing and I can see the changes reflected in the scene. However, when I go back to edit the collection again it seems to be loading the old one? Sprites that I had removed/added/renamed are all back. Is there a cache for this being held somewhere?

habitoti:
This should be fixed with this Beta (open sprite collection through new „Edit...“ funtion in tk2d menu).

However, I had one or two occasions where it still happened again and added sprites where missing on later opening. It seems not to be 100% stable yet. However I couldn‘t reproduce it and find a stable root cause to report. For now I just check back immediately to not later forget what needs to be in the collection, and it is ok most of the time!

Please note that there is still one other issue in case you use platform support. If you change source graphics on the filesystem, Unity just updates the platform collection that is currently selected for the editor. The other(s) will be messed up. Make sure you finally re-check all supported resolutions explicitly and re-commit them in tk2d collection editor, if required.

Regards, habitoti

zblack:
There is definitely some kind of cache happening. I can quit Unity, restart, etc. and the new sprite I have set in the scene is still there - properly assigned. But when I open the collection with  the Edit menu, it's not visible in the collection.

habitoti:
The sprite in your scene comes from the generated atlas. This part is not the issue, as the atlas is generated once you commited the added sprites. The source metadata (the sprite you added to the collection and the settings you chose for it) is — still seemingly sometimes — not properly persisted in the collection prefab. That’s why it’s missing on the next opening of the editor. So it’s a design time issue, not a runtime one.

I have to say that it’s much better now if you take special care. At least there is a high chance you eventually end up with what you need (especially working with multiple res.-platforms). I’d prefer if we were back at the works-always-no-worries state of a few years back, but it was worse when I had to keep a list of newly added sprites to re-add them whenever another change was required. That was extremely error-prone and annoying. I’d probably give tk2d a pass by now if I’d not have “fallen in love” with so many of the great detail features it has...

Navigation

[0] Message Index

[#] Next page