Asynchronous Spacewarp - Big Improvement?

[HJ]-RedRaven

[HJ]-RedRaven
Dozer.k.a.o. said:
I tryed this, excited , but with my 980ti didn't see any improvement at all.. i know it's working because when i use the 45f limit i can see the judder.

Still those ocasional stuttering, here and there, and between all the modes... i found better not to use it.
Click to expand...

Ideally, you'd leave it on the Ctrl-NumPad 4 setting - that way ASW can turn on and off by itself.
You'll be at 90fps everywhere your GPU is able to maintain it, and drop to 45fps with ASW when your GPU is falling behind.

- - - - - Additional Content Posted / Auto Merge - - - - -

woodstok said:
Hello guys,

I'm on Oculus runtime 1.9 / GTX 970 and I've just checked the service.txt log file and according to that ASW is enabled by default for me.
I've not put in a reg hack or anything.

has the latest runtime ... 1.9 ... turned on ASW by default now ?
Click to expand...

I'm pretty sure ASW isn't turned on by default yet.
 

mazi

mazi
reading the ED 2.2 release notes i figured that the Oculus LibOVR gets updated to 1.4. Since some reported working ASW and others not i wonder if this has sth to do with beta sw players only? However Oculus claims about ASW are that it works out of the box for all VR titles, so i'd hope it has not much to do with LibOVR versions. Oculus claims "improvements for ASW" with v1.9, funny sidenote ATW was introduced in readme for v1.3, but ASW never got introduced before v1.9.

When comparing the Oculus requirement for AMD with the currently released driver there is quite an offset, e.g. 16.40.xxxx vs. 16.10.xxxx. I hope we don't have to wait for the next big driver release after Crimson series, that would be towards end of November. :(

For nVidia we are currently on v375.63, so here everything is fine already

According to the Oculus dev website the requirements for ASW are
Oculus Runtime 1.9 or later
Windows 8 or later
For Nvidia, driver 373.06 or later
For AMD, driver 16.40.2311 or later

Until the minimum specification is released, we recommend the following GPUs for ASW testing:
Manufacturer Series Minimum RAM Minimum Model
Nvidia Maxwell 3GB 1060
Nvidia Pascal 4GB 960
AMD Polaris 4GB 470
Click to expand...
 

CMDR MAIN SEQUENCE

CMDR MAIN SEQUENCE
mazi said:
When comparing the Oculus requirement for AMD with the currently released driver there is quite an offset, e.g. 16.40.xxxx vs. 16.10.xxxx. I hope we don't have to wait for the next big driver release after Crimson series, that would be towards end of November. :(
Click to expand...

The current display driver version is 10.40.2911. 16.10.2 is the current Radeon Software edition.
 

mazi

mazi
hard to belive Oculus mixed up version numbers into one, so until no AMDs work i guess they are talking about the Radeon driver package, 16.x is Crimson...

my bad: just realized Crimson 16.10.2 reads 16.40.2911 in drv pack version....:eek:
 
Last edited:

dogbite

dogbite
Just so it's clear to those who haven't yet turned on ASW, it requires 1.9 now but still is not turned on and requires the registry edit. I believe I read that runtime 2.0 will have ASW enabled by default. It also needs Windows 8.1 or higher to run.
 

ZZZRonin

Z
Using 980TI with Oculus client 1.9, ASW is now enabled by default for me. I was not aware of this change until I run Elite yesterday and saw a big improvement. That's why I came here to know what cause this change.
 

mazi

mazi
Here is some more official information from Oculus on ASW. It reads that starting 9th of November the ASW is officially available. Another article goes more into details and states Oculus 1.10 Runtime.
Too bad we can't force update of the runtime/home client but have to wait for whenever they think is good for us...[sour]
 
You must log in or register to reply here.
Back
Top Bottom