A few regressions in Animate 23 from 22

[BSB2018]

Hey everyone, just thought i'd post a few things i've ran into after updating to 23 over the last big project. These are things I did not really have a problem with in 22.

1. The asset warp tool is more unreliable

On multiple, larger warped assets spanning over 60 seconds long (at 30fps) of warped asset tweens, copying and pasting tween frames can randomly break the link to the asset with the tween. The warped asset will either change it's association to the next warped object in the layer below or above it, or the linked asset will show '---' and become invisible. Because there is currently no way to right click > swap warped asset with another like a symbol, the animation is corrupted. This doesn't happen on 22 when copying and pasting large warped assets.

2. Undos can become corrupted

Undoing when a history path includes entering an exiting a symbol can corrupt the undo history. Pressing ctrl+z past this point will start giving undesired behaviour, where undos in a symbol are being done on the main timeline or another symbol. (Animate did not enter or exit the symbol correctly through the undo history)

3. Animate is aggressively remembering selections per-frame.

Something introduced in 22 but seems to be even worse, this 'feature' remembers selections on a per-frame basis. Skipping between frames to view animations with ',' and '.' are difficult because the selection will show grey dots over your drawn work. You need to press ctrl+shift+a on every frame that remembers it has a selection.

Yes I know this is a community group. Please share any other regressions you've had in 23. I've had to return to 22 for my projects for now.

[kglad]

these are user-to-user forums.

 for applicable apps, you can make (some) suggestions to adobe here, https://helpx.adobe.com/ie/x-productkb/global/how-to-user-voice.html

for others, use https://www.adobe.com/products/wishform.html

[BSB2018]

"Yes I know this is a community group. Please share any other regressions you've had in 23. I've had to return to 22 for my projects for now."

Yes I know. I thought it would be useful to share my known issues here and ask others to do the same. It is extremely disheatening to not know about these issues, one that corrupts long animation, and lose days of work. Best that people know about this and at least avoid the Asset warp tool for large projects in 23. And to avoid using a long undo-history for now.

[CIRKUS]

Hi BSB2, 

Indeed, the Asset Warp Tool has been giving me trouble (probably from the software update?). Everything was fine during the project in early 2023, but I opened my files recently. The PNG & meshes are completely ''distort/torn'' now for no reason, cause I haven't touched it since.

Could this problem really come from software updates?

Or for another reason that you noticed on your side?

I'm trying to fix this problem for an important project.

Thanx

[kglad]

no update would change your old files unless opened and resaved with the update..

[CIRKUS]

Thanks kglag for your answer. In fact, I did not save in a more recent version, but only noticed the torn PNGs when simply opening the files.

[kglad]

they could have been damaged when saving with the older version.  there's nothing unusual with asset warp bugs and parenting bugs.

[CIRKUS]

I opened the files in different versions, still the same ''extreme'' mesh distortion bug. Strange, everything was OK during the project (with 22 version). And I read here a post ''A few regressions in Animate 23 from 22 version''. But even with the original working version (22), the problem remains the same. I'm going to do some tests again.

[kglad]

that's expected if the problem occurred when saving.  afaik, the only way to determine if you're saving a corrupt file is to save and reopen.

hence the recommendation to save frequently with increasing version number appended and periodically close and reopen the latest version.

only if it opens ok can you safely delete the older versions 

[CIRKUS]

yes, I often work with Animate (since Macromedia Flash in fact!!) and I save several versions as you say. I haven't really had problems since, until this one. I'm going to do other tests with several backup versions, I'll see if one of them works well, even if I've already tested a dozen versions. Thanx again kglad, appreciated : ) 

[kglad]

hope you find a working version.  but remember to prevent this in the future using version numbers.

[CIRKUS]

Thx kglad!! 

[kglad]

you're welcome.  hope you can update with good news.