I have created my own SequenceComponent in C++ and attached it to MyCharacter. Here is the code:
UCLASS(ClassGroup=(Custom), meta=(BlueprintSpawnableComponent))
class TEST_API USequencerComponent : public UActorComponent
{
GENERATED_BODY()
public:
URGSequencerComponent();
UFUNCTION()
void Init();
UPROPERTY(Interp,EditAnywhere,BlueprintReadWrite,Category = "Sequencer")
int PropertyInt;
UPROPERTY(Interp,EditAnywhere,BlueprintReadWrite,Category = "Sequencer")
float PropertyFloat;
UFUNCTION(BlueprintCallable)
void MoveTo(FVector Location);
}
//Create in MyCharacter
AMyCharacter::AMyCharacter(){
SequencerComponent = CreateDefaultSubobject<GSequencerComponent>(TEXT("SequenceComponent"));
}
then I created a Blueprint, BP_SequenceActor, which acts as a dummy for edit the sequence. BP_SequenceActor inherits from Character and has a SequenceComponent added in the Blueprint.There is no logic other than. Here is the Blueprint:
Next, I created a LevelSequence and dragged the BP_SequenceActor into the scene. I added BP_SequenceActor to the LevelSequence and “convert to Spawnable” object. Then, I added a SequenceComponent (use +Track) to it and added a tag for binding replacement with MyCharacter at runtime.
I used the following Blueprint for binding and playing:
My expected result was that MyCharacter would execute the Track under the SequenceComponent, but it didn’t work as expected. To test it, I added an Event Track under the Object Track and a Track under the SequenceComponent Track. I printed the current object name at the start of the Play.and set “Allow Bindings from Asset” false.
The result showed that myCharacter was successfully bound, but I didn’t get the SequenceComponent.
I am aware that the documentation Note that You can bind Actors of different classes together, however you will only be able to access the components of the first bound Actor. However, my SequenceComponent should meet this requirement.
Does anyone have any thoughts or answers on how I might be able to do this? I can give more explanation if needed. Any suggestions or solutions would be greatly appreciated.