Jump to content

Recommended Posts

Posted

Hi Guys,

 

Has anyone else encountered a problem with the Oculus SDK in the last few days?

 

I can no longer run either 1.11 or 1.12 of the SDK because it returns a message saying "Unable to connect to service, or an HMD isn;t connected".

 

Without the SDK, there seems to be no way of disabling the incredibly annoying ASW.

 

A quick scan of the Oculus developer forums seems to suggest that there was an Oculus home update recently which has prevented the SDK from working. See here: https://forums.oculus.com/developer/discussion/49800/oculus-debug-tool-cant-connect-to-service-hmd/p1

 

I'm completely fed up with Oculus playing around with this, particularly as they are now forcing us to use ASW. I note that an Oculus Dev has posted in their forum stating that there is no current way of disabling ASW - even by editing the registry.

 

Does anyone here know of a workaround?

 

:mad:

CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit
Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System

Posted

you can disabled ASW in the registry.

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted
you can disabled ASW in the registry.

 

Thanks but from what I'm reading on the dev forum, this no longer works? It's difficult to get a definitive opinion on this!

CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit
Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System

Posted

I get the same error message when I try to start the SDK.

I7 6700K, Asus Z170 Pro Gaming, EVGA GTX1080Ti SC, 32GB DDR4 @ 3000, Win10 64, BenQ EW3270ZL 2560x1440, VPC WarBRD Base + TM Warthog Grip, TM Warthog Throttle, MFG Crosswind Rudder Pedals, Oculus Rift S

 

Posted

Can anyone confirm if the ability to disable ASW is also gone, either via registry and/or Ctrl_KP1?

 

I am trying both yet ASW seems stuck on for me whatever I do...

CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit
Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System

Posted
Looks like there is a new debug tool. Maybe there will be a new SDK too.

https://forums.oculus.com/developer/discussion/51150/download-link-for-the-oculus-debug-tool-for-1-13

 

Ah, great catch Kayos! It was just posted shortly after my post :-)

CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit
Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...