V56 and up, Quest Pro Link stability
Hello, I've been developing an app at work for PCVR, we're using Quest Pros and extremely high end PCs with one router that has four WiFi bands, hardware is not an issue here, all new and a bit of an overkill performance-wise. The problems we're having are crashes and stability of tracking when in link, the headsets repeatedly reset and adjust their position as if pressing recenter. We were using spatial anchors before but that can no longer be utilized as they cause our app AND oculus desktop app to crash. We're building on Unreal Engine 5.2 with developer features turned on so we can use hand tracking and anchors on PC. We tested for what could cause the crashes and found out that it is Quest system version, even with the newest plugin in Unreal the app runs smoothly on v55 but still stashes on v56 and v57. Is this a known issue or are we the first to encounter it? Any help with solving the crashes would be appreciated, we had to code our own provisional spatial anchors for now but the instability with link makes them an unviable option.2.3KViews3likes2CommentsSDK 0.0.0 and İnfinite loading screen
Hello, Im developing a vr game. İt was working just fine. I have Buy a SSD and clean win10 at it. my program now just dont launch. I have try xr-plugin , manual OVRPlugin but not working. İf I enable any of them unity returns me "Unable to load OvrPlugin.dll" or a crash. İf I dont my game start at unity but stuck at loading screen on Rift S. I tried a new project with oculus integration packages "Room" scene but same thing happened. As you can see bellow there is "SDK v0.0..0" is this problem about it? how can ı install/update this. Unity v2020.2.0b14, Oculus Utilities v1.55.0, OVRPlugin v1.55.0, SDK v0.0.0. UnityEngine.Debug:Log (object) OVRManager:InitOVRManager () (at Assets/Oculus/VR/Scripts/OVRManager.cs:1246) OVRManager:Awake () (at Assets/Oculus/VR/Scripts/OVRManager.cs:1404)749Views0likes0CommentsOculusSDK causing application crash on exit
Windows 10, Visual Studio 2010 C++ OculusSDK 1.8.0, firmware version 7.9 GeForce GTX 1070/PCIe/SSE2, OpenGL Version: 4.6.0 NVIDIA 398.11, GLSL Version: 4.60 NVIDIA It seems that something has changed just in the past few days (as of 2018-08-23) that's causing our application to crash on exit. We wrap the OculusSDK 1.8.0 in our own DLL that we load at run-time via LoadLibrary, depending on application configuration options. (The application supports various VR tracking and display environments; the Oculus Rift is one option.) As of today, the application crashes on exit, only if the OculusSDK has been opened, and only in the release build; the debug build does not crash. This happens whether or not we explicitly call FreeLibrary for our DLL at program exit. The OculusSDK logs these status messages in our console window: [ At startup, we open with ovr_Initialize (nullptr) ] 23/08 19:07:20.832 {INFO} [Kernel:Default] [CAPI] LibOVR module is located at C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT64_1.dll 23/08 19:07:20.835 {INFO} [Client] Connected to the server running version (prod = 1).1.29.0(build = 651191) feature version = 0. Client runs version (prod = 1).1.29.0(build = 0) feature version = 0 23/08 19:07:20.838 {DEBUG} [Kernel:Default] [HMDState] Using default profile default 23/08 19:07:20.838 {INFO} [Kernel:Default] IAD changed to 64.2mm 23/08 19:07:20.839 {DEBUG} [SharedMemory] Creating factory 23/08 19:07:22.178 {DEBUG} [D3D11_CliCompositorClient] CliD3D11CompositorClient::initialize 1 23/08 19:07:22.220 {DEBUG} [KMTSyncObject] Creating KMTHandle 0x0d2fc4d0 23/08 19:07:22.222 {DEBUG} [KMTSyncObject] Creating KMTHandle 0x0d2fc610 23/08 19:07:22.222 {DEBUG} [KMTSyncObject] KMTHandle::Create hDevice=0x80000380 23/08 19:07:22.222 {DEBUG} [KMTSyncObject] KMTHandle::Create hContexts[0] = 2147485504 23/08 19:07:22.222 {DEBUG} [KMTSyncObject] KMTHandle::Create hContexts[1] = 2147485824 23/08 19:07:22.286 {DEBUG} [D3D11_CliCompositorClient] CliD3D11CompositorClient::addGLRef 2 23/08 19:07:23.552 {INFO} [Kernel:Default] [HMDState] Detected the active window handle changed to 111af0ll 23/08 19:07:28.635 {WARNING} [Tracking:Filter] Prediction interval too high: 0.101367 s, clamping at 0.100000 s [ The application runs well, with a good frame rate. I can move and resize the on-screen mirror window. Everything renders well in the Rift and on-screen. The test scene averages well over 100 frames per second, so the initial high prediction interval seems to be a startup fluke. ] [ At exit, we close with ovr_Destroy (m_Session) and ovr_Shutdown() ] 23/08 19:07:31.115 {DEBUG} [D3D11_CliCompositorClient] CliD3D11CompositorClient::release 2 23/08 19:07:31.117 {DEBUG} [D3D11_CliCompositorClient] CliD3D11CompositorClient::release 1 23/08 19:07:31.117 {DEBUG} [D3D11_CliCompositorClient] Unblocking monitored fence 23/08 19:07:31.121 {INFO} [Kernel:System] Graceful shutdown: OnThreadDestroy 23/08 19:07:31.121 {INFO} [Kernel:System] Graceful shutdown: OnSystemDestroy 23/08 19:07:31.121 {DEBUG} [SharedMemory] Destroying factory 23/08 19:07:31.121 {DEBUG} [Kernel:Default] [Client] Disconnected 23/08 19:07:31.121 {INFO} [Kernel:System] Graceful shutdown: Stopping logger At program exit, it dies in the Windows function __tmainCRTStartup(void) (in crtexe.c): A problem caused the program to stop working correctly. All of our C++ wrapper class close and d'tor functions appear to return successfully. I have wrapped the entire body of our main function in try {} catch() {}, but it fails to catch this exception. I have put a 10-second sleep just before the program exit, but that merely delays the crash; it does not avoid it. The console messages and the crash are all new behavior that I did not see (or notice) just a few days ago. The crash is definitely a new behavior. This application has not changed during that time. Judging from those console messages, it seems that maybe some Oculus resource isn't shutting down properly -- and that maybe somebody has been struggling with that. The fact that it crashes in the release build, but not the debug build, suggests that maybe something has not been initialized properly (e.g., to zero). Maybe the debug build initializes it; or maybe the lower degree of optimization avoids some memory corruption. Maybe there's a dangling reference to SharedMemory. Maybe the logging itself is causing the crash. I did not request logging, and in fact tried to explicitly disable it with ovrInitParams init_params = { 0, 0, nullptr, 0, 0 }; ovr_Initialize (&init_params) but the logging messages still appear in the console window. The appearance of the logging messages correlates with the crash-at-exit behavior: they're both new. Please advise. Thanks. -- Ted Hall <twhall@umich.edu>Solved3.9KViews0likes5CommentsGear VR crash issue with unity 5.4.2 p2
Hello, I am developing a simple application in which some data and images gets downloaded from server and gets stored in local storage. Now there are 2 issues - 1) When I start my application for the very first time it runs fine, it do not gets any file from local storage so downloads it from threads. Now when I start the application the second time it gets crashed. If I delete the data from Applications it runs again. 2) After successful run of the application I am on my main scene. Now when I go to another scene and comes back to the main scene it crashes giving a "memory violation" error in logs. I thought that its a Read permission issue so I added those permissions in my manifest and checked if its getting merged in the google project. But then also its happening. Please help as i am under deadlines and literally stuck because of this.765Views0likes1CommentSDK 1.3 ovr_Initialize failure. fffff447 --
Hi, My DK2 runs perfectly with the latest Oculus Home (1.3) and so do the bundled apps. However when I try to compile the SDK 1.3 samples none of them work. The OculusWorldDemo throws up the error message: "ovr_Initialize failure. fffff447". OculusRoomTiny throws up the error "Failed to initialize LibOVR". I cant see a runtime version issue as being the culprit as I seem to have the latest. Please help ! Thanks Sanjit4.8KViews0likes3CommentsBug? If I search for LibOVRRT64_0_8.dll with ProcessExplorer my computer crashes
Download and install ProcessExplorer [1]. Open ProcessExplorer and select Find | Find Handle or DLL... Type in LibOVRRT64_0_8.dll and click Search button. My computer crashes. Any thoughts? As a backstory I was trying to look into why we occasionally see crashes in ovr_Lookup() from this dll with our Unity3d based VR application despite the fact that we are using an HTC Vive. [1] https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx { "Time": "2016-04-05_16:12:21", "SDK Version": "0.8.0.0", "Local SDK Version": "0.8.0.0", "Service Running Time": { "Hours": 0, "Minutes": 13, "Seconds": 22 }, "Display Status": { "Display Mode": 2, "Win10 Native": { "Capable": 1, "Available": 1, "ResultCode": 0, "Status": "DXGI 2 Preview available" }, "IHVDirect": { "Capable": 1, "Available": 1, "ResultCode": 0, "Status": "Direct Display available" }, "Legacy Direct": { "Capable": 0, "Available": 0, "ResultCode": -3005, "Status": "OVRDirect not supported on this OS. Please use one of the more supported modes" }, "Summary ResultCode": 0, "Summary Status": "" }, "System Specifications": { "Operating System": "Microsoft Windows 10 Pro", "Processor": "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz", "Graphics Adapters": [{ "Name": "NVIDIA GeForce GTX 980", "Video Controller RAM (MB)": 4095, "Driver Version": "10.18.13.6472", "Video Mode": "2560 x 1440 x 4294967296 colors" }, { "Name": "NVIDIA GeForce GTX 980", "Video Controller RAM (MB)": 4095, "Driver Version": "10.18.13.6472", "Video Mode": "" }], "Total RAM (GB)": 32, "USB Tree": [{ "name": "Intel(R) C610 series/X99 chipset USB Enhanced Host Controller #1 - 8D26", "deviceid": "PCI\\VEN_8086&DEV_8D26&SUBSYS_064C1028&REV_05\\3&11583659&0&E8", "caption": "Intel(R) C610 series/X99 chipset USB Enhanced Host Controller #1 - 8D26", "manufacturer": "Intel", "Devices": [{ "manufacturer": "(Standard USB Host Controller)", "name": "USB Root Hub" }, { "manufacturer": "(Generic USB Hub)", "name": "Generic USB Hub" }] }, { "name": "Intel(R) C610 series/X99 chipset USB Enhanced Host Controller #2 - 8D2D", "deviceid": "PCI\\VEN_8086&DEV_8D2D&SUBSYS_064C1028&REV_05\\3&11583659&0&D0", "caption": "Intel(R) C610 series/X99 chipset USB Enhanced Host Controller #2 - 8D2D", "manufacturer": "Intel", "Devices": [{ "manufacturer": "(Standard USB Host Controller)", "name": "USB Root Hub" }, { "manufacturer": "(Generic USB Hub)", "name": "Generic USB Hub" }] }, { "name": "Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)", "deviceid": "PCI\\VEN_8086&DEV_8D31&SUBSYS_064C1028&REV_05\\3&11583659&0&A0", "caption": "Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)", "manufacturer": "Generic USB xHCI Host Controller", "Devices": [{ "manufacturer": "(Standard USB HUBs)", "name": "USB Root Hub (xHCI)" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic SuperSpeed USB Hub" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic SuperSpeed USB Hub" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic SuperSpeed USB Hub" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic SuperSpeed USB Hub" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic USB Hub" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic USB Hub" }, { "manufacturer": "(Standard USB Host Controller)", "name": "USB Composite Device" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "(Standard system devices)", "name": "HID-compliant vendor-defined device" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "(Standard system devices)", "name": "HID-compliant vendor-defined device" }, { "manufacturer": "(Standard USB Host Controller)", "name": "Unknown USB Device (Device Descriptor Request Failed)" }, { "manufacturer": "Broadcom", "name": "BCM20703 Bluetooth 4.1 USB Device" }, { "manufacturer": "(Standard USB Host Controller)", "name": "USB Composite Device" }, { "manufacturer": "Microchip Technology, Inc.", "name": "USB5734 COM Port (COM5)" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic USB Hub" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "Microsoft", "name": "HID-compliant mouse" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic USB Hub" }, { "manufacturer": "Realtek Semiconduct Corp.", "name": "Realtek USB 2.0 Card Reader" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "(Standard system devices)", "name": "HID-compliant vendor-defined device" }, { "manufacturer": "(Standard USB Host Controller)", "name": "USB Composite Device" }, { "manufacturer": "Corsair", "name": "Corsair K70 Gaming Keyboard" }, { "manufacturer": "(Standard keyboards)", "name": "HID Keyboard Device" }, { "manufacturer": "Corsair", "name": "Corsair K70 Gaming Keyboard" }, { "manufacturer": "Microsoft", "name": "HID-compliant consumer control device" }, { "manufacturer": "(Standard system devices)", "name": "USB Input Device" }, { "manufacturer": "(Standard keyboards)", "name": "HID Keyboard Device" }, { "manufacturer": "Intel Corporation", "name": "Intel(R) Wireless Bluetooth(R)" }, { "manufacturer": "Microsoft", "name": "Microsoft Bluetooth LE Enumerator" }, { "manufacturer": "Microsoft", "name": "Bluetooth Device (RFCOMM Protocol TDI)" }, { "manufacturer": "Microsoft", "name": "Microsoft Bluetooth Enumerator" }, { "manufacturer": "Microsoft", "name": "Service Discovery Service" }, { "manufacturer": "Microsoft", "name": "Microsoft Hardware Bluetooth Device" }, { "manufacturer": "Microsoft", "name": "Device Identification Service" }, { "manufacturer": "Microsoft", "name": "Microsoft Sculpt Comfort Mouse" }, { "manufacturer": "Microsoft", "name": "Bluetooth Device (Personal Area Network)" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic USB Hub" }, { "manufacturer": "(Standard USB HUBs)", "name": "Generic USB Hub" }, { "manufacturer": "(Standard USB Host Controller)", "name": "USB Composite Device" }, { "manufacturer": "Oculus VR", "name": "Rift DK2 Sensor" }] }] }, "Video Device Tree": [{ "Name": "NVIDIA GeForce GTX 980", "VRAM (MB)": 4008, "Monitors": [{ "Name": "\\\\.\\DISPLAY1", "Width": 2560, "Height": 1440, "Refresh Rate": 59 }, { "Name": "\\\\.\\DISPLAY2", "Width": 2560, "Height": 1440, "Refresh Rate": 59 }] }, { "Name": "NVIDIA GeForce GTX 980", "VRAM (MB)": 4008, "Monitors": [] }, { "Name": "Microsoft Basic Render Driver", "VRAM (MB)": 0, "Monitors": [] }], "Devices": [{ "HMDNRFVersion": "", "TrackerNRFVersion": "(none)" }], "Profile": { "Player Name": "jimbo", "IPD": 0.064000, "Eye height": 1.726672, "Eye Cup": "", "Eye Relief": 3, "Gender": "Male", "Eye To Neck": 0.075000, "Player Height": 1.830000 } }796Views0likes0Comments