Description

Repro Rate: 3/3

This issue was reproduced in //UE5/Release-5.1 at CL 23058290.

This is confirmed to be a regression since the errors do not occur on the previous version and is regression tested on //UE5/Release-5.0 at CL 20979098.

Steps to Reproduce

Steps:

  1. Create a blueprint template project.
  2. In the Content Browser, click the Add button then select Cinematics > Level Sequence.
  3. Create a Python file with the following code:
import unreal
reg = unreal.AssetRegistryHelpers.get_asset_registry()
unreal.log(reg.get_assets_by_class(unreal.TopLevelAssetPath("/Script/LevelSequence.LevelSequence")))
  1. Make the output log visible.
  2. Go to Tools > Execute Python Script... then select the newly created Python file.

Actual Result: Results in errors.

LogPython: Error: Traceback (most recent call last):
LogPython: Error:   File "C:/Users/Jan.Yu/Desktop/my_script.py", line 3, in <module>
LogPython: Error:     unreal.log(reg.get_assets_by_class("LevelSequence"))
LogPython: Error: TypeError: AssetRegistry: Failed to convert parameter 'class_path_name' when calling function 'AssetRegistry.GetAssetsByClass' on 'Default__AssetRegistryImpl'
LogPython: Error:   TypeError: NativizeProperty: Cannot nativize 'str' as 'ClassPathName' (StructProperty)
LogPython: Error:     TypeError: NativizeStructInstance: Cannot nativize 'str' as 'TopLevelAssetPath'
LogPython: Error:       Exception: TopLevelAssetPath: Struct has 2 initialization parameters, but the given sequence had 13 elements

Expected Result: It should print out a list of Level Sequence Assets in the Output Log.

LogPython: [{object_path: "/Game/NewLevelSequence.NewLevelSequence", package_name: "/Game/NewLevelSequence", package_path: "/Game", asset_name: "NewLevelSequence", asset_class: "LevelSequence"}]

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-170724 in the post.

0
Login to Vote

Fixed
ComponentUE - Foundation - Core
Affects Versions5.1
Target Fix5.2
Fix Commit23496490
Main Commit23496490
CreatedNov 21, 2022
ResolvedJan 5, 2023
UpdatedJan 11, 2023
View Jira Issue