After investigation it seemed to be related to a ChildActor being attached to the motion controller in construction script that failed both controller attachments without showing an error or warning message. Yesterday I did attached the Child Actor right before the batteries of the motion controllers went dead. Today I did not think attaching a child actor would be an issue but apparently it is. When I remove the ChildActor from the blueprint it worked again. Currently setting the actual blueprint to attach to the motion controller using a public property from the level blueprint (instead of a childactor) to the character blueprint and attaching it that way. It works…