René R
My feedback
2 results found
-
15 votes
An error occurred while saving the comment René R supported this idea · -
280 votes
Hi Everyone,
We have fixed this bug in our latest release – v 24.2.1 which is available worldwide now. Thanks for your patience on this.
Please note that after upgrading you might still see that Align To sets itself to Align to Key Object. If you see this, please manually set the Align To to the required setting, and this reported bug will not happen again. You’ll need to this one time only.
The reason Align To might get set to Key Object after update is because Ai remembers your last Align To on subsequent launches as well. So, if your last Align To was Key Object before quitting/upgrading, after first multi-selection, it will set itself to Key Object. After you manually change it one-time, it will work fine.
You can update to the latest release using Creative Cloud desktop App: https://helpx.adobe.com/in/creative-cloud/help/creative-cloud-updates.html
An error occurred while saving the comment René R commentedHi, the problem seemed to have been resolved for some time, although I did notice some strange behavior every now and then when using Align.
On closer inspection, this turns out to be the same behavior as Wes Rand wrote about on October 17: when I select multiple objects, I can only choose "Align to Artboard". This only seems to happen (or especially) when I select all objects at once by selecting a complete layer.
If I go back and select all objects individually, I get to choose from the other options "Align Selection" of "Align to Main Object".
I am using version 24.3, 64 bit, Windows, Dutch version.
I remember havingAn error occurred while saving the comment René R commentedAfter upgrading it works for me. Please note that you are using version 24.2.1, this version was not directly available in Dutch, perhaps that was also the case in other languages. See help / info in Illustrator for your version. Version 24.2 (without 1) does not work properly.
René R supported this idea ·
I'm experiencing this issue too. It is introduced in 29.1 (Windows 11).
I agree on both the Reproduction Procedure and the Workaround as monokano described. Thank you, monokano!