Skalli Posted November 8, 2018 Share Posted November 8, 2018 I can confirm that it works for me. :-) It's fluid, immersive and a great experience. Thanks! And I guess I was lucky I didn't have to wait too long. :D Link to comment Share on other sites More sharing options...
Scalvert Posted November 8, 2018 Share Posted November 8, 2018 Hello all, I've not had chance to test it out properly, but the latest Vive Wireless software driver/firmware update appears to have resolved the issue for me as well. (Version: 1.20181102.0) Drivers appear to re-install correctly during the update process with no headset warnings. A quick round of Beat Saber showed no stuttering or playback issues. I can now look forward to giving it a proper shakedown over the weekend! - Steven. Link to comment Share on other sites More sharing options...
Synthesis Posted November 8, 2018 Share Posted November 8, 2018 Were you having performance issues/CPU spikes before?Thank you, -John C Link to comment Share on other sites More sharing options...
Scalvert Posted November 8, 2018 Share Posted November 8, 2018 Hi John, Apologies, I should have been a bit clearer. No, I wasn't having any CPU spikes or other performance related issues before. (At least when Wired, Wireless just didn't work at all.) It's just that while trying to find a solution to this issue, performance and stuttering seemed to be a common issue people were having with the Wireless unit. I just wanted to confirm that the patch seemed to address the issue stated, without noticing any other common issues for the short time that I was using it. - Steven. Link to comment Share on other sites More sharing options...
WSY Posted November 11, 2018 Share Posted November 11, 2018 感謝 更新玩韌體後問題解決了 thank you very much Link to comment Share on other sites More sharing options...
HackPerception Posted November 12, 2018 Share Posted November 12, 2018 Just an update, I am confirming here that the patch released on Friday the 9th was specifically targeted at hoxfixing those experiencing this cluster of errors specifically under Windows 7. If you are still seeing these errors, let us know. Link to comment Share on other sites More sharing options...
rscott Posted December 29, 2018 Share Posted December 29, 2018 It did not fix mine. After xmas it installed it freash, did a firmware update but still says Head not detected. I'm getting simular problem. But with Error Code 37 for Intel MA-USB Host PAL in device manager. Are they still working on this??? If not I need to return the product. I'm running Windows 7 Ultimate SP1. How do I check and force a firmware update. I don't know what version I have? from Log: [2018-12-29 15:17:53.724 -5 0x1330 INFO LOG] No new DisplayLink version : 1.1.33748.8682 [2018-12-29 15:17:53.724 -5 0x1330 INFO LOG] No new IntelWiGig version : 4.0.10375.24G_VR(msi) [2018-12-29 15:17:53.724 -5 0x1330 INFO LOG] No new WirelessUpdate version : 1.0.0.12 [2018-12-29 15:17:53.724 -5 0x1330 INFO LOG] No new CU version : 1.0.0.70b [2018-12-29 15:41:33.853 -5 0x550 INFO LOG] (ControlCenter)AddNewDevice [2018-12-29 15:41:34.197 -5 0x11F8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_STOPPED(3), reason = SDK_CURRENT_STATE_REASON_NOT_SCANNING(16) [2018-12-29 15:41:34.259 -5 0x11F8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_ADD_NEW_DEVICE(10), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9) [2018-12-29 15:41:34.306 -5 0x550 INFO LOG] No stored profile, enter not connected state. [2018-12-29 15:41:34.306 -5 0x550 INFO LOG] Connection Status set to 0(CONNECTION_STATUS_NOT_CONNECTED) [2018-12-29 15:41:34.306 -5 0x550 INFO LOG] Connection Status set to 1(CONNECTION_STATUS_WAITING_ADD) [2018-12-29 15:41:42.651 -5 0x11F8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTING(5), reason = SDK_CURRENT_STATE_REASON_INCOMING_CONNECTION(5) [2018-12-29 15:41:42.651 -5 0x550 INFO LOG] Connection Status set to 3(CONNECTION_STATUS_CONNECTING) [2018-12-29 15:41:43.932 -5 0x11F8 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_CONNECTED(7), reason = SDK_CURRENT_STATE_REASON_SUCCEED_TO_CONNECT(13) [2018-12-29 15:41:43.948 -5 0x1424 INFO LOG] Connection Status set to 7(CONNECTION_STATUS_PREPARING) [2018-12-29 15:41:43.948 -5 0x1424 INFO LOG] BeginMcuUpdate [2018-12-29 15:41:43.948 -5 0x10BC INFO LOG] (ControlCenter)Get dock device name : VIVE113E [2018-12-29 15:41:43.948 -5 0x10BC INFO LOG] Device Name : VIVE113E [2018-12-29 15:41:43.948 -5 0x1424 INFO LOG] MCU Update Launch OK. [2018-12-29 15:41:43.948 -5 0x10BC INFO LOG] (ControlCenter)Otp Channel 1 [2018-12-29 15:41:43.948 -5 0x10BC INFO LOG] (ControlCenter)Otp Channel 2 [2018-12-29 15:41:43.948 -5 0x10BC INFO LOG] (ControlCenter)Otp Channel 3 [2018-12-29 15:41:43.948 -5 0x10BC INFO LOG] (ControlCenter)Get dock preferred channel : Channel 3 (Player 2) [2018-12-29 15:41:43.948 -5 0x10BC INFO LOG] Preferred Channel : Channel 3 (Player 2) [2018-12-29 15:41:43.963 -5 0x10BC INFO LOG] (ControlCenter)CurrentFwVersion : 4.0.10375.22 [2018-12-29 15:41:43.963 -5 0x10BC INFO LOG] (ControlCenter)FactoryFwVersion : 4.0.10327.19 [2018-12-29 15:41:43.963 -5 0x10BC INFO LOG] (ControlCenter)NvmVersion : 8.32.2.7 [2018-12-29 15:41:43.963 -5 0x10BC INFO LOG] (ControlCenter)MacHwVersion : 6577 [2018-12-29 15:41:43.963 -5 0x10BC INFO LOG] (ControlCenter)RFEM1HwVersion : 8 [2018-12-29 15:41:43.963 -5 0x10BC INFO LOG] (ControlCenter)RFEM2HwVersion : 8 [2018-12-29 15:41:43.963 -5 0x10BC INFO LOG] (ControlCenter)ActiveFwVersion : MAIN [2018-12-29 15:41:44.916 -5 0x11F8 INFO LOG] (ControlCenter)Link Condition Change : peerSignalQuality = 4, performanceQuality = 3 [2018-12-29 15:41:53.932 -5 0x550 INFO LOG] M_Temperature=28, R_Temperature=25 [2018-12-29 15:41:53.948 -5 0x1424 INFO LOG] Connection Status set to 5(CONNECTION_STATUS_CONNECTED) [2018-12-29 15:41:56.776 -5 0xA20 INFO LOG] USB node not found 1. [2018-12-29 15:42:01.776 -5 0xA20 INFO LOG] USB node not found 2. Please help! Link to comment Share on other sites More sharing options...
rscott Posted December 29, 2018 Share Posted December 29, 2018 I checked in the tool its using: Version: 1.20181102.0 Still doesnt work! Link to comment Share on other sites More sharing options...
rscott Posted December 29, 2018 Share Posted December 29, 2018 The message in device manager is; Windows cannot initialize the device driver for this hardware. (Code 37) Link to comment Share on other sites More sharing options...
dzimbeck Posted July 8, 2019 Share Posted July 8, 2019 Same problem, the PAL driver says windows cannot itialize the driver. The headset pairs but will never connect. Windows 7 64 Intel and I bought Intel just so it would work with this wireless headset according to forums, so now I've spent money on that and no solution. Please help fix this I will pay whatever you guys want. I just want this thing to work. I can't stand Windows 10 and will do whatever it takes to avoid it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now