CV1: Smear yes (was there before), banding: yes, menus: flashes and morphing and jumping. ASW is not an improvement to me.
Last edited:
Oculus home 1.10
- Thread starter CMDR_JAMESONS
- Start date
![[HJ]-RedRaven](https://forums-cdn.zaonce.net/data/avatars/m/67/67389.jpg?1553527112){kind=avatar}
My CV1 has colour banding too, but I put it down to the gpu driver, or ED itself. I see similar colour banding on my monitor as well as in the Rift.
I don't think the Rift is limited in this regard - the Vive has reputedly better colour vibrance using the exact same panels.
I feel there's way too much expectation in the community for this first-gen hardware (and for the apps that run in VR). As a former wholesale IT rep myself I remember horrifying disparity between the marketing surrounding 3D cards like the 3Dfx Voodoo etc compared to the actual power of the cards. The marketing was long on promises and heavy with hyperbole.
Oculus does need to be more firm with their definitions and what the hardware is capable of vs software. Only a few models exist in the public hardware-wise but software could do any number of bad things to the visuals and there are already hundreds of VR-possible apps. They're certainly not going to run QA on every app title - that's up to the software developer.
Remember ED is a 'worst case scenario' for colour banding (like the lunar cinema, ugh). Plus, who here actually knows how intensive the sun coronas etc in ED are to process?
meh, I dunno, everyone seems to be an armchair expert (including me) - what we do need is more/clearer communication from FD/Oculus and FD hasn't been forthcoming on this issue.
And Oculus actually refunding CV1 owners when there's possibly nothing wrong with the hardware. Its first-gen. Deal.
I don't think the Rift is limited in this regard - the Vive has reputedly better colour vibrance using the exact same panels.
I feel there's way too much expectation in the community for this first-gen hardware (and for the apps that run in VR). As a former wholesale IT rep myself I remember horrifying disparity between the marketing surrounding 3D cards like the 3Dfx Voodoo etc compared to the actual power of the cards. The marketing was long on promises and heavy with hyperbole.
Oculus does need to be more firm with their definitions and what the hardware is capable of vs software. Only a few models exist in the public hardware-wise but software could do any number of bad things to the visuals and there are already hundreds of VR-possible apps. They're certainly not going to run QA on every app title - that's up to the software developer.
Remember ED is a 'worst case scenario' for colour banding (like the lunar cinema, ugh). Plus, who here actually knows how intensive the sun coronas etc in ED are to process?
meh, I dunno, everyone seems to be an armchair expert (including me) - what we do need is more/clearer communication from FD/Oculus and FD hasn't been forthcoming on this issue.
And Oculus actually refunding CV1 owners when there's possibly nothing wrong with the hardware. Its first-gen. Deal.
Do you guys also see "flickering" on the star background in super cruise? It'l like the black areas in the center field of view turns grey and then black again, flickering in an annoying fashion. Started with 1.10.
Color banding: yes, ASW issues: yes
ASW is really a bit annoying. MY BEAM LASERS LOOK LIKE SINE WAVES, acutally! Kinda cool, somehow..
But I must admit that it's probably due to my CPU being a bit underpowered. I always had a bit of stuttering in ED in complex scenes (large stations, inside and outside), but I didn't care, it wasn't there during combat etc. Now, ASW jumps in everywhere and makes a lot of flickering. Gonna buy me mo' powwa!
Color banding: yes, ASW issues: yes
ASW is really a bit annoying. MY BEAM LASERS LOOK LIKE SINE WAVES, acutally! Kinda cool, somehow..
But I must admit that it's probably due to my CPU being a bit underpowered. I always had a bit of stuttering in ED in complex scenes (large stations, inside and outside), but I didn't care, it wasn't there during combat etc. Now, ASW jumps in everywhere and makes a lot of flickering. Gonna buy me mo' powwa!
Last edited:
There's a thread there now: https://forums.oculus.com/community/discussion/45093/1-10-broke-elite-dangerous
Banding is definitely more apparent since 1.10.
- - - Updated - - -
I don't think your PC spec is the reason for the distortion. I personally think ASW is overrated and under-tested. I have a 1080gtx with i7-4770 and I experience exactly the same thing.
- - - Updated - - -
Do you guys also see "flickering" on the star background in super cruise? It'l like the black areas in the center field of view turns grey and then black again, flickering in an annoying fashion. Started with 1.10.
Color banding: yes, ASW issues: yes
ASW is really a bit annoying. MY BEAM LASERS LOOK LIKE SINE WAVES, acutally! Kinda cool, somehow..
I don't think your PC spec is the reason for the distortion. I personally think ASW is overrated and under-tested. I have a 1080gtx with i7-4770 and I experience exactly the same thing.
Well, at least they are looking into it.
If it was a gpu driver issue then I would have expected to see earlier drivers which were not exhibiting these color banding and color depth issues to now be suffering this. That is not the case. When I have rolled back (used DDU and clean install)and tried earlier drivers I get the same crud.
If it was Frontiers fault it would not be appearing in other titles.
That leaves Oculus runtime or firmware updates as the only other change to my system when this became an issue for me.
Glad to see Frontier making the effort to resolve and having the same suspicion that it is an Oculus created issue. Hope they soon get Oculus to remove their heads from their butts and get on board here.
I find Ctrl Alt NP1 will turn off ASW as is evidenced for me in fps reportage. The only major issue I have with ASW is some slight ripple effect I only see in DCS. I won't complain about ASW as it is barely out the door and will likely improve with future updates. I just turn it off when necessary.
If it was Frontiers fault it would not be appearing in other titles.
That leaves Oculus runtime or firmware updates as the only other change to my system when this became an issue for me.
Glad to see Frontier making the effort to resolve and having the same suspicion that it is an Oculus created issue. Hope they soon get Oculus to remove their heads from their butts and get on board here.
I find Ctrl Alt NP1 will turn off ASW as is evidenced for me in fps reportage. The only major issue I have with ASW is some slight ripple effect I only see in DCS. I won't complain about ASW as it is barely out the door and will likely improve with future updates. I just turn it off when necessary.
There's more issues with 1.10 that I'm concerned about than the ASW effects. Now my headset disconnects every couple of minutes. Takes a full PC reboot to turn it back on again, but that'll only buy me about 10-15 minutes before it happens again. The game/app is still running, just the HMD is off.
Really frustrating.
Really frustrating.
Have you turned off power mgmt. for usb?
In device manager select each usb hub, controller and also the Rift sensor. Select properties of each of these then the power management tab and untick "allow the computer to turn off this device to save power
final quote to get this closed - just in case anybody still searching on Oculus ASW issues:
Today the ASW feature works with the latest Oculus 1.11 runtime also for AMD Polaris GPUs and CPUs that don't support SSE4.1 (at least my Phenom II X6).
With the 1.10 runtime at least in my case a Ctrl-Alt-Num1 on Oculus home screen client disabled the broken ASW successfully.
Today the ASW feature works with the latest Oculus 1.11 runtime also for AMD Polaris GPUs and CPUs that don't support SSE4.1 (at least my Phenom II X6).
With the 1.10 runtime at least in my case a Ctrl-Alt-Num1 on Oculus home screen client disabled the broken ASW successfully.
Last edited: