2016-08-24 70 views
1

我最近爲我全新的CV1做了一些改進。儘管我的GTX 980M不推薦VGA,但它應該顯示一些東西。現在關於這個問題。它開始於Oculus Home設置,似乎一切正常,甚至跟蹤正在工作,我從安裝過程中聽音頻,但顯示是完全黑色。 LED是橙色的順便說一句。不過,我設法只通過我的Oculus遙控器使用音頻傳遞設置。現在我可以看到Oculus Home,但是當我嘗試從那裏運行任何應用程序時,它只會保持黑色。我也是一個Unity3D開發者,當我嘗試啓動我自己的應用程序時也是如此。在統一HDM工作,陀螺儀是好的(我可以看到我的筆記本電腦顯示器,當我轉身),但顯示仍然是黑色,橙色LED燈。在這裏,我已經捕獲了一些Oculus服務器日誌,也許它可以幫助!請幫助任何人!Oculus Rift CV1黑色顯示屏

24/08 15:36:48.824 {INFO} [LifeCycle] motionSensorEvent() Start 
24/08 15:36:48.824 {INFO} [LifeCycle] HMD Moving: true 
24/08 15:36:48.824 {INFO} [TrackingManager] Setting tracking mode to on 
24/08 15:36:48.824 {INFO} [Server] Tracking Enabled : true 
24/08 15:36:48.824 {DEBUG} [Server] UpdateFocusedVirtualHmd: ConfigureTracking On (112) 
24/08 15:36:48.824 {DEBUG} [Kernel:Default] [VirtualHMD] Applying client-specific caps 
24/08 15:36:48.825 {WARNING} [Server] Setting connection focus to pid: 1336, file: oculus-overlays.exe, but no window handle exists 
24/08 15:36:48.825 {INFO} [LifeCycle] motionSensorEvent() End 
24/08 15:36:49.118 {INFO} [HW:Enumeration] HMDs: 1, Displays: 1 
24/08 15:36:49.118 {DEBUG} [HW:HmdSensor] IMU report rate = 500 
24/08 15:36:49.118 {INFO} [HW:HmdSensor] Leaving idle mode 
24/08 15:36:49.118 {INFO} [HW:Enumeration] Setting frameInterval = 19200, ledExposure = 399 
24/08 15:36:49.118 {INFO} [HW:HmdSensor] Setting LED state: true 
24/08 15:36:49.320 {DEBUG} [Server] Connection open for pid: 12020, file: Unity.exe 
24/08 15:36:49.320 {DEBUG} [Server] Accepted a client from pid: 12020(Unity.exe) running version (prod = 1).1.7.0(build = 262766) feature version = 0. Server is version (prod = 1).1.7.0(build = 262766) feature version = 0 
24/08 15:36:49.321 {DEBUG} [Server] UpdateFocusedVirtualHmd: ConfigureTracking On (112) 
24/08 15:36:49.321 {DEBUG} [Kernel:Default] [VirtualHMD] Applying client-specific caps 
24/08 15:36:50.450 {WARNING} [Server] Setting connection focus to pid: 1336, file: oculus-overlays.exe, but no window handle exists 
24/08 15:36:50.450 {DEBUG} [Server] Hmd_Create 
24/08 15:36:50.450 {DEBUG} [Kernel:Default] [AppFocusObserver] AddProcess: Recognizing the newly added process as in-focus pid=12020 
24/08 15:36:50.450 {INFO} [LifeCycle] registerPid() Start 
24/08 15:36:50.450 {INFO} [LifeCycle] Register Pid: 12020 (Sideloaded) 
24/08 15:36:50.450 {INFO} [LifeCycle] Registering tracker: 12020 (Sideloaded) 
24/08 15:36:50.450 {INFO} [LifeCycle] App already added. 
24/08 15:36:50.450 {INFO} [LifeCycle] registerPid() End 
24/08 15:36:50.450 {DEBUG} [Server] Hmd_GetHmdInfo 
24/08 15:36:50.454 {DEBUG} [Kernel:Default] [AppFocusObserver] UpdateTextureSetActive: Setting rift window for pid=12020 textureset=1 
24/08 15:36:50.454 {INFO} [LifeCycle] requestFocus() Start 
24/08 15:36:50.454 {INFO} [LifeCycle] Request Focus: 12020 (Sideloaded) 
24/08 15:36:50.454 {INFO} [LifeCycle] Request Location: APP 
24/08 15:36:50.454 {INFO} [LifeCycle] Push Location: APP 
24/08 15:36:50.454 {INFO} [LifeCycle] Update Location: HSW 
24/08 15:36:50.454 {INFO} [LifeCycle] Inactive Focus: 3452 (oculus-home) 
24/08 15:36:50.454 {INFO} [LifeCycle] Already Focused: 0 (Unknown) 
24/08 15:36:50.454 {INFO} [LifeCycle] requestFocus() End 
24/08 15:36:50.455 {INFO} [Kernel:Default] WARNING: [CameraTimeSynchronizer] out of sync. Exposure Delta = 33830.2 ms, cameraDelta = -32430.4 ms. 
24/08 15:36:50.455 {WARNING} [Tracking:Tracker] WMTD302S600Z3S: at 0, skipped 1 frames (37403 -> 37405) 
24/08 15:36:50.569 {INFO} [Kernel:Default] [CameraTimeSynchronizer] successfully synchronized. 
24/08 15:36:50.667 {DEBUG} [Tracking:Filter] HMD: Large change, resetting position filter 
24/08 15:36:51.031 {INFO} [DeviceEvent] SENSOR [WMTD302S600Z3S] TrackingChanged 0 
24/08 15:36:51.031 {INFO} [HardwareManager] Tracker WMTD302S600Z3S got tracking event with error code 0 
24/08 15:36:51.518 {DEBUG} [Kernel:Default] [AppFocusObserver] UpdateRenderingActive: pid=12020 active 
24/08 15:36:51.518 {INFO} [LifeCycle] enterVR() Start 
24/08 15:36:51.518 {INFO} [LifeCycle] Enter VR: 12020 (Sideloaded) 
24/08 15:36:51.518 {INFO} [AppTracker] VR Ready: 12020 (Sideloaded) 
24/08 15:36:51.518 {INFO} [LifeCycle] Request Focus: 12020 (Sideloaded) 
24/08 15:36:51.518 {INFO} [LifeCycle] Request Location: APP 
24/08 15:36:51.518 {INFO} [LifeCycle] Push Location: APP 
24/08 15:36:51.518 {INFO} [LifeCycle] Update Location: HSW 
24/08 15:36:51.519 {INFO} [LifeCycle] Inactive Focus: 3452 (oculus-home) 
24/08 15:36:51.519 {INFO} [LifeCycle] Already Focused: 0 (Unknown) 
24/08 15:36:51.519 {INFO} [LifeCycle] enterVR() End 
24/08 15:36:54.815 {DEBUG} [Tracking:Pnp] RansacMatch: Too many outliers: 1 outliers out of 5, allowed 0 
24/08 15:36:58.592 {DEBUG} [Kernel:Default] [AppFocusObserver] UpdateTextureSetActive: Active process pid=12020 dismantling its last texture set 
24/08 15:36:58.592 {DEBUG} [Kernel:Default] [AppFocusObserver] NextProcess: Switching active rift process to pid=1336 textureset=1 (not updating active render window) 
24/08 15:36:58.592 {INFO} [LifeCycle] requestFocus() Start 
24/08 15:36:58.592 {INFO} [LifeCycle] Request Focus: 1336 (oculus-overlays) 
24/08 15:36:58.592 {INFO} [LifeCycle] Setting focus to Overlays is not allowed. 
24/08 15:36:58.592 {INFO} [LifeCycle] requestFocus() End 
24/08 15:36:58.594 {DEBUG} [Server] UpdateFocusedVirtualHmd: ConfigureTracking On (112) 
24/08 15:36:58.594 {DEBUG} [Kernel:Default] [VirtualHMD] Applying client-specific caps 
24/08 15:36:58.598 {WARNING} [Server] Setting connection focus to pid: 1336, file: oculus-overlays.exe, but no window handle exists 
24/08 15:36:58.598 {INFO} [Server] Connection closed for pid: 12020, file: Unity.exe 
24/08 15:36:58.598 {DEBUG} [Server] UpdateFocusedVirtualHmd: ConfigureTracking On (112) 
24/08 15:36:58.598 {DEBUG} [Kernel:Default] [VirtualHMD] Applying client-specific caps 
24/08 15:36:58.616 {WARNING} [Server] Setting connection focus to pid: 1336, file: oculus-overlays.exe, but no window handle exists 
24/08 15:36:58.616 {INFO} [Server] Connection destroyed for pid: 12020, file: Unity.exe 
24/08 15:37:01.456 {INFO} [DeviceEvent] SENSOR [WMTD302S600Z3S] TrackingChanged 0 
24/08 15:37:01.456 {INFO} [HardwareManager] Tracker WMTD302S600Z3S got tracking event with error code 0 
+0

