Build 765 does fix a lot of sprite issues
The delay with play was fixed also. [import]uid: 38820 topic_id: 22756 reply_id: 92454[/import]
Build 765 does fix a lot of sprite issues
The delay with play was fixed also. [import]uid: 38820 topic_id: 22756 reply_id: 92454[/import]
everything is fixed for me with my sprite sheets [import]uid: 86417 topic_id: 22756 reply_id: 92456[/import]
Just wanted to add on to what everyone said here. All fixed on mine too. [import]uid: 39846 topic_id: 22756 reply_id: 92481[/import]
Really happy to hear this, thanks for the updates all of you
Peach [import]uid: 52491 topic_id: 22756 reply_id: 92514[/import]
Unfortunately, I still have the scalebug and the delaybug with 765 [import]uid: 5942 topic_id: 22756 reply_id: 92553[/import]
@jbverschoor_bloomsix same here - back to āoldā sprite engine. [import]uid: 12704 topic_id: 22756 reply_id: 92567[/import]
@jbverschool_bloomsix / @gtatarkin, I believe that the āscalebugā is due to Frame Trimming not being supported yet, but itās on the way:
Frame Trimming Not Yet Supported
Something thatās missing from both Image Sheets and the new Sprite API is the ability to trim/crop frames in an image sheet, which is a common practice when it comes to constructing texture atlases. We are currently working on integrating this feature into the new APIās and will be rolled into the daily builds once itās ready.
Just wanted to point that out - it seems like itās less of a bug, and more of an item on the development to-do list. [import]uid: 49447 topic_id: 22756 reply_id: 92579[/import]
I had already disabled frame trimming in texturepacker. Iāll just wait patiently
Iām sure all will be fixed soon⦠Iāll keep reporting back with new daily builds [import]uid: 5942 topic_id: 22756 reply_id: 92584[/import]
I posted this on the Jonathanās blog post/new sprite API doc:
Build 764 ā Have not changed any code. spriteObject:setSequence() now works to reset sprite to first frame. However, calling spriteObject:play() after this does not play the animation again. Instead of being stuck on the last frame of the sequence, itās stuck on the first.
Also, spriteObject.frame = 1 does not work once the animation has completed. In fact, once the animation has completed spriteObject.frame returns 1 even if sprite is displaying the last frame of sequence.
Nothing has changed for build 765, same issues. Others have confirmed this behavior in the blog post comments.
If I need to file a bug for this I will, but this should be easy to spot and fix⦠[import]uid: 40137 topic_id: 22756 reply_id: 92755[/import]
Restless, can you please file this as a bug, including test case we can run to see the issue?
Easy or not it helps to have it in the system for tracking purposes and to make sure the best person for the job is dealing with it, etc.
Peach [import]uid: 52491 topic_id: 22756 reply_id: 92936[/import]
Itās fixed in 766 [import]uid: 40137 topic_id: 22756 reply_id: 93012[/import]