Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unreal: Fix Render Creator with new Level Sequence wrong sequence name #5728

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

simonebarbieri
Copy link
Member

Changelog Description

Fixed an issue with the Render creator when creating a new level sequence.

Additional info

The Level Sequence was named with the subset name, but the Level Sequence needs to be named as the asset, to retrieve information about the specific shot (frame range especially for the Validator).

Testing notes:

  1. Create a new Render instance with the option to create a new Level Sequence, and selecting the right asset.
    image
  2. Start a render for that sequence.
  3. Try publishing the render. The publish should be successful with no complaints from the validators.

@simonebarbieri simonebarbieri added type: bug Something isn't working sponsored Client endorsed or requested host: UE labels Oct 9, 2023
@simonebarbieri simonebarbieri self-assigned this Oct 9, 2023
@ynbot ynbot added the size/XS Denotes a PR changes 0-99 lines, ignoring general files label Oct 9, 2023
@LiborBatek
Copy link
Member

Did create Render Publish Instance for my shot sh020 and got the Publish Instance with name renderAnimationMain

image

Is that supposed to be like that? I guess it should contain the asset in the name...

It however did not failed and rendered ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
host: UE port to AYON size/XS Denotes a PR changes 0-99 lines, ignoring general files sponsored Client endorsed or requested target: AYON target: OpenPype type: bug Something isn't working
Projects
Status: Pending Review
Development

Successfully merging this pull request may close these issues.

None yet

4 participants