n.b. as mentioned in another thread ..
https://forums.frontier.co.uk/showthread.php?p=4619400&viewfull=1#post4619400
.. "OCT" is a typo (although it's not clear to me at least what it's actually supposed to say).
Asynchronous Spacewarp - Big Improvement?
- Thread starter Nebula109
- Start date
n.b. as mentioned in another thread ..
https://forums.frontier.co.uk/showthread.php?p=4619400&viewfull=1#post4619400
.. "OCT" is a typo (although it's not clear to me at least what it's actually supposed to say).
Pretty sure it is 1.25
As you r not showing up anymore i wonder what happened.
Lost in speedy VR? Blown up DK2?
So just done a bit more testing on the ASW front leaving it in auto rather than enabled and maxed out the GFX settings. Also hacked the configs to run 6k textures and set oculus debug tool to 1.5 PD. Running on an overlcocked Pascal TitanX on water I think the hardware with ASW on auto handles max settings extremely well only once dropping to ASW on planetary landing. Threw together the following VID if anyone's interested what the max with current hardware can accomplish.
Check the VID https://youtu.be/UZ83vJDsQmU
Happy to have a geek discussion on how I got the game to this point.
Check the VID https://youtu.be/UZ83vJDsQmU
Happy to have a geek discussion on how I got the game to this point.
What is that all, someone here has everything maxed with 2.0SS on a GTX 1080...No water cooling or anything fancy. Honest just ask him... /sarcasm
Last edited:
I am not sure it is working for me..... I added the registry keys as per OP, and using the oculus dev performance to monitor, the FPS never drops to 45, regardless of trying ctrl 1,2,3,4 etc, its always 80-90.
Although on the other hand, I am running Ultra settings with 1.5 pd in dev tool, and flying around a planetary base is buttery smooth, seems smoother than before at those settings (latest Nvidia driver).
Although on the other hand, I am running Ultra settings with 1.5 pd in dev tool, and flying around a planetary base is buttery smooth, seems smoother than before at those settings (latest Nvidia driver).
Also running Titan XP (stock) - with i7-5930, M.2 SSD, W10 64bit and latest nvidia driver.
Gave ASW a whirl last night (set to auto I think) - initial impression with 1.0 s/s and 1.5 DB (mostly max settings) it was incredibly smooth and I only noticed the drop to 45FPS a couple of times (viewed in DB HUD) during an hour or so whilst in busy battles at nav beacon. The rest of the time is stayed at a rock solid 90. I need more time to try different combo's to find a good balance.
One thing that immediately struck me is how much more 'immersive' it felt. I've no idea why that could be?!?! Maybe the smoothness, lack of judder etc sent some slightly different messages to my brain?!?
Gave ASW a whirl last night (set to auto I think) - initial impression with 1.0 s/s and 1.5 DB (mostly max settings) it was incredibly smooth and I only noticed the drop to 45FPS a couple of times (viewed in DB HUD) during an hour or so whilst in busy battles at nav beacon. The rest of the time is stayed at a rock solid 90. I need more time to try different combo's to find a good balance.
One thing that immediately struck me is how much more 'immersive' it felt. I've no idea why that could be?!?! Maybe the smoothness, lack of judder etc sent some slightly different messages to my brain?!?
Last edited:
note that i said that I HAVE NOT enabled AWS..which leads me to believe that it is entirely possible that WITH AWS the judder could be eliminated even at the highest settings. so yeah...
Last edited:
I'm not liking ASW. I have a 1080GTX and have tried if for a few hours. If I hit CTRL - F it shows 45FPS in the windowed display on my monitor which I assume means that ASW is working.
It seems to create odd judder for me. Strange distortions when scrolling through menus (like commodoties). Distortion when spinning round the galaxy map. Not liking it at all. It seems to make things worse for me.
It seems to create odd judder for me. Strange distortions when scrolling through menus (like commodoties). Distortion when spinning round the galaxy map. Not liking it at all. It seems to make things worse for me.
It halves the frame rate and interpolates.
Spinning space stations can 'skip' now and then if you sit and watch them so I guess depending on how good your system is you may see more or less of this sort of thing.
Generally, if you have a decent enough rig in the first place you're not going to eek out much more with this and as you say, sometimes actually make it worse.
Spinning space stations can 'skip' now and then if you sit and watch them so I guess depending on how good your system is you may see more or less of this sort of thing.
Generally, if you have a decent enough rig in the first place you're not going to eek out much more with this and as you say, sometimes actually make it worse.
![[HJ]-RedRaven](https://forums-cdn.zaonce.net/data/avatars/m/67/67389.jpg?1553527112){kind=avatar}
Set the Debug Tool HUD to App Render Timings - that way you can see the time it takes the GPU to render your frames. Switching Ctrl-Numpad 1 is the original native mode, going to 4 will enable ASW and you'll see the left hand graph drop to 45fps if ASW is having to work. If its staying at 90, then your Titan is managing to finish rendering while meeting the 11.1ms deadline much more of the time and thus staying out of ATW and out of ASW too.
You guys on a Titan X Pascal might have a fair bit more power to throw at ED compared to even the 1080GTX.
On a 1080GTX, my experience seems to be much closer to CylonSurfer; that is I'm spending quite a lot of time at 45fps unless I drop to Low-medium settings.
Will try kicking all the settings to max tonight and see what ASW makes of that. My slideshow awaits, I feel.
On the bright side, if ASW allows the GPU up to 20ms or so to render (1/45 sec with a bit for ASW/compositor), you're rendering slower, but setting higher detail means you're giving ASW a much better sample to begin with.
So you'd want ALL of that 20ms taken up in GPU rendering.
Presumably rendering over 20ms will give you a lot of judder as you'll miss two deadlines and be at 30fps with ASW trying to make up two frames for every finished render. Yuk.
I think there's different way to skin the cat here depending on sensitivity to the judder (in normal piloting scenarios, not looking out of the cockpit 90 degrees left/right and rolling like a demented porpoise looking for artifacts)...
Nice vid!
Two queries -
Which frame rate/temp counter are you using (purple text, top left of monitor screen?
And which capture program for the video?
![[VR] Frank_G](https://forums-cdn.zaonce.net/data/avatars/m/59/59394.jpg?1553527111){kind=avatar}
I have sessions with and without judder. Its not consistant. The first time i tried, i got excellent performance in VR ultra, next day i got judder at VR high in the same scene. Tweaking the settings did not affect judder unless going to VR medium. Something isnt working as expected yet.
I assume that is why it is not already enabled by default. They said on Conn3ct, ASW will be a runtime version or two away, before they enable it for public use. We are looking at prototype software here. But i guess, they are pretty confident, otherwise they wouldnt have lowered the low end specs.
Agree, Oculus will be several builds ahead of what is in the wild (v1.8.0) and will be much closer to solving those issues.
Hopefully the artifacting in the menus will be reduced, and the shimmering SRV cockpit too (Aaargh I'm melting in 1970's Blake's Seven transporter beam style!)
After doing some more testing in beta last night, its not a magic bullet.
Once a res got jumping with three commanders, ice rocks and of course a butt load of npcs things would reduce to a right mess.
But this was at ultra fidelity, I would scale it back somewhat.
And of course there's always been a huge drop in performance when a wing instance gets busy.
And of course the servers last night was glitchy at best.
As it stands I would personally like to increase shadow fidelity and terrain quality rather than squeeze a higher multiplier.
But this is in deed a very good improvement.
Once a res got jumping with three commanders, ice rocks and of course a butt load of npcs things would reduce to a right mess.
But this was at ultra fidelity, I would scale it back somewhat.
And of course there's always been a huge drop in performance when a wing instance gets busy.
And of course the servers last night was glitchy at best.
As it stands I would personally like to increase shadow fidelity and terrain quality rather than squeeze a higher multiplier.
But this is in deed a very good improvement.
Last edited:
Hi, 6k textures are set in the graphics config file. I did another vid that shows the graphics settings at the beginning of the vid. Just change the galaxy background and planet textures to 6144 in the appropriate places. https://youtu.be/nSx4xriHuxI
- - - - - Additional Content Posted / Auto Merge - - - - -
Hi, I was using MSI Afterburner with Riva tuner statistics server for the OSD and capturing using the Nvidia Shadow Play app for video capture.
- - - - - Additional Content Posted / Auto Merge - - - - -
Hi, I was using MSI Afterburner with Riva tuner statistics server for the OSD and capturing using the Nvidia Shadow Play app for video capture.
in case of AMD...
The Radeon drivers support ASW now:
On an official AMD Radeon webpage they refer to the QRQ feature as a technical basis. That QRQ would only need GCN gen2 GPUs, so there is still hope AMD enables this also for Fury and 280/380+ models....
I tested it on W10 with RX480, those drivers and Crimson 16-10-2 and Oculus V1.9 without any luck so far, no toggling for ASW possible, no difference in DebugTool performance meter ....[sad]
I'm guessing we need Oculus V2.0 to have it working on AMDs GPUs as well...
The Radeon drivers support ASW now:
but only for the new Polaris ones. Since RX 460 is not fast enough the RX 470 is minimum requirement so far.AMD Radeon-Software-Crimson-Edition-16-10-1-Release-Notes said:
On an official AMD Radeon webpage they refer to the QRQ feature as a technical basis. That QRQ would only need GCN gen2 GPUs, so there is still hope AMD enables this also for Fury and 280/380+ models....
I tested it on W10 with RX480, those drivers and Crimson 16-10-2 and Oculus V1.9 without any luck so far, no toggling for ASW possible, no difference in DebugTool performance meter ....[sad]
I'm guessing we need Oculus V2.0 to have it working on AMDs GPUs as well...
Last edited:
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.
Still those ocasional stuttering, here and there, and between all the modes... i found better not to use it.