• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
11

Bug in expression Layer.outPoint with precompositions

Community Beginner ,
Nov 30, 2022 Nov 30, 2022

Copy link to clipboard

Copied

I've found a bug in the expressions which breaks some functionnalities in Duik (so it's a big problem and I can't find any workaround)
The value of `layer.outPoint` is not updated when the layer is a precomp which has been trimmed

 

1. Create a long comp "A", let's say 10s

2. Add it into another comp, "B"

3. Add an expression to any property using the layer "A" outPoint, just throw the value or display it on a text layer for example. I used this in the sourceText property:

 

var l = thisComp.layer("A");
"Layer outPoint: " + l.outPoint;

4. Trim or change the duration of precomp "A"
The value of the outPoint should change, but it does not

5. Edit the outPoint of the layer "A" (cut it), now the value of the outPoint is updated and it's the right one.

 

Here's a GIF to show the issue

 

outpoint_bug.gif

 

I have attached the project, as it is just after having trimmed the precomp, with the wrong value shown in the text layer.

 

I've searched a workaround but found nothing, the issue persists after reopening the project and/or purging cache.

 

Ae 23.0.0x59 and previous versions (tested on 2021 too)

Windows 11

 

Bug Investigating
TOPICS
Expressions

Views

608

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Dec 20, 2022 Dec 20, 2022

Thank you for reporting this issue, @Duduf | RxLaboratory. We are also able to reproduce this behavior, and now have a ticket open to investigate possible fixes for a future version of After Effects.

 

Thanks again,

- John, After Effects Engineering Team 

Status Investigating

Votes

Translate

Translate
2 Comments
Adobe Employee ,
Dec 20, 2022 Dec 20, 2022

Copy link to clipboard

Copied

Thank you for reporting this issue, @Duduf | RxLaboratory. We are also able to reproduce this behavior, and now have a ticket open to investigate possible fixes for a future version of After Effects.

 

Thanks again,

- John, After Effects Engineering Team 

Status Investigating

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 29, 2023 Nov 29, 2023

Copy link to clipboard

Copied

LATEST

This bug still exists in AE 23.6.0

Votes

Translate

Translate

Report

Report