Alternative to deprecated get_bound_objects ?

Development Pipeline & Plugins Editor Scripting
, ,
1

In Unreal 5.0 i wrote in my code following.
bound_objects = unreal.SequencerTools().get_bound_objects(bla,bla,bla)
And everything works well.

In Unreal 5.3.2 everything works well, but i receive a deprecation warning

DeprecationWarning: SequencerTools: Function ‘get_bound_objects’ on ‘SequencerToolsFunctionLibrary’ is deprecated: Function ‘GetBoundObjects’ is deprecated.

Ok. But there is no alternative was offered.

The question is:
What function i must use instead of “get_bound_objects”?

2

Also get_object_bindings also marked as deprecated. Which methods should i use instead?

3

Hey there @9Evgeny9! Welcome back to the community! Looks like that might have been moved to ULevelSequenceEditorBlueprintLibrary::GetObjectBindings

Deprecated * SequencerTools::GetObjectBindings has been deprecated because it doesn’t work with Spawnables, please use ULevelSequenceEditorBlueprintLibrary::GetObjectBindings which operates on the currently opened sequence in Editor

Is that still accurate?

4

You provide some C++ function, but i asked about Python replacements of get_bound_objects and get_object_bindings from this reference unreal.SequencerTools — Unreal Python 5.3 (Experimental) documentation

5

Apologies! I didn’t catch the Python tag on the original post. I’m unfamiliar with the Python API but I’d wager it follows suit (if it was updated that is). Does the respective functions work for this over on unreal.LevelSequenceEditorBlueprintLibrary? I couldn’t find any direct reference other than the aforementioned C++ docs mentioning the deprecation of the original calls.

https://docs.unrealengine.com/5.3/en-US/PythonAPI/class/LevelSequenceEditorBlueprintLibrary.html#unreal-levelsequenceeditorblueprintlibrary

6

Nope. Not work. Totally different set of function arguments.

7

Hey @9Evgeny9 , did you ever find a solution to this? I’m running into the same problem.

8

Hi @SpockPR1ME1,

Looks like this method is still working in 5.3, and has been marked for eventual removal. If you do not plan to update engine versions and plan to stay on 5.3 (or it looks like 5.4/5.5 as well), you should be safe to use this. Fingers crossed Epic updates the documentation when they eventually implement a new method- right now there isn’t any other way of doing this outside of Cpp.

As a side note- I believe the reason this was marked as depreciated is because it does not support Spawnables, as it looks like that was implemented into the Cpp version in 5.3.