08-30-2016 03:12 PM
In the left pane, navigate here:
Computer Configuration -> Administrative Templates -> System -> Power Management
4. In the right pane of the window shown above, double click Specify a custom active power plansetting which is Not Configured by default to get this:
5. In the above shown window, firstly click Enabled and then in the Options section, input the Custom Active Power Plan (GUID) as we copied from step 1. Click Apply followed by OK. You may close the Local Group Policy Editor now.
6: When you go back into Power Options you should see this:
Finally, if you go back into Event Viewer and select 'Windows Logs/System' you should see:
See the top one?
(Also, note underneath the top one you can see OR Home is resetting the power policy every three seconds, no wonder people are getting hdmi and sensor disconnects!)
After this, you should never see a single error associated with 'UserModePowerService'
Source:
09-05-2016 12:00 AM
Well that is interesting.
Albeit it does not explain why some people have no disconnects at all, how apparently software can have an impact on this and how some of the apparently successful workarounds may work and why we have two types of disconnect issues, the HMD and the sensor, which again do not occur for everybody.
For instance, I had HMD disconnects on the innatek card but not anymore since running the HMD from asmedia.
People also observe varying frequence of (sensor) disconnects depending on the running software. How can the HMD work fine in Oculus home but fail when applications are started? For me it was even one particular experience (using starforce copy protection) that *caused* sensor disconnects which never happened before or after (reported in separate post).
Don't know if that together with the powerplan resetting makes sense to an engineer.
However, if it does, I hope that could be fixed on Oculus side - stop resetting powerplan every few seconds. So users shouldnt be requiered to install a custom plan as descriped above.
Also people complained from day one about oculus messages flooding the windows event viewer. Maybe someone should just have an eye on that.
Greets.
09-05-2016 04:14 AM
09-05-2016 06:29 AM
DNACowboy said:
... wifi controllers are well-known to cause hardware conflicts with the Rift.
Excuse me, what?! Seems not to be too well known, thats first I hear about it. Also there is no (in-)compatibility list for wifi controllers that I know of nor is the wifi controller part of the Oculus compatibility checker.
The more components seem to interfere with the rift, the more hilarious becomes the determination of system wide rift compatibility.
I hope Oculus can find solutions to get the Rifts periphals more robust and less affected by those things.
Cheers
09-05-2016 06:33 AM
Hornet_F4C said:
DNACowboy said:
... wifi controllers are well-known to cause hardware conflicts with the Rift.
Excuse me, what?! Seems not to be too well known, thats first I hear about it.
09-05-2016 01:41 PM
09-05-2016 02:33 PM
09-06-2016 05:55 AM
09-07-2016 08:50 AM
09-07-2016 09:15 AM
VonTornefeld said:
Hornet_F4C said:
DNACowboy said:
... wifi controllers are well-known to cause hardware conflicts with the Rift.
Excuse me, what?! Seems not to be too well known, thats first I hear about it.
Strange right ?
09-07-2016 10:12 AM