This happened to me as well.
Commenting out this block in DefaultEngine.ini restored movement:
[RemoteSession]
+Channels=(Name=FRemoteSessionFrameBufferChannel,Mode=Write)
+Channels=(Name=FRemoteSessionInputChannel,Mode=Read)
+Channels=(Name=FRemoteSessionARCameraChannel,Mode=Read)
+Channels=(Name=FRemoteSessionXRTrackingChannel,Mode=Read)
Camera rotation did work briefly with these RemoteSession channels set up, but then failed on a subsequent run and couldn’t be used again without commenting the block out.
Anybody else have thoughts on this?