New to the forums? Click here to read the "How To" Guide.
Developer? Click here to go to the Developer Forums.
Developer? Click here to go to the Developer Forums.
4 Sensors? - Tracking issues? - Log your details here
Valuable Player
Everyone with 4 sensors,
Can you please post logs here and detail your setup like I have below?
The aim of this is not to bitch or moan, but give as much detail to the dev team as possible, I don't suggest we alter our setups, but instead give a true reflection of how we are using our rift.
I will be uploading logs after each gaming session, please do the same.
@cybereality,
Can you pass these on to the devs please? if there is any more detail required then please let us know.
As with most people that have 4 sensors i've got a small tracking issue.
on first run it's relatively flawless (but only because i have all 4 on usb 3.0)
After that it gets a little choppy (as in if you take off the headset or what have you).
It's not game breaking but dam annoying.
You will see in the logs the difference I'm sure.
The only reason i get a little bit of glitching and not the ridiculus loss of frames is because I have OVRserver_x64 priority set to real time (permanenty set using Process Hacker 2). Without that it would be unplayable.
Set up is as follows:
I've tried with the USB 2.0 for sensors 3 and 4 but i get the spiraling hand nonesence (on the left touch) as well as the issues described above.
Here are the dimensions of my setup
Can you please post logs here and detail your setup like I have below?
The aim of this is not to bitch or moan, but give as much detail to the dev team as possible, I don't suggest we alter our setups, but instead give a true reflection of how we are using our rift.
I will be uploading logs after each gaming session, please do the same.
@cybereality,
Can you pass these on to the devs please? if there is any more detail required then please let us know.
As with most people that have 4 sensors i've got a small tracking issue.
on first run it's relatively flawless (but only because i have all 4 on usb 3.0)
After that it gets a little choppy (as in if you take off the headset or what have you).
It's not game breaking but dam annoying.
You will see in the logs the difference I'm sure.
The only reason i get a little bit of glitching and not the ridiculus loss of frames is because I have OVRserver_x64 priority set to real time (permanenty set using Process Hacker 2). Without that it would be unplayable.
Set up is as follows:
| Sensor | Postition | Extention | USB Slot |
|---|---|---|---|
| HMD | Head  | 2m usb 3.0 passive extention | inateck card USB 3.0 |
| sensor 1 | front left | 3m usb 3.0 passive extention | inateck card USB 3.0 |
| sensor 2 | front right | no extention | mobo usb 3.0 |
| sensor 3 | back right | 5m USB 3.0 active extention | mobo USB 3.0 |
| sensor 4 | back left | 10m USB 3.0 active extention | inateck card USB 3.0 |
I've tried with the USB 2.0 for sensors 3 and 4 but i get the spiraling hand nonesence (on the left touch) as well as the issues described above.
Here are the dimensions of my setup
This is my forum signature.
There are many others like it, but this is mine.
There are many others like it, but this is mine.
0
Comments
it's not behaving the way it should, so i'm reporting it so it can be improved on.
it doesnt happen with 3 sensors so I'm sure reporting it is what oculus would prefer
There are many others like it, but this is mine.
There are many others like it, but this is mine.
height movement, spiralling hands, glitching to high hell!!
logs are attached, might have to drop to usb 2.0 for the rear sensors i think and maybe even back to only 3
well directly after writing this I checked task manager and had a background app using 25% cpu (dafuq!)
so that got killed, i put the headset back on and other than one or 2 minor glitches, it was pretty dam good
There are many others like it, but this is mine.
I've also had a change in setup (bought a second inatech card), and use the script at the base of the page (copy it all and paste to notepad, save as whatever.bat if you like it) to make sure power options are all set.
my setup is now as follows:
also log attached from my last session (only watched the dear angelica video, will add more as time goes on)
it looks as though the laggy hands after sleep problem is fixed (and was the only issue i was bothered about) but would be good for all you trail blazers with 4 sensors to post everything in one place. then we can have a clear outline of what does and doesnt work!
the way to get the laggy hands to dissapear is as follows:
- run set up with all 4 sensors plugged in (found this out when bug fixing, odd it never worked first time but hey ho)
bugs i've exerpienced so far:- When having my hands on my lap in home in an area i would normally get the flying hands issue (sat at my desk with maximum LED blockage), i noticed the entire virtual world moving, however it did move back.
- Every now and then in dear angelica, my guradian walls would flash up for a fraction of a second. i was nowhere near the edg of my play space each time.
Oh yeah, and @cybereality, is this useful?You never replied to the previous tag in the OP.
EDIT
for anyone wondering why i have tripple posted (i would normally never tolerate such nonesence) it's because each entry is to serve as a timeline for when issue arrise, as well as replies and such.
;@echo off<br>;Findstr -rbv ; %0 | powershell -c -<br>;goto:sCode<br><br>#Requires -Version 3.0<br>#Requires -RunAsAdministrator<br><br># This script will disable all USB power saving settings on the system, in particular those associated with the Oculus Rift or Fresco Logic controllers.<br># It should run fine on Windows 8, Windows 8.1 and Windows 10.<br># If you have Windows 7, you will need to update Powershell first. Download and install (in order):<br># 1: https://www.microsoft.com/en-us/download/details.aspx?id=42642<br># 2: https://www.microsoft.com/en-us/download/details.aspx?id=40855<br><br># To run:<br># Save the script as 'OculusUSBfix.ps1' somewhere. Open the file's properties and check 'Unblock' and click Apply.<br># Go to Start, Windows Powershell, right click and select 'Run as administrator'.<br># Type 'Set-ExecutionPolicy RemoteSigned' once to be able to run PowerShell scripts (Or 'Set-ExecutionPolicy Unrestricted' if you did not unblock the file.)<br># Go to the folder where you saved the script and run it.<br><br># These are the USB hardware IDs that we want to disable the 'Allow the computer to turn off this device to save power' setting on.<br># If you want to disable another USB devices power management, go to device manager, the properties of the device, details tab, Device ID / instance path, and copy the 'VID_nnnn&PID_nnnn' (Vendor ID and Product ID) to the following list. VID_2833 is Oculus VR LLC.<br>$DeviceIDs = (<br>"VID_2833&PID_0211", # Oculus Rift Sensor<br>"VID_2833&PID_0330", # Oculus Rift HMD<br>"VID_2833&PID_0031", # Oculus Rift HMD<br>"ROOT_HUB_FL30" # Fresco Logic xHCI (USB3) Root Hub<br>)<br><br><br># The script starts here.<br>Write-Output "Starting script to fix Oculus Rift related USB power problems, and tune Fresco Logic USB settings."<br>Write-Output "This script will not check USB driver versions or fix any physical issues. If the problem persists, the following may help:"<br>Write-Output "- Check if you are running known good USB controller drivers or update them to a newer version."<br>Write-Output "- Mount the sensors right-side-up."<br>Write-Output "- Do not connect more than 2 sensors to the same USB controller on USB3 ports. Either use an extra card with USB3 ports, use USB2 ports, or use a USB2 extension cable."<br>Write-Output "- Test without USB and HDMI extension cables."<br>Write-Output "- Temporarily disconnect unneeded USB devices (The dongle for the Xbox controller is known to be bad about sharing the USB bus)."<br>Write-Output "- Close down any software that might be using the CPU in the background while you play. (Steam, Origin, Battle.net, Google Drive, Dropbox, etc.)."<br><br># To track if we make changes anywhere.<br>$ChangesMade = $False<br>$IsRebootRequired=$False<br><br># Initiate a CIM session to use in the following CIM commands.<br>Try {<br> $CIM_Session = New-CimSession -ErrorAction Stop<br>} catch {<br> Throw "Could not establish a CIM session. The script cannot run."<br>}<br><br># If the 'USB 3 Link Power Management' option is currently hidden.<br>$RegPath = "Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\2a737441-1930-4402-8d77-b2bebba308a3\d4e98f31-5ffe-4ce1-be31-1b38b384c009"<br># If the USB 3 Link Power Management option exists (Windows 7 does not have this setting, so we cannot set it.)<br>If ( Test-Path $RegPath ) {<br> If ( (Get-ItemProperty -Path $RegPath).Attributes -ne 2 ) {<br> Write-Output "Unhiding the 'USB 3 Link Power Management' option in 'Power Options', 'Edit Plan settings', 'Change advanced power settings', 'USB Settings'."<br> Set-ItemProperty -Path $RegPath -Name "Attributes" -Value 2<br> # We made a change. Track this.<br> $ChangesMade = $True<br> }<br>}<br><br># Get the currently active power plan.<br>$CurrentPowerPlan = $PowerPlans | Where-Object { $_.IsActive }<br><br># Make a list of power plans in the system. We are mainly interested in the current power plan, the 'High Powerformance' power plan that the oculus changes to.<br>If ( $CurrentPowerPlan.InstanceID -like "*{a1841308-3541-4fab-bc81-f71556f20b4a}" ) {<br> # If the current power plan is the "Power Saver" power plan we are going to change all the power plans.<br> $PowerPlans = Get-CimInstance -CimSession $Cim_Session -ClassName Win32_PowerPlan -Namespace "root\cimv2\power"<br>} Else {<br> # If the current power plan is not the "Power Saver" power plan we can exclude it from our list.<br> $PowerPlans = Get-CimInstance -CimSession $Cim_Session -ClassName Win32_PowerPlan -Namespace "root\cimv2\power" | Where-Object { $_.InstanceID -notlike "*{a1841308-3541-4fab-bc81-f71556f20b4a}" }<br>}<br><br># For each power plan in our list of power plans.<br>Foreach ( $PowerPlan in $PowerPlans ) {<br> # Get the currently configured 'USB selective suspend setting' under power options.<br> $FilterString = "%$(($PowerPlan.InstanceID).SubString(($PowerPlan.InstanceID).Length-38))%AC%{48e6b7a6-50f5-4782-a5d4-53bb8f07e226}"<br> $USBSuspendSetting = Get-CimInstance -CimSession $Cim_Session -ClassName Win32_PowerSettingDataIndex -Namespace "root\cimv2\power" -Filter "InstanceID like '$FilterString'"<br><br> # If 'USB selective suspend setting' is currently enabled.<br> If ( $USBSuspendSetting.SettingIndexValue -ne 0 ) {<br> Write-Output "Changing 'Power Options', '$($PowerPlan.ElementName)', 'Change (current) plan settings', 'Change advanced power settings', 'USB settings', 'USB selective suspend setting' to Disabled."<br> $USBSuspendSetting | Set-CimInstance -CimSession $Cim_Session -Property @{SettingIndexValue = 0}<br> # If this power plan is the currently active power plan.<br> If ( $PowerPlan.IsActive ) {<br> Write-Output "Reactivating power plan $($PowerPlan.ElementName) to ensure our change is applied right now."<br> $return = Invoke-CimMethod -CimSession $Cim_Session -InputObject $PowerPlan -MethodName Activate -ErrorAction SilentlyContinue<br> If ( !$return ) {<br> Throw "There was an error while applying the power policy change."<br> }<br> }<br> # We made a change. Track this.<br> $ChangesMade = $True<br> }<br><br> # Get the currently configured 'USB 3 Link Power Mangement' under power options.<br> $FilterString = "%$(($PowerPlan.InstanceID).SubString(($PowerPlan.InstanceID).Length-38))%AC%{d4e98f31-5ffe-4ce1-be31-1b38b384c009}"<br> $USBLinkPowerManagementSetting = Get-CimInstance -CimSession $Cim_Session -ClassName Win32_PowerSettingDataIndex -Namespace "root\cimv2\power" -Filter "InstanceID like '$FilterString'"<br><br> # If the USB 3 Link Power Management option exists (Windows 7 does not have this setting, so we cannot set it.)<br> If ( $USBLinkPowerManagementSetting ) {<br> # If 'USB 3 Link Power Mangement' is not set to 'Off'<br> If ( $USBLinkPowerManagementSetting.SettingIndexValue -ne 0 ) {<br> Write-Output "Changing 'Power Options', '$($PowerPlan.ElementName)', 'Change (current) plan settings', 'Change advanced power settings', 'USB settings', 'USB 3 Link Power Mangement' to Off."<br> $USBLinkPowerManagementSetting | Set-CimInstance -CimSession $Cim_Session -Property @{SettingIndexValue = 0}<br> # If this power plan is the currently active power plan.<br> If ( $PowerPlan.IsActive ) {<br> Write-Output "Reactivating power plan $($PowerPlan.ElementName) to ensure our change is applied right now."<br> $return = Invoke-CimMethod -CimSession $Cim_Session -InputObject $PowerPlan -MethodName Activate -ErrorAction SilentlyContinue<br> If ( !$return.ReturnValue ) {<br> Throw "There was an error while applying the power policy change."<br> }<br> }<br> # We made a change. Track this.<br> $ChangesMade = $True<br> }<br> }<br>}<br><br># Get a list of all the USB devices in the system so we can find user friendly names.<br>$USBDevices = Get-CimInstance -CimSession $CIM_Session -ClassName Win32_PnPEntity -Namespace "root\cimv2"<br><br># Get a list of all devices with power management in the system.<br>$PowerDevices = Get-CimInstance -CimSession $Cim_Session -ClassName "MSPower_DeviceEnable" -Namespace "root\wmi"<br><br># For each device with power management in the system.<br>Foreach ( $PowerDevice in $PowerDevices ) {<br> # Check against the entire list of DeviceIDs defined at the beginning of the script.<br> Foreach ( $DeviceID in $DeviceIDs ) {<br> $PowerDeviceUpperCase = $PowerDevice.InstanceName.ToUpper()<br> $DeviceIDUpperCase = $DeviceID.ToUpper()<br> # Find where the USB device is the power device.<br> If ( "$PowerDeviceUpperCase" -like "*$DeviceIDUpperCase*" ) {<br> # If 'Allow the computer to turn off this device to save power' is enabled.<br> If ( $PowerDevice.Enable ) {<br> # Retrieve the name of the USB device so we can display a user friendly name.<br> $USBDevice = $USBDevices | Where-Object { $_.DeviceID -eq ($PowerDevice.InstanceName -replace "_0$") }<br> $USBDeviceName = $USBDevice.Name<br> Write-Output "Disabling 'Allow the computer to turn off this device to save power', under 'Device Manager', '$USBDeviceName', 'Properties'."<br> $PowerDevice | Set-CimInstance -CimSession $Cim_Session -Property @{Enable = $False}<br> # We made a change. Track this.<br> $ChangesMade = $True<br> }<br> }<br> }<br>}<br><br># If a driver for a Fresco Logic FL1xxx USB controller is installed.<br>If ( Test-Path -Path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FLxHCIc\Parameters ) {<br> # If the U1U2LowPower registry setting does not exist or is not set to disabled (0).<br> If ( (Get-ItemProperty -Path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FLxHCIc\Parameters).U1U2LowPower -ne 0 ) {<br> Write-Output "Adding registry key 'HKLM\SYSTEM\CurrentControlSet\Services\FLxHCIc\Parameters\U1U2LowPower' to disable low power states for Fresco Logic USB controllers."<br> Try {<br> New-ItemProperty -Path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FLxHCIc\Parameters -Name U1U2LowPower -PropertyType DWORD -Value 0 -Force | Out-Null<br> } catch {<br> Throw "Could not create registry key."<br> }<br> # We made a change. Track this.<br> $ChangesMade = $true<br> # A registry setting change will not be picked up by the driver until the computer is rebooted. Track this.<br> $IsRebootRequired = $true<br> }<br> # If the BulkInRingBuffers does not exist is not set to decimal 256.<br> If ( (Get-ItemProperty -Path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FLxHCIc\Parameters).BulkInRingBuffers -ne 256 ) {<br> Write-Output "Adding registry key 'HKLM\SYSTEM\CurrentControlSet\Services\FLxHCIc\Parameters\BulkInRingBuffers' to increase buffers for Fresco Logic USB controllers."<br> Try {<br> New-ItemProperty -Path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FLxHCIc\Parameters -Name BulkInRingBuffers -PropertyType DWORD -Value 256 -Force | Out-Null<br> } catch {<br> Throw "Could not create registry key."<br> }<br> # We made a change. Track this.<br> $ChangesMade = $true<br> # A registry setting change will not be picked up by the driver until the computer is rebooted. Track this.<br> $IsRebootRequired = $true<br> }<br>}<br><br># If we made any change.<br>If ( $ChangesMade ) { <br> If ( $IsRebootRequired ) {<br> Write-Output "Changes were applied. Due to changes in the registry for the Fresco Logic USB controller driver a REBOOT IS REQUIRED before the changes take effect."<br> } Else { <br> Try {<br> Write-Output "Restarting the Oculus VR Runtime Service to ensure it works okay."<br> # We restart the Oculus VR Runtime only if a reboot of the computer isn't required.<br> Get-Service -Name "OVRService" -ErrorAction Stop | Restart-Service -ErrorAction Stop<br> Write-Output "Changes were applied. No reboot is required."<br> } catch {<br> Write-Output "WARNING: Could not restart the Oculus VR Runtime Service. You may have to reboot before the changes take effect."<br> }<br> }<br>} Else {<br> Write-Output "No changes were needed."<br>}<br><br># Close the CIM session.<br>Remove-CimSession -CimSession $CIM_Session -ErrorAction SilentlyContinue<br><br>;:sCode<br>;echo done<br>;pause & goto :eofThere are many others like it, but this is mine.
unlikje mst who got taller, looks like i got shorter
also, my system thinks i've moved to the corner of my room as my guardian was up in front and to the left of me, and i was facing the wrong way in OH even though i was sat at my desk (which is facing forward and slightly yto the right on my play space.
logs attached for the last hour
There are many others like it, but this is mine.
hey ho, this will serve as a good timeline if nothing else.
I've raised a ticket and support havent suggested any resolve other than checking my drivers are upto date and refering me to the generic setup help files (i've clearly followed all those) so i've asked my ticket is kept open until a resolve is in place (most likely the next patch or the one after etc etc)
anywho, another hour gaming done so another set of logs
toodle pip all
There are many others like it, but this is mine.