這應該在魔環的論壇或超級用戶要求。除非您使用Oculus SDK編寫軟件並使用您自己的應用程序獲取黑屏,否則這不是要問的地方。 – Jherico

+0

雖然不是主題,但我遇到了同樣的問題 - 嘗試更換USB端口,可能這個端口沒有足夠的功率。 –

+0

它不僅發生在我的應用程序中,Oculus Home還顯示帶有音頻的黑屏。我試圖在我的兩個usb3端口之間切換,但沒有區別:| – wilk3ns

回答

1

幾天後,我發現了這個問題。儘管華碩ROG G751沒有啓用Optimus技術,但其HDMI端口仍與英特爾GPU相關。這就是爲什麼裂痕沒有獲得足夠的表現,並保持黑色。我嘗試了一些雷電(迷你顯示器端口)和VGA適配器。什麼都沒有解決。然後我從Oculus讀取服務器日誌,並且有人說沒有足夠的帶寬。我明白這個問題是與適配器性能有關的,所以我用4k的Mini Displayport轉HDMI適配器(下面的鏈接)和voliah! Rift正在工作!沒有滯後或任何其他問題!只需嘗試4K啓用的適配器!

這裏是一個工作適配器 - https://www.amazon.com/Macally-Aluminum-DisplayPort-Thunderbolt-MDHDMI4K/dp/B013H07SX6/ref=sr_1_fkmr0_1?ie=UTF8&qid=1472844784&sr=8-1-fkmr0&keywords=macally+mdp+hdmi