Oculus (non-steam) controls for ASW/ATW
- Thread starter vic
- Start date
They dropped the registry-thing in one of the latest runtimes, as a result it's not possible to edit ASW related stuff that way any longer.
I'm curious as why CTRL+1/2/3/4 won't work for you, though. It HAS to work, so are you 100% sure the framerate doesn't change accordingly?
Another thing you could try is using the Debug Tool wich is part of the Oculus SDK. There's an option in there to force several ASW settings on or off. You'd need to make sure to set it before booting up the game and leave it running in the background while playing.
I'm curious as why CTRL+1/2/3/4 won't work for you, though. It HAS to work, so are you 100% sure the framerate doesn't change accordingly?
Another thing you could try is using the Debug Tool wich is part of the Oculus SDK. There's an option in there to force several ASW settings on or off. You'd need to make sure to set it before booting up the game and leave it running in the background while playing.
Last edited:
Thanks for the reply. Yes I am certain that my fps are unaffected, unless it takes time before the change takes affect?! I regularly use the oculus config tool for pixel density but I could not find any way to change ASW/ATW settings in that tool. Am I missing something?
Last edited:
You are hitting Ctrl+Numpad 1/2/3/4 ?
Make sure you have downloaded a recent SDK. Although oddly the debug tool version is always 0.3, they added the ASW control in later versions of the SDK.
p.s. you can't control ATW, it's always active, unlike ASW which has to be supported by the card.
Make sure you have downloaded a recent SDK. Although oddly the debug tool version is always 0.3, they added the ASW control in later versions of the SDK.
p.s. you can't control ATW, it's always active, unlike ASW which has to be supported by the card.
Last edited:
![[HJ]-RedRaven](https://forums-cdn.zaonce.net/data/avatars/m/67/67389.jpg?1553527112){kind=avatar}
Its important to note that the NumLock has to be ON, and you're pressing the 1,2,3 or 4 on the number pad, not the number keys above q,w,e and r. (Just sayin') 
If @vic is using an older GPU ASW wouldn't work.
The GPU in your PC also has to support ASW - nVidia's 900-series or later is needed ( ie my old 780GTX can only run ATW, but not ASW). Edit: AMD R9 Fury, Fury X, and Nano are the minimum for ASW support.
If @vic is using an older GPU ASW wouldn't work.
The GPU in your PC also has to support ASW - nVidia's 900-series or later is needed ( ie my old 780GTX can only run ATW, but not ASW). Edit: AMD R9 Fury, Fury X, and Nano are the minimum for ASW support.
Last edited:
The FPS changes from switching ASW on and off are instantaneous. Press Ctrl-F to see the frame rate in the ED monitor window; the number is the raw frame rate, you will ALWAYS see 90 refreshes in VR, hence the difficulty in seeing any actual drop).
Mode 1 disables ASW and only ATW will create synthetic frames when the frame rate drops below 90fps.
Modes 2 and 3 will drop the ED frame rate to 45fps max, without/with ASW support forced.
Mode 4 is the default where ASW will turn on and off by itself. In ED, it tends to turn on a bit too quick and stays on, especially on planets and in stations/ menus.
I always turn it off as it does tend to get stuck on, even in areas where my 1080GTX will happily crunch a solid raw 90fps out. The ASW threshold is set too conservatively imo.
You don't really need to - ED has the HMD Quality setting in the graphics options which is the same setting as the Pixel Density in the Debug Tool. Unless you're using a custom setting for the HMD Quality and not the 1.0, 1.25, 1.5 etc listed in ED?
So with CTRL-F on, the fps displayed will not be affected by the ASW/ATW changes? If so then how do I know if the ASW/ATW changes happen or not?
About the oculus debug tool I think I have older one, seems there is indeed new one. Also notice there is now 2 tools one is oculusdebugtool and the other is oculusdebugtoolCLI, which should I use?
Last edited: