BuildingBlocks not working for Matchmaking, Voice and how to do Teleporting!?
Edit: my bad, I had the interaction essentials package installed, rather than the interaction package, which has the teleport building block 🙂 all works now I was excited to see the buildingsblocks. However, they are a pain so far. First of all, once you start using them, you are completely dependent on them. OK. Problems arise when I want to add something basic as teleportation, there is no easy way to do this, because I have to somehow add it to the Building Block Camera Rig. I can´t take a rig from another sample, because that is not a building block. Adding all the teleport components is a huge pain and undocumented AFAIK. I cant get it working anyway. PLease turn this also into a building block then. What VR game doesn´t use teleportation!? Not so many. Then the "Auto" Matchmaking and Networked avatar. It simply does not work. As a long term dev, I know multiplayer is very hard. But if you present something as "building blocks", without further details or info, then you set the expectation that is JUST WORKS.338Views0likes0Comments
Spatializer error with new projects
When I import Oculus Integration and then import Oculus via XR Management in a new 2020.2 project I get the following error: GUID [a57801270cf689244b48012cf9db1713] for asset 'Packages/com.unity.xr.oculus/Runtime/Android/arm64/libAudioPluginOculusSpatializer.so' conflicts with: 'Assets/Oculus/Spatializer/Plugins/Android/libs/arm64-v8a/libAudioPluginOculusSpatializer.so' (current owner) We can't assign a new GUID because the asset is in an immutable folder. The asset will be ignored. Think this is a bug that needs to be solved, so we don't have to pick one of the files and delete the other.4.2KViews6likes7Comments
Fix for shaky/distorted objects in Right/LeftHandAnchor?
I'm no longer at the PC I use to develop, so I can't provide a picture of my problem. I'm using Unity 2017.4.0, or whatever the most current version is. So, I've had trouble getting items tracked by the touch controllers to display properly. Using the Unity Utilities 1.19, Oculus Platform SDK 1.19, and Avatar SDK 1.16, I am trying to display the avatar hands to in my scene. Everything works fine at first, but the avatar hands start to shake and become increasingly more shaky as the scene goes on; it almost looks like a mirage as it gets more distorted. It also does the same for child objects of the Left/RightHandAnchors of the OVRCameraRig prefab. For example, when attaching a cube to the RightHand, I'm able to move it around as normal using the controller. It looks like a normal cube at first, but then starts shaking and become more distorted and mirage-like. I have no idea what might cause this to happen, and I'm so close to having the TouchControllers set-up otherwise.6.8KViews0likes11Comments
Rare Crashes
As our product matures my team and I are starting to work toward stabilizing it. It had some issues that we cleared out. But there are some issues that are hard to track. We are using Unity with Oculus Integrations. The application is relatively stable but still has some issues. One thing is that the apps sometimes: - crash and close - freeze - present black screen but continue to work - crash on startup These seem to happen more often in smaller rooms with less distinguishable features or on places with a lot of people traffic. The app would sometimes crash on startup or resume. Or freeze in the middle of an experience. We have tried to collect crash logs but most of the time the crash logs will indicate that the app tried to "resume" and the ActivitiManager is killing it due timeout. Sometimes the app will go on background and present "tracking lost" overlay and then crash when going back. Here is some accompanying adb traces that we have managed to capture. *** This seems to happen when tracking dies: 2019/11/26 13:03:16.032 14466 14632 Warn [CT]: VIPER: StateBuffer: Could not get velocity from buffer. Not currently tracking in 6dof. 2019/11/26 13:03:16.033 2561 2561 Debug SurfaceRender: [com.oculus.ovrmonitormetricsservice.SurfaceRender@aaa61d] Not running, shutting down render thread 2019/11/26 13:03:16.033 2561 2561 Debug SurfaceRender: [com.oculus.ovrmonitormetricsservice.SurfaceRender@aaa61d] Shutdown Rendering. 2019/11/26 13:03:16.035 2561 2561 Info SurfaceRender: [com.oculus.ovrmonitormetricsservice.SurfaceRender@aaa61d] exiting 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.038 1858 1923 I [OAR] HttpClient: Append 2019/11/26 13:03:16.038 1858 1923 Info PanelUtil_JNI: Using caller's JNIEnv 2019/11/26 13:03:16.041 14466 14611 Info SyncBossInput: [lcon () d041cfbdxxxxxxxx]: 83532853 [info ] {THDG}: active_seek -> active_connected 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.052 1858 1923 I [OAR] HttpClient: Append 2019/11/26 13:03:16.052 1858 1923 Info PanelUtil_JNI: Using caller's JNIEnv 2019/11/26 13:03:16.056 2016 2074 Debug OculusFbPermissionsContentProvider: Package(s) are not FbPermission signed: '[com.android.keychain, com.oculus.os.vrmtpapp, com.oculus.vraudiodatadumpmanager, com.oculus.inputmethod.pacific, com.android.wallpaperbackup, com.oculus.micservice, com.oculus.externalstorage, com.qualcomm.timeservice, com.oculus.unifiedtelemetry, com.oculus.os.chargecontrol, com.qualcomm.wfd.service, com.oculus.vrpowermanager, com.oculus.vrcast, com.oculus.os.settings, oculus.platform, com.android.settings, com.oculus.location.geocoder, com.oculus.companion.server, com.oculus.wifiindoze, android, com.oculus.os.vrlockscreen, com.oculus.preloader, com.android.inputdevices, com.oculus.vrdesktop, com.android.providers.settings, com.oculus.gatekeeperservice, com.oculus.vrshell.desktop, com.android.location.fused, com.oculus.bugreporter, com.oculus.deviceauthserver, com.oculus.vralertservice, com.oculus.linefrequencyservice, com.oculus.headsetsfx, com.oculus.os.clearactivity, com.oculus.notification_proxy]') 2019/11/26 13:03:16.061 14466 14633 Error [CT]: FATAL: Fatal error 2019/11/26 13:03:16.061 14466 14633 Error [CT]: boltlib: Failed to close domain 2019/11/26 13:03:16.064 14466 14633 Error [CT]: FATAL: 0 /libMontereyTracker.so 0x0000007fab94a644 0x0 + 548339492420 2019/11/26 13:03:16.064 14466 14633 Error [CT]: FATAL: 1 /libMontereyTracker.so 0x0000007faae0bcf0 std::__ndk1::basic_string<char, std::__ndk1::char_traits<char>, std::__ndk1::allocator<char> > visionlog::logFatalError<char const (&) [15], char const (&) [32]>(char const (&&&) [15], char const (&&&) [32]) + 312 2019/11/26 13:03:16.064 14466 14633 Error [CT]: FATAL: 2 /libMontereyTracker.so 0x0000007faae0b954 void visionlog::doFatalError<char const (&) [32]>(char const (&&&) [32]) + 40 2019/11/26 13:03:16.064 14466 14633 Error [CT]: FATAL: 3 /libMontereyTracker.so 0x0000007fab7f9514 bolt::StatelessFastRPC::waitInvokeInternal(std::__ndk1::basic_string<char, std::__ndk1::char_traits<char>, std::__ndk1::allocator<char> >, std::__ndk1::function<int ()>, bolt::StatelessFastRPC::ExtraArgs) + 1516 2019/11/26 13:03:16.065 14466 14633 Error [CT]: FATAL: 4 /libMontereyTracker.so 0x0000007fab7fa04c bolt::StatelessFastRPC::waitInvokeAsync(int) + 1228 2019/11/26 13:03:16.065 14466 14633 Error [CT]: FATAL: 5 /libMontereyTracker.so 0x0000007fab10ea6c viper::monterey::initializePyramids(gsl::span<perception::ImagePyramidBase<unsigned char, perception::ImageHalfSample3x3>* const, -1l>, perception::ImageHalfSample3x3::Parameters const&, perception::ImagePyramidInitializationState, void (*)(bool, void*), void*) + 92 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 6 /libMontereyTracker.so 0x0000007fab10a9dc 0x0 + 548330842588 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 7 /libMontereyTracker.so 0x0000007fab0f2294 perception::ImagePyramidInitializerBase<perception::ImagePyramidBase<unsigned char, perception::ImageHalfSample3x3> >::ensureInitialized(gsl::span<perception::ImagePyramidBase<unsigned char, perception::ImageHalfSample3x3>* const, -1l>) + 204 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 8 /libMontereyTracker.so 0x0000007fab45e328 viper::VideoFrames::ensureImagePyramidsAreInitialized(gsl::span<viper::VideoFrame const, -1l>) + 260 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 9 /libMontereyTracker.so 0x0000007faad6939c viper::StereoInitializerHandler::addFrames(viper::VideoFrames const&, TooN::SO3<double> const&, viper::StateBuffer const&) + 448 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 10 /libMontereyTracker.so 0x0000007faacf6fb0 viper::Slam::Impl::track_initial_features(viper::VideoFrames const&, viper::ImuMeasurements const*, TooN::SO3<double> const&, boost::optional<TooN::Vector<3, float, TooN::Internal::VBase> > const&) + 100 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 11 /libMontereyTracker.so 0x0000007faacec7b8 viper::Slam::Impl::process_frames(viper::VideoFrames const&) + 280 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 12 /libMontereyTracker.so 0x0000007faad0ca7c viper::VideoFrameAnalyzer::Impl::process_frames(viper::VideoFrames const&) + 1764 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.066 1858 1923 I [OAR] HttpClient: Append 2019/11/26 13:03:16.066 1858 1923 Info PanelUtil_JNI: Using caller's JNIEnv 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 13 /libMontereyTracker.so 0x0000007faad08888 viper::VideoFrameAnalyzer::Impl::on_frames(perception::IdTmpl<unsigned int, perception::slam::FrameSetIdTag, false>, gsl::span<unsigned char const* const, -1l>, viper::LiveTimestamp, gsl::span<double const, -1l>, gsl::span<double const, -1l>) + 924 2019/11/26 13:03:16.066 14466 14633 Error [CT]: FATAL: 14 /libMontereyTracker.so 0x0000007faac65d64 coretech::InsideOutTrackingEngine::onImageData(gsl::span<VisionImageData const, -1l>, visiontypes::Timestamp<TheProcessingClock>) + 936 2019/11/26 13:03:16.067 14466 14633 Error [CT]: FATAL: 15 /libMontereyTracker.so 0x0000007faac603c4 0x0 + 548325950404 2019/11/26 13:03:16.067 14466 14633 Error [CT]: FATAL: 16 /libMontereyTracker.so 0x0000007fab759f20 0x0 + 548337458976 2019/11/26 13:03:16.068 14466 14633 Error [CT]: FATAL: 17 /libtracker-devices.so 0x0000007faa1dcb38 0x0 + 548314925880 2019/11/26 13:03:16.068 14466 14633 Error [CT]: FATAL: 18 /libdevices.so 0x0000007fac841fe4 OVR::Devices::CameraFrameSetManager::sendFrameSet(std::__1::vector<std::__1::shared_ptr<OVR::Devices::ImageData>, std::__1::allocator<std::__1::shared_ptr<OVR::Devices::ImageData> > >&) + 568 2019/11/26 13:03:16.068 14466 14633 Error [CT]: FATAL: 19 /libdevices.so 0x0000007fac8421f8 OVR::Devices::CameraFrameSetManager::processCompleteFrameSet(OVR::Devices::CameraFrameSetManager::FrameSet&, std::__1::vector<std::__1::shared_ptr<OVR::Devices::ImageData>, std::__1::allocator<std::__1::shared_ptr<OVR::Devices::ImageData> > >&, std::__1::unique_lock<std::__1::mutex>&) + 84 2019/11/26 13:03:16.068 14466 14633 Error [CT]: FATAL: 20 /libdevices.so 0x0000007fac841144 OVR::Devices::CameraFrameSetManager::frameSetOutputWorker() + 204 2019/11/26 13:03:16.068 14466 14633 Error [CT]: FATAL: 21 /libdevices.so 0x0000007fac842440 void* std::__1::__thread_proxy<std::__1::tuple<void (OVR::Devices::CameraFrameSetManager::*)(), OVR::Devices::CameraFrameSetManager*> >(void*) + 120 2019/11/26 13:03:16.068 14466 14633 Error [CT]: FATAL: 22 /libc.so 0x0000007fad3f6458 0x0 + 548367459416 2019/11/26 13:03:16.068 14466 14633 Error [CT]: FATAL: 23 /libc.so 0x0000007fad39e208 0x0 + 548367098376 2019/11/26 13:03:16.068 14466 14633 Error [CT]: FATAL: 24 ??? 0x0000000000000000 0x0 + 0 2019/11/26 13:03:16.068 14466 14633 Fatal [CT]: Fatal error 2019/11/26 13:03:16.068 14466 14633 Fatal [CT]: boltlib: Failed to close domain 2019/11/26 13:03:16.069 14466 14633 Fatal libc: Fatal signal 6 (SIGABRT), code -6 in tid 14633 (CamSlamCfsMgr) 2019/11/26 13:03:16.072 14466 14632 Warn [CT]: VIPER: StateBuffer: Could not get velocity from buffer. Not currently tracking in 6dof. *** This as well: 2019/11/26 13:03:16.400 1858 1923 Info PanelUtil_JNI: Using caller's JNIEnv 2019/11/26 13:03:16.406 2185 13762 Info TrackingServiceClient: Implausible sensor time! pt = 0.266076 2019/11/26 13:03:16.413 2185 13762 Info TrackingServiceClient: Implausible sensor time! pt = 0.272931 2019/11/26 13:03:16.413 2185 13762 Info TrackingServiceClient: Implausible sensor time! pt = 0.272968 2019/11/26 13:03:16.413 1858 1923 Info TrackingServiceClient: Implausible sensor time! pt = 0.273438 2019/11/26 13:03:16.414 1858 1923 Info TrackingServiceClient: Implausible sensor time! pt = 0.27361 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.414 1858 1923 I [OAR] HttpClient: Append 2019/11/26 13:03:16.414 1858 1923 Info PanelUtil_JNI: Using caller's JNIEnv 2019/11/26 13:03:16.415 14466 14611 Error SyncBossHAL: ../../hal/syncboss_shared/input/syncboss_hal_input_controller.c(69): ERROR: 1715eb6cxxxxxxxx: IMU corrupt: cur = 1502802, last = 1238610, delta = 264192, a = {-253, -322, -969}, g = {20, 10, -28} 2019/11/26 13:03:16.415 14466 14612 Error [CT]: TIMESTAMPCHECKER: IMU-IOHM timestamp: Measured delta time = 0.261254, nominal = 0.001. Dropped approx. 260.3 samples. Issue occurred 1 times since start. Time since last check: 0.271179 2019/11/26 13:03:16.415 14466 14612 Warn [CT]: VIPER: IMU Update delta (0.261254s) exceeds threshold (0.25s)! Partially resetting attitude filter. 2019/11/26 13:03:16.415 14466 14611 Error SyncBossHAL: ../../hal/syncboss_shared/input/syncboss_hal_input_controller.c(69): ERROR: d041cfbdxxxxxxxx: IMU corrupt: cur = 1502468, last = 1238392, delta = 264076, a = {906, -31, 471}, g = {14, -47, -7} 2019/11/26 13:03:16.415 14466 14612 Warn [CT]: VIPER: IMU Update delta (0.261254s) exceeds threshold (0.25s)! Partially resetting attitude filter. 2019/11/26 13:03:16.422 2468 2504 Info GuardianSystem: GuardianSystem::BroadcastInfoToShell systemux://guardian/update_state 2019/11/26 13:03:16.422 2468 2504 Debug VrRuntimeService: sendBroadcastIntent - action: 'com.oculus.vrshell.intent.action.GUARDIAN' data: 'systemux://guardian/update_state' intent_pkg: com.oculus.vrshell intent_cmd: 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.424 621 621 W : debuggerd: handling request: pid=14466 uid=1000 gid=1000 tid=14633 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.428 1858 1923 I [OAR] HttpClient: Append 2019/11/26 13:03:16.428 1858 1923 Info PanelUtil_JNI: Using caller's JNIEnv 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.429 1858 1858 D [OAR] ShellControlBroadcastReceiver: onReceive with MainActivity native pointer 3885044144, action com.oculus.vrshell.intent.action.GUARDIAN 2019/11/26 13:03:16.432 14466 14612 Error [CT]: TIMESTAMPCHECKER: Magnetometer-IOHM timestamp: Measured delta time = 0.300067, nominal = 0.0333333. Dropped approx. 8.0 samples. Issue occurred 1 times since start. Time since last check: 0.299979 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.432 1858 1858 D [OAR] ShellControlBroadcastReceiver: Shell foreground 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.442 1858 1923 I [OAR] ShellApp: 0xcca3f388 msg: broadcastIntent: 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.442 1858 1923 I [OAR] ShellApp: guardian_action_type = 0 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.442 1858 1923 I [OAR] ShellApp: intent_data = systemux://guardian/update_state 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.442 1858 1923 I [OAR] ShellApp: intent_pkg = com.oculus.vrshell 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.442 1858 1923 I [OAR] ShellApp: intent_cmd = 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.442 1858 1923 I [OAR] ShellApp: intent_action = com.oculus.vrshell.intent.action.GUARDIAN 0001/01/01 00:00:00.000 -1 -1 Info : 2019-11-26 13:03:16.442 1858 1923 W [OAR] ShellApp: Received unexpected broadcast intent com.oculus.vrshell.intent.action.GUARDIAN. 2019/11/26 13:03:16.401 14659 14659 Warn debuggerd64:dmp: type=1400 audit(0.0:61): avc: denied { execute } for name="sh" dev="dm-0" ino=523 scontext=u:r:debuggerd:s0 tcontext=u:object_r:shell_exec:s0 tclass=file permissive=0 2019/11/26 13:03:16.496 14660 14660 Fatal DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 2019/11/26 13:03:16.496 14660 14660 Fatal DEBUG: Build fingerprint: 'oculus/vr_monterey/monterey:7.1.1/NGI77B/415630.6700.0:user/release-keys' 2019/11/26 13:03:16.496 14660 14660 Fatal DEBUG: Revision: '0' 2019/11/26 13:03:16.496 14660 14660 Fatal DEBUG: ABI: 'arm64' 2019/11/26 13:03:16.496 14660 14660 Fatal DEBUG: pid: 14466, tid: 14633, name: CamSlamCfsMgr >>> /system/bin/trackingservice <<< 2019/11/26 13:03:16.496 14660 14660 Fatal DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- 2019/11/26 13:03:16.500 14660 14660 Fatal DEBUG: Abort message: 'Fatal error 2019/11/26 13:03:16.500 14660 14660 Fatal DEBUG: boltlib: Failed to close domain' 2019/11/26 13:03:16.500 14660 14660 Fatal DEBUG: x0 0000000000000000 x1 0000000000003929 x2 0000000000000006 x3 0000000000000008 2019/11/26 13:03:16.500 14660 14660 Fatal DEBUG: x4 0000007f95bfd130 x5 000000000000003f x6 0000000000000001 x7 0000005567900ed4 2019/11/26 13:03:16.500 14660 14660 Fatal DEBUG: x8 0000000000000083 x9 0000007f95bff450 x10 e5a9e7c46d6a3e4e x11 0000000000000000 2019/11/26 13:03:16.501 14660 14660 Fatal DEBUG: x12 0000000000000001 x13 0000000000000020 x14 ffffffffffffffdf x15 000417347d0cc994 2019/11/26 13:03:16.501 14660 14660 Fatal DEBUG: x16 0000007fad458ec8 x17 0000007fad3f9ed0 x18 000000000000002e x19 0000007f95bff4f8 2019/11/26 13:03:16.501 14660 14660 Fatal DEBUG: x20 0000000000000006 x21 0000007f95bff450 x22 0000000000000016 x23 0000007fabeb9b00 2019/11/26 13:03:16.501 14660 14660 Fatal DEBUG: x24 0000007facc2e518 x25 0000007f95bfd6c0 x26 0000007f95bfd700 x27 0000007fabbb601a 2019/11/26 13:03:16.501 14660 14660 Fatal DEBUG: x28 00000000000186a0 x29 0000007f95bfcff0 x30 0000007fad3f6c84 2019/11/26 13:03:16.501 14660 14660 Fatal DEBUG: sp 0000007f95bfcfd0 pc 0000007fad3f9ed8 pstate 0000000060000000 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: backtrace: 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #00 pc 0000000000079ed8 /system/lib64/libc.so (tgkill+8) 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #01 pc 0000000000076c80 /system/lib64/libc.so (pthread_kill+64) 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #02 pc 0000000000024ac0 /system/lib64/libc.so (raise+24) 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #03 pc 000000000001cdcc /system/lib64/libc.so (abort+52) 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #04 pc 0000000000003d58 /system/bin/trackingservice (__android_log_assert+224) 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #05 pc 0000000000b5497c /system/lib64/libMontereyTracker.so (_ZN9visionlog12doFatalErrorIJRA32_KcEEEvDpOT_+80) 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #06 pc 0000000001542510 /system/lib64/libMontereyTracker.so (_ZN4bolt16StatelessFastRPC18waitInvokeInternalENSt6__ndk112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEENS1_8functionIFivEEENS0_9ExtraArgsE+1512) 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #07 pc 0000000001543048 /system/lib64/libMontereyTracker.so (_ZN4bolt16StatelessFastRPC15waitInvokeAsyncEi+1224) 2019/11/26 13:03:16.530 14660 14660 Fatal DEBUG: #08 pc 0000000000e57a68 /system/lib64/libMontereyTracker.so (_ZN5viper8monterey18initializePyramidsEN3gsl4spanIKPN10perception16ImagePyramidBaseIhNS3_18ImageHalfSample3x3EEELln1EEERKNS5_10ParametersENS3_31ImagePyramidInitializationStateEPFvbPvESE_+88) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #09 pc 0000000000e539d8 /system/lib64/libMontereyTracker.so 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #10 pc 0000000000e3b290 /system/lib64/libMontereyTracker.so (_ZN10perception27ImagePyramidInitializerBaseINS_16ImagePyramidBaseIhNS_18ImageHalfSample3x3EEEE17ensureInitializedEN3gsl4spanIKPS3_Lln1EEE+200) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #11 pc 00000000011a7324 /system/lib64/libMontereyTracker.so (_ZN5viper11VideoFrames33ensureImagePyramidsAreInitializedEN3gsl4spanIKNS_10VideoFrameELln1EEE+256) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #12 pc 0000000000ab2398 /system/lib64/libMontereyTracker.so (_ZN5viper24StereoInitializerHandler9addFramesERKNS_11VideoFramesERKN4TooN3SO3IdEERKNS_11StateBufferE+444) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #13 pc 0000000000a3ffac /system/lib64/libMontereyTracker.so (_ZN5viper4Slam4Impl22track_initial_featuresERKNS_11VideoFramesEPKNS_15ImuMeasurementsERKN4TooN3SO3IdEERKN5boost8optionalINS8_6VectorILi3EfNS8_8Internal5VBaseEEEEE+96) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #14 pc 0000000000a357b4 /system/lib64/libMontereyTracker.so (_ZN5viper4Slam4Impl14process_framesERKNS_11VideoFramesE+276) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #15 pc 0000000000a55a78 /system/lib64/libMontereyTracker.so (_ZN5viper18VideoFrameAnalyzer4Impl14process_framesERKNS_11VideoFramesE+1760) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #16 pc 0000000000a51884 /system/lib64/libMontereyTracker.so (_ZN5viper18VideoFrameAnalyzer4Impl9on_framesEN10perception6IdTmplIjNS2_4slam13FrameSetIdTagELb0EEEN3gsl4spanIKPKhLln1EEENS_13LiveTimestampENS8_IKdLln1EEESF_+920) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #17 pc 00000000009aed60 /system/lib64/libMontereyTracker.so (_ZN8coretech23InsideOutTrackingEngine11onImageDataEN3gsl4spanIK15VisionImageDataLln1EEEN11visiontypes9TimestampI18TheProcessingClockEE+932) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #18 pc 00000000009a93c0 /system/lib64/libMontereyTracker.so 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #19 pc 00000000014a2f1c /system/lib64/libMontereyTracker.so 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #20 pc 0000000000043b34 /system/lib64/libtracker-devices.so 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #21 pc 0000000000020fe0 /system/vendor/lib64/libdevices.so (_ZN3OVR7Devices21CameraFrameSetManager12sendFrameSetERNSt3__16vectorINS2_10shared_ptrINS0_9ImageDataEEENS2_9allocatorIS6_EEEE+564) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #22 pc 00000000000211f4 /system/vendor/lib64/libdevices.so (_ZN3OVR7Devices21CameraFrameSetManager23processCompleteFrameSetERNS1_8FrameSetERNSt3__16vectorINS4_10shared_ptrINS0_9ImageDataEEENS4_9allocatorIS8_EEEERNS4_11unique_lockINS4_5mutexEEE+80) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #23 pc 0000000000020140 /system/vendor/lib64/libdevices.so (_ZN3OVR7Devices21CameraFrameSetManager20frameSetOutputWorkerEv+200) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #24 pc 000000000002143c /system/vendor/lib64/libdevices.so (_ZNSt3__114__thread_proxyINS_5tupleIJMN3OVR7Devices21CameraFrameSetManagerEFvvEPS4_EEEEEPvS9_+116) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #25 pc 0000000000076454 /system/lib64/libc.so (_ZL15__pthread_startPv+204) 2019/11/26 13:03:16.531 14660 14660 Fatal DEBUG: #26 pc 000000000001e204 /system/lib64/libc.so (__start_thread+16) 2019/11/26 13:03:16.536 2016 16500 Debug OculusFbPermissionsContentProvider: Package(s) are not FbPermission signed: '[com.android.keychain, com.oculus.os.vrmtpapp, com.oculus.vraudiodatadumpmanager, com.oculus.inputmethod.pacific, com.android.wallpaperbackup, com.oculus.micservice, com.oculus.externalstorage, com.qualcomm.timeservice, com.oculus.unifiedtelemetry, com.oculus.os.chargecontrol, com.qualcomm.wfd.service, com.oculus.vrpowermanager, com.oculus.vrcast, com.oculus.os.settings, oculus.platform, com.android.settings, com.oculus.location.geocoder, com.oculus.companion.server, com.oculus.wifiindoze, android, com.oculus.os.vrlockscreen, com.oculus.preloader, com.android.inputdevices, com.oculus.vrdesktop, com.android.providers.settings, com.oculus.gatekeeperservice, com.oculus.vrshell.desktop, com.android.location.fused, com.oculus.bugreporter, com.oculus.deviceauthserver, com.oculus.vralertservice, com.oculus.linefrequencyservice, com.oculus.headsetsfx, com.oculus.os.clearactivity, com.oculus.notification_proxy]') 2019/11/26 13:03:16.542 2016 2680 Debug OculusFbPermissionsContentProvider: Package(s) are not FbPermission signed: '[com.android.keychain, com.oculus.os.vrmtpapp, com.oculus.vraudiodatadumpmanager, com.oculus.inputmethod.pacific, com.android.wallpaperbackup, com.oculus.micservice, com.oculus.externalstorage, com.qualcomm.timeservice, com.oculus.unifiedtelemetry, com.oculus.os.chargecontrol, com.qualcomm.wfd.service, com.oculus.vrpowermanager, com.oculus.vrcast, com.oculus.os.settings, oculus.platform, com.android.settings, com.oculus.location.geocoder, com.oculus.companion.server, com.oculus.wifiindoze, android, com.oculus.os.vrlockscreen, com.oculus.preloader, com.android.inputdevices, com.oculus.vrdesktop, com.android.providers.settings, com.oculus.gatekeeperservice, com.oculus.vrshell.desktop, com.android.location.fused, com.oculus.bugreporter, com.oculus.deviceauthserver, com.oculus.vralertservice, com.oculus.linefrequencyservice, com.oculus.headsetsfx, com.oculus.os.clearactivity, com.oculus.notification_proxy]') 2019/11/26 13:03:16.548 2185 13762 Info Clocks: SetSchedFifo( tid=1923, pri=0 ) succeeded 2019/11/26 13:03:16.549 2185 13762 Info Clocks: SetSchedFifo( tid=14475, pri=0 ) succeeded 2019/11/26 13:03:16.550 2185 13762 Info Clocks: SetSchedFifo( tid=2582, pri=0 ) succeeded 2019/11/26 13:03:16.557 2016 16500 Debug LibraryProvider: running queryApp(system) for android.uid.system:1000 *** These happen every once in a while 2019/11/26 13:03:17.718 1545 1545 Info VrPowerManagerService: transition from HEADSET_MOUNTED to HEADSET_UNMOUNTED 2019/11/26 13:03:17.719 2468 2582 Info VrApi: ovr_HandleHmdEvents: HMT was UNmounted 2019/11/26 13:03:17.720 1545 1545 Error JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 100) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: error broadcasting state 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at android.os.BinderProxy.transactNative(Native Method) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at android.os.BinderProxy.transact(Binder.java:617) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at oculus.internal.power.IVrPowerManagerClient$Stub$Proxy.onStateChange(IVrPowerManagerClient.java:77) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at com.oculus.vrpowermanager.VrPowerManagerService$IVrPowerManagerClientProxy.notifyState(VrPowerManagerService.java:606) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at com.oculus.vrpowermanager.VrPowerManagerService$ServiceInterface.notifyStateChange(VrPowerManagerService.java:710) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at com.oculus.vrpowermanager.VrPowerManagerService.transitionToState(VrPowerManagerService.java:307) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at com.oculus.vrpowermanager.VrPowerManagerService.-wrap7(VrPowerManagerService.java) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at com.oculus.vrpowermanager.VrPowerManagerService$3.handleMessage(VrPowerManagerService.java:207) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at android.os.Handler.dispatchMessage(Handler.java:102) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at android.os.Looper.loop(Looper.java:154) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at android.app.ActivityThread.main(ActivityThread.java:6144) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at java.lang.reflect.Method.invoke(Native Method) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886) 2019/11/26 13:03:17.721 1545 1545 Error VrPowerManagerService: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776) 2019/11/26 13:03:17.721 1778 1778 Debug VRLifecycleSessionManager: onHeadsetUnmounted() 2019/11/26 13:03:17.721 2185 2185 Debug VrRuntimeService: Received broadcast: com.oculus.intent.action.MOUNT_STATE_CHANGED *** And in our app Then again there are some issues with the app as well. But as mentioned it is very hard to reproduce in the office conditions. It usually happen when we are in new places. Often with the application built with il2cpp, arm64, release. The crash logs lack stacktraces. The application is not distributed through the store. The issues seem to happen more often when switching on and off the headset in presence of network noise and moving people. But also sometimes there are issues when the app is long running, like 45min straight. Are there any suggestions or guidelines how to deal with issues like these?2.7KViews0likes3Comments
[v13-15] Editor crashes on play after upgrading Oculus Integration.
I just updated Oculus Integration to v13 and found Unity editor crashes with hand tracking. What I did is make a new project and a new scene, add setup some necessary stuff such as importing Oculus Integration, and add OVRCameraRig to the scene as well as OVRHandPrefab and OVRControllerPrefab as children of the hand anchors. Finally, change the platform to Android and set OVRManager's Hand Tracking Support to "Controller And Hands". Then I hit play and it crashed. I tried Unity 2019.2.9f1 and 2019.3.0f6 but both didn't work. The HandTest scene worked successfully just once, and at that time my scene worked too. But after rebooting It didn't work again. I don't know why. Anyone knows the solution? By the way I am using Oculus Quest and Oculus Link.4.2KViews4likes14Comments
Button.One not working on Unity via Oculus Link, works fine in build
All the buttons work other than Button.One when using Link to make Unity game, if the code is deployed to the Quest all the buttons work, so probably an issue with Unity interface. Test code, outputs a uint32 bitmask, when run inside Unity via Link (Beta) will not give Button.One (00000001) but works fine when deployed. uint AllButtons() { uint tResult = 0; for (int i = 0; i < 32; i++) { OVRInput.Button tMask = (OVRInput.Button)((uint)1 << i); tResult |= (OVRInput.Get(tMask, mControllerHelper.m_controller) ? (uint)1 : (uint)0) << i; } return tResult; }444Views0likes0CommentsOculus' Teleportation example tries to kill me
Hi I built the SDK examples and have been trying the teleportation (aka locomotion scene). However, when I teleport I get placed in a completely different location than the one I select, and I often get placed outside of the example scene's mesh. So then I fall.. Indefinitely.. until floating point errors tear my soul apart. So question is: how can I fix the teleportation? :)481Views0likes0Comments
libovravatar.dll (version 1.2.3.0) Causing unlogged crashes
Context info (from OVRManager's console log): Unity v2018.2.21f1, Oculus Utilities v1.37.0, OVRPlugin v1.37.0, SDK v1.38.0. ---Yesterday, the sdk version was also 1.37.0, I'm not quite sure how that updated but the crashes have happened with both versions. The crashes are not logged in Unity's output log, nor are there any hints as far as I could tell. I used the OculusLogGatherer tool to finally find what was causing the crash. I'll paste the event logs. The Unity application we're developing is a crane simulation, where we teach the player how to give specific hand gestures/motions to signal a crane. To help with that, we use the Oculus avatar system to record a developer giving the correct signals and play the recording back at runtime for the player to mimic. This project has been in development for 2 years and we have updated our Unity version and Oculus sdk and plugin a few times over that span. The signal recordings were taken a long time ago and we have updated our project since then. So far, the crashes have not occurred predictably; we can sit and watch the recordings playback for several minutes, starting and stopping as expected. Then, in the middle of one of the recordings, the editor (or build) will crash. I haven't been able to establish a clear pattern for it, but it might be related to starting a new recording soon after ending a previous one, but that is a low confidence guess. The crashes occur both on our development machines and on Valve's test machines, which is unfortunately how we first noticed the crashes. I'm guessing our QA team flew through the tutorial so fast that the problem didn't show up. Here are the event logs capturing the crashes, some in the editor and one in the player: Faulting application name: Signal Person Training.exe, version: 2018.2.21.8949, time stamp: 0x5c73f900 Faulting module name: libovravatar.DLL, version: 1.2.3.0, time stamp: 0x5cdb398c Exception code: 0xc0000409 Fault offset: 0x000000000004c23c Faulting process id: 0x1968 Faulting application start time: 0x01d5212f09126f1a Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\CLS Signal Person\Signal Person Training.exe Faulting module path: C:\Program Files\Oculus\Support\oculus-runtime\libovravatar.DLL Report Id: c1a76a9f-e118-4675-bae6-6308941d7cf2 Faulting package full name: Faulting package-relative application ID: Faulting application name: Unity.exe, version: 2018.2.21.8949, time stamp: 0x5c73f759 Faulting module name: libovravatar.DLL, version: 1.2.3.0, time stamp: 0x5d003cf3 Exception code: 0xc0000409 Fault offset: 0x000000000004cc3c Faulting process id: 0x3188 Faulting application start time: 0x01d521e815270000 Faulting application path: C:\Program Files\Unity\Hub\Editor\2018.2.21f1\Editor\Unity.exe Faulting module path: C:\Program Files\Oculus\Support\oculus-runtime\libovravatar.DLL Report Id: 208d504e-7332-474f-b614-47dc04020bc3 Faulting package full name: Faulting package-relative application ID: Faulting application name: Unity.exe, version: 2018.2.21.8949, time stamp: 0x5c73f759 Faulting module name: libovravatar.DLL, version: 1.2.3.0, time stamp: 0x5d003cf3 Exception code: 0xc0000409 Fault offset: 0x000000000004cc3c Faulting process id: 0x1e2c Faulting application start time: 0x01d521f05faa3373 Faulting application path: C:\Program Files\Unity\Hub\Editor\2018.2.21f1\Editor\Unity.exe Faulting module path: C:\Program Files\Oculus\Support\oculus-runtime\libovravatar.DLL Report Id: 59ac9a4a-6b19-42d5-badf-eedd001667db Faulting package full name: Faulting package-relative application ID: After investigating the reported exception code, it looks like this is a stack buffer overflow fault, according to this Microsoft forum (https://social.msdn.microsoft.com/Forums/sqlserver/en-US/aa84a49e-6bfe-4b89-928a-ea477e73c07e/clr-exception-0xc0000409?forum=clr) and supported by other search results. I couldn't find any information on my version of libovravatar.dll (1.2.3.0), but since it's part of the runtime I expect Oculus to automatically update this. Our recording and playback system is based on the provided sample scripts in Assets/Oculus/Avatar/Samples/RemoteLoopback and the guide found here: https://developer.oculus.com/documentation/avatarsdk/latest/concepts/avatars-gsg-unity/ Here's the playback code: TextAsset asset = Resources.Load(filename) as TextAsset; if (asset != null) { MemoryStream s = new MemoryStream(asset.bytes); reader = new BinaryReader(s); loadPacket(); } /// <summary> /// This is called recursively for every frame in the avatar recording. /// </summary> void loadPacket() { if (reader.BaseStream.Position >= reader.BaseStream.Length) {//If we've reached the end of the file, load it again and start over. reader.Close(); this.DelayedInvoke(delegate { loadFile(); }, .1f); return; } int sequence = reader.ReadInt32(); int size = reader.ReadInt32(); byte[] sdkData = reader.ReadBytes(size); IntPtr packet = CAPI.ovrAvatarPacket_Read((UInt32)size + 8, sdkData); OvrAvatarPacket p = new OvrAvatarPacket {ovrNativePacket = packet}; remoteAvatar.GetComponent<OvrAvatarRemoteDriver>().QueuePacket(sequence, p); this.DelayedInvoke(delegate { normalize(); loadPacket(); }, remoteAvatar.PacketSettings.UpdateRate); } private void OnDestroy() { if (reader != null) { reader.Close(); } if (remoteAvatar) { Destroy(remoteAvatar.gameObject); } } normalize() adjusts the scale and position of the playback avatar to make it look nice and appear where we expect. I'm hoping someone can tell me if this is a bug on Oculus' end, or if we are using the api improperly in some subtle way I haven't discovered yet. In either case, Is there a suggested workaround? We could bypass the problem altogether by moving away from the avatar system and just tracking position and pose data ourselves, but that seems an awful waste.959Views0likes1Comment[OVRNetworkTcpServer] EndAcceptTcpClient failed: The object was used after being disposed.
I'm getting memory leaks from the performance metrics script. Without worrying too much about why this happens (I really don't find myself using Oculus's profiler or performance metrics much), is there a way to disable this? I believe it's causing the headset to go black, with the only way to fix it being to restart the Oculus app.591Views1like0Comments
