Empty Array of IMotionControllers for Unreal using Oculus Quest
The typical way of setting up a MotionController in Unreal Engine is through Blueprints, but I'm trying to identify different types of motion controllers for various VR setups and from there apply the orientation and position data. I have no problems getting Oculus Rift and Vive controllers and trackers using C++, but on Oculus Quest the array that's populated with IMotionControllers is empty when debugging over ADB. Why might this be? The following code will print a length of 0 on Oculus Quest only. const FName feature = FName(TEXT("MotionController")); TArray<IMotionController*> controllers = IModularFeatures::Get().GetModularFeatureImplementations<IMotionController>(feature); UE_LOG(LogGloveController, Warning, TEXT("Number of Controllers: %d"), controllers.Num());
Arc not working in UE4 with Occulus Go
The Arc on the motion controller is not working, it will only go to about how you see it in the image, and at the tip is this quickly rotating broken mesh that spins at the end, with bright cylinders slowly moving towards the end. This is using the VR Template in Unreal Engine, and nothing much is changed. I've tried looking this up, changing some things like SDK version, local to world in the arc function, checking collisions, checking nav mesh, and seeing if anyone has any videos of using the Go. Nothing! So I'm here, and I'm hoping someone has a fix.
Oculus Go and Accessibility
Hi, I've been developing content and the target users are people with disabilities. One issue I have run into with sessions is that the motion controller seems to be required to be held or the Go springs a message that it has lost it. This is impossible for some of my community with physical impairments. Is there a way to turn off the requirement for a motion controller, or at least suppress warnings. I am using the Samsung VR player with sideloaded videos in retail/demo mode.
