Start Recording Sequence Restrictions as of 4.16?

anonymous_user_7f2ebbc2 · August 17, 2017, 8:02pm

Start and Stop Recording Sequence blueprint nodes worked fine in 4.15, but as of 4.16 they produce a warning as my pawn in a non editor module? And in 4.17 it is an error instead of a warning. I tried changing my blueprint parent to VREditor clases such as the VREditorActor, and that fixed the error, but broke the VR setup. Any ideas?

Max.Chen · August 19, 2017, 4:13pm

What’s the warning/error that you’re seeing?

anonymous_user_7f2ebbc2 · August 21, 2017, 4:15pm

BlueprintEditorCompileResults:Warning: Warning Function in Editor Only Module ’ Stop Recording Sequence ’ cannot be called within the Non-Editor module blueprint base class ’ Pawn '.

LogBlueprint: Error: [Compiler …] Function in Editor Only Module ’ Stop Recording Sequence ’ cannot be called within the Non-Editor module blueprint base class ’ Pawn '.

Max.Chen · August 22, 2017, 2:31pm

Yeah, you’re right. Looks like those restrictions are in place for editor module BP functions.

Can you try executing the console command: “RecordSequence”. Arguments are:

all
actor [actorLabel]
class [actorClass]

For example: “RecordSequence actor CineCameraActor1”

anonymous_user_7f2ebbc2 · September 26, 2017, 2:04am

That worked great! Thanks for your help. For anyone wondering, the console command to stop is “StopRecordingSequence”