Skip to main content
K
KTMouse
Participant
October 3, 2022
Question

Internal asset numbering conflict

  • October 3, 2022
  • 5 replies
  • 2172 views

Latest version (v22.6) on Windows 10 (OS build 19044.2006) is suddenly showing the attached error message when I try and import an AEP into the current AEP.

 

Those AEPs were all created in the same AE installation on the same computer, and open fine in AE on their own. Only on import do they cause issues. 

 

The import does go ahead, but then throws out the positioning on layers in other previously imported (and previously fine) AEPs/Compositions.

For example a previous import of a character (made up of arm layer, leg layer, etc) rowing in a boat, those animated layers now appear spread out in the wrong positions in the composition.

 

No idea why, have had to roll back to previous AE installation which seemto work.

 

 

This topic has been closed for replies.

5 replies

nishu_kush
Community Manager
nishu_kushCommunity Manager
Community Manager
May 28, 2024

I'll move your post to the Discussions board while we await your information.

 

Thanks,

Nishu

S
Saariko2
Known Participant
August 27, 2023

Create a new project and import your old project into it, instead of opening the old project directly.
Fixed this issue for me.
FYI.

    R
    rittur83279004
    Participant
    August 16, 2023

    I'm also getting the same error. Even when you are importing a aep file with just one shape layer also it creates this problem.

    JohnColombo17100380
    Community Manager
    JohnColombo17100380Community Manager
    Community Manager
    October 17, 2022

    Hi @KTMouse,

    As mentioned by @Mylenium, could you please attach a project file that is showing the behavior you've described? That would allow us to best investigate this issue.

     

    Thanks for reporting and for any further information you can provide, 

    - John, After Effects Engineering Team  

    Mylenium
    Mylenium
    Legend
    October 3, 2022

    Without any specific info about your project(s) like actual layer names, comp structure and so on we can't really tell you much. Perhaps this is a similar thing to that bug in 22.5 where parenting info would be lost when importing projects referencing the same assets. Anyway, provide some screenshots of the timeline(s) and pertinent details and we may be able to get to the bottom of it.

     

    Mylenium

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices