RIFT - Color, banding, and image warping issues. Any solutions? HELP!

I know, isn't that the weirdest thing? I've noticed when starting Elite that I get stuck with a 1280x720 Windows that render my game on my monitor. It's small but still, it's such an unnecessary thing for my video card. Without this crap I'm sure I could get at least like 5 or 10 FPS and sometimes that makes a huge difference.

Monitor Window effect on performance
I disagree - I doubt that removing the monitor window would increase performance by much, if at all. The GPU can convert the final rendered image in a trivial amount of time (fractions of a millisecond). If you raise or lower the resolution of the monitor window, it makes no effective difference to the frame rate you see. 0.1-0.2fps, perhaps? The ATW, barrel distortion and compositing function is much more complex than simply rendering to a second window and even that is only taking a tiny amount of time (still all well under a millisecond, according to Oculus).

VR app developers (and Oculus) have gone to great pains to make sure the rendering pipeline is as good as it can be given current drivers and mainstream installed GPU technology. If the monitor window sucked up any appreciable GPU resources (like 5-10fps), they'd have done away with it during the last 2-3 years of VR development.

ASW effect on colour banding = none.
I regularly turn ASW off and on, and I am familiar with the effects ASW has on the rendered image. On my GTX1080, I see no appreciable difference between the ATW-only mode (1) and the ASW-enabled modes (Ctrl-NumPad 3 and 4). Upon turning ASW off, I see less rippling in the image, particularly for the solid coloured menu items (default orange for me), and for the vertical lines in the GUI. Most evident in high-load scenes like the SRV on-planet, especially on lateral side-to-side translation.

EDIT - I was wrong - there is a noticeable shift in the colour banding if ASW is turned on. Colour banding is worsened by ASW. AW only works on Win8.1 and higher OSes, with supported GPU's. Colour banding is reduced in the ATW-only mode (Ctrl-Numpad1). Apologies.


Colour Banding discussion:
I agree with dogbite - something is happening in firmware or software. Probably within the Oculus part of the rendering.
Looking back at 2015 screenshots, the source monitor window image is comparable in terms of colour gradients - I do not think this is a problem FD have introduced. My earlier screenshots still show some colour banding, but at the 2D higher resolution it is less noticeable. In the Rift, of course, the colour banding is right in your face screaming look at me!

On the other hand, we saw hard edges on cloud blobs etc when in witchspace transition (before they updated it). This was squarely in FD's court - poor texturing. They fixed it - although a number of the same textures are used in the new transition, all the hard edges are gone. That's not Oculus. Perhaps FD can engineer their texturing to offset the Rift's colour banding issue.

As an idea, is it possible our Rift panels are 'wearing in'? Given several months of hard use (3-4 hrs per day in my case, so I'm up to nearly 400hours now).

I got a couple of decent shots last night, but an actual video might allow the colour banding to be seen as it moves across the camera sensor. Video might actually give a better image and depiction over a still camera shot. Got blasted by the wife last night as it was late "stop playing with your toy" so I'll give that a go tonight :D
 
Last edited:
On my GTX1080, I see no appreciable difference between the ATW-only mode (1) and the ASW-enabled modes (Ctrl-NumPad 3 and 4)

I don't know what to say, disabling ASW does works for me and the difference is huge. I have a Titan X with a good CPU so I don't really need ASW anyway. I wish I could take a screenshot of "with and without ASW" but I don't think that's possible? I couldn't even play the game before because the "space sky" was just an ugly mess but now, without ASW and proper gamma settings, I barely notice the color banding...
 
I don't know what to say, disabling ASW does works for me and the difference is huge. I have a Titan X with a good CPU so I don't really need ASW anyway. I wish I could take a screenshot of "with and without ASW" but I don't think that's possible? I couldn't even play the game before because the "space sky" was just an ugly mess but now, without ASW and proper gamma settings, I barely notice the color banding...

That's great! I'm on a 1080, and I agree ASW is not required so much at the high end. I just don't see any improvement in the colour banding turning it on or off (I see all the other ASW-related changes etc).
 
Tried this numerous times and unfortunatley it made no difference to color banding or anything else graphically to me.

Be aware that Oculus' "numpad hotkey" programming is a bit rubbish...

It only works with NumLock ON.

You actually have to enable NumLock, then hit Ctrl-Numpad1, or it won't do anything.



And, yes, I get exactly the same colour-banding problems in my Rift. ASW makes it really bad... but it's still noticeable with ASW off.

Side note: When I first went digging about Rift colour band issues, I found some interesting discussions on Reddit about it all (incl. the issue where ASW makes banding even worse), here.
 
ASW ON or OFF do absolutely nothing on color banding issue on my GTX 1080. It create problem on geometry as it compute estimated movement of things (like menu bar, spaceship moving, etc.) but on color chapter it change strictly nothing on banding. I was near a planet few days ago with one part in the dark and the other on on sunlight. The transition was awful. So I kept my ship stopped, and turn ASW off and on, and nothing happened. Color banding problem was their far before ASW was implemented by the way.

I also bought 2 days ago the Cmoar VR Cinema viewer on Steam and it have the same color banding issue if you turn 180 degres and look back of the theater. So I also tried ASW on and off here and same conclusion : ASW don't have any relation with colors them self (and that's seems logical if you think about the technology behind ASW).
 
Last edited:
If there is a problem with the hardware (like a sort of bandwidth limitation during the image processing in hardware), or similar, we're not likely to see anything out of Oculus.
Possibly the majority of Rift users don't see the problem, or it's not an issue for them. The first is possible, the second is likely.

I am hoping the issue lies in the Oculus software/firmware, and that it can be fixed.
I have found it gets on my nerves more an more over the past few days. A shame because I really enjoy my time in the Rift. Its not a game breaker for me, but it is disappointing.

Consider this screenshot, from the Beta3 back in 2014:
http://lavewiki.com/_media/fuel-scoop.jpg

There is a classic colour gradient banding issue.
Zoom in and some artifacting is visible from the jpeg compression, but the overall sun corona banding is very similar to what we see today in the Rift.
Why didn't we see it then? Logically, the effect is worsened in the Rift. Our eyes adjust and the effect is more easily noticed. But why is this not the case for Vive owners? (Or is it and they're just staying quiet?)
 
I don't know what to say, disabling ASW does works for me and the difference is huge. I have a Titan X with a good CPU so I don't really need ASW anyway. I wish I could take a screenshot of "with and without ASW" but I don't think that's possible? I couldn't even play the game before because the "space sky" was just an ugly mess but now, without ASW and proper gamma settings, I barely notice the color banding...

@spacehamburger - OK, I see it. My apologies mate - I normally turn ASW off and wasn't seeing the difference. Just tried it then and I can easily see the difference in colours when ASW is turned on.
God, that's horrible... cannot un-see! I tried just regular space (not near a star), and the dark black/blue nebula background breaks up badly. Near a star, the number of bands is dramatically affected... like going from 256 colours to 16!

Luckily with ASW turned OFF, the colour gradients are still banded, but not as badly as when ASW is active.

Even parts of my Python cockpit go all 256-colour-ish. Yikes.

@yololo69 - try turning ASW on and off (I just switched between Ctrl-Numpad1 and Ctrl-Numpad3) and its like chalk and cheese. Not sure what I was thinking earlier (was at work lol).
 
Last edited:
Damn, really? Are you using a Rift? Cause technically when turning on and off ASW you SHOULD see a difference. If you don't see any difference between NUM 1 to 4 then there is a problem.

Using dk2 and applying ctrl-numpad 1 to 4 (with numlock on) makes absolutely no difference to color banding when looking at nebula's. If you took the time to read the posts on this thread and forum you would see I'm not the only one, as reported by numerous rift users this does not help with banding. I'm using gtx970 .nVidia drivers. win7. Maybe windows version is the reason?!
 
Last edited:
I have a feeling oculus have this color banding issue on very low priority becuase color banding is only a big issue for us ED players and maybe one or two other apps and only when in very dark scenes. Compared to other games and apps , where scenes are mostly well lit/bright, banding is a non-issue. So our situation is a minority as far as oculus is concerned, hence not given us a fix yet. But I may be wrong on my opinion.
 
Last edited:
I wonder if there are banding problems in Eve Valkyrie? It is an Oculus launch title that takes place in space so there must be many dark scenes with planets potentially producing an hollow that have banding problems.
 
Using dk2 and applying ctrl-numpad 1 to 4 (with numlock on) makes absolutely no difference to color banding when looking at nebula's. If you took the time to read the posts on this thread and forum you would see I'm not the only one, as reported by numerous rift users this does not help with banding. I'm using gtx970 .nVidia drivers. win7. Maybe windows version is the reason?!

ASW requires Win 8.1 or higher
 
If there is a problem with the hardware (like a sort of bandwidth limitation during the image processing in hardware), or similar, we're not likely to see anything out of Oculus.
Possibly the majority of Rift users don't see the problem, or it's not an issue for them. The first is possible, the second is likely.

I am hoping the issue lies in the Oculus software/firmware, and that it can be fixed.
I have found it gets on my nerves more an more over the past few days. A shame because I really enjoy my time in the Rift. Its not a game breaker for me, but it is disappointing.

Consider this screenshot, from the Beta3 back in 2014:
http://lavewiki.com/_media/fuel-scoop.jpg

There is a classic colour gradient banding issue.
Zoom in and some artifacting is visible from the jpeg compression, but the overall sun corona banding is very similar to what we see today in the Rift.
Why didn't we see it then? Logically, the effect is worsened in the Rift. Our eyes adjust and the effect is more easily noticed. But why is this not the case for Vive owners? (Or is it and they're just staying quiet?)

Definately no in the Vive. I had both the Rift and Vive and the Rift went back - Colour banding in ED has also nothing to do with ED, but is solely a problem of Oculus as was pointed out few times in this thread. Fix will have to come from Oculus (which considering that they are not even properly acknowledging the issue might be some time for the CV1). If you want to see the issues with colour banding in Oculus just load up the Moon landing in Oculus Video or play Apollo. ED looks still rather well in comparison to the other titles. In my case, the advice by Oculus was to return it as I had it only for short while, but I understand the frustration. I could not play ED with the color banding like that.

Also your last () implying that Vive owners have banding, but possibly can't see it is surprising after your involvement in this thread (https://forums.frontier.co.uk/showthread.php/310846-Does-vive-also-have-color-banding-issues).

I get that some people are really fanboyish about one or the other headset, but when it comes to troubleshooting, being objective is the only way and objectively the Color banding in Rift is terrible for immersion and visuals. To me it affects the immersion to the same degree as did the unclear text for Vive before we got text patch and Asynch Reprojection on Vive. I just pray now that nothing gets broken on the Vive side :D and guys I hope that Oculus gets it fixed for you asap, so the two headsets just work for all users :)
 
Last edited:
Using dk2 and applying ctrl-numpad 1 to 4 (with numlock on) makes absolutely no difference to color banding when looking at nebula's. If you took the time to read the posts on this thread and forum you would see I'm not the only one, as reported by numerous rift users this does not help with banding. I'm using gtx970 .nVidia drivers. win7. Maybe windows version is the reason?!


Like I said to [HJ]-RedRaven, I don't know what to say. For me, when I turn off ASW and use proper gamma the difference is massive and instantly noticeable. It's day and night, it's 256 color vs 32 bit (almost). It's still not perfect without ASW but it's pretty darn close. I'm not imagining things and it's not a placebo affect either, I wish I could take a pictures of all the different settings. When I press CTRL + numpad1-4 the image quality changes instantly and the color banding is much MUCH less prominent.

I also saw that you're using a DK2 with Windows 7 so that might be your problem right there. I don't think Windows 7 is supported anymore and from the look of it ASW isn't even supported for Windows 7 so that might be why nothing happen when you press CTR +numpad-4.
 
Like I said to [HJ]-RedRaven, I don't know what to say. For me, when I turn off ASW and use proper gamma the difference is massive and instantly noticeable. It's day and night, it's 256 color vs 32 bit (almost). It's still not perfect without ASW but it's pretty darn close. I'm not imagining things and it's not a placebo affect either, I wish I could take a pictures of all the different settings. When I press CTRL + numpad1-4 the image quality changes instantly and the color banding is much MUCH less prominent.

I also saw that you're using a DK2 with Windows 7 so that might be your problem right there. I don't think Windows 7 is supported anymore and from the look of it ASW isn't even supported for Windows 7 so that might be why nothing happen when you press CTR +numpad-4.

Yeah you may be right there. And I do beleive you, I was just trying to let you know that that solution does not work for many of us. I'm starting to regret the decision to not upgrading to win10 for free when I had the chance!
 
Last edited:
Yeah you may be right there. And I do beleive you, I was just trying to let you know that that solution does not work for many of us. I'm starting to regret the decision to not upgrading to win10 for free when I had the chance!

The only reason I upgraded to Win 10 was to play with ASW which I find I turn off most of the time anyway. It does have some advantages in DCS for me but introduces graphics ripples on occasion, so there are trade offs. I do hope this will disappear as it matures. You could still upgrade to Win 10 this way. https://www.microsoft.com/en-us/accessibility/windows10upgrade. There are no checks as to whether you actually use accessibility features. It just upgrades your Win 7.
 
About Warping

With all the color issues being of primary concern, I forgot to address the Warping issue. Because I store my Rift of to the side of the room and place it center and go on each session, I didn't realize I should realize re-center it in Oculus home and would just true up my center in each game I played. There then seems to be a slight deviation as to where center is for the Rift. If you see Warping re-center in OH before starting your game. Solved this for me. Hope that helps.
 
Last edited:
About Warping

With all the color issues being of primary concern, I forgot to address the Warping issue. Because I store my Rift of to the side of the room and place it center and go on each session, I didn't realize I should realize re-center it in Oculus home and would just true up my center in each game I played. There then seems to be a slight deviation as to where center is for the Rift. If you see Warping re-center in OH before starting your game. Solved this for me. Hope that helps.

For anyone like like me who's a bit particular about this, there's an ED reset HMD thingy (soz, I've been drinking) you can bind to reset centre. I have this bound to a joystick button and hit it frequently.
 
The whole discussion has gotten tired fix it already stop pointing fingers FD and Oculus work together and get it solved, enough!
 
I don't know what to say, disabling ASW does works for me and the difference is huge. I have a Titan X with a good CPU so I don't really need ASW anyway. I wish I could take a screenshot of "with and without ASW" but I don't think that's possible? I couldn't even play the game before because the "space sky" was just an ugly mess but now, without ASW and proper gamma settings, I barely notice the color banding...

Took your advice Spaceham and did a little tinkering. Found that I still had some keys bound to Numpad 1,2,3,4 from voice attack. Killed those and shut off ASW. Turned my gamma down to what you show and the result is dramatic. Can still see some banding if I turn away from a star when I drop in then look back at it but not even nearly as pronounced. this is a major improvement probably 60-70%. Appreciate the find have some rep dude. Thanks how do you like that Titan? This really is the main game I am interested in and thinking about selling off the 1080 and making that last purchase until something big. Give us some feedback please.

Still a bit blotchy and colors not what they should be but much better also notice certain areas of space just look better Maia looks much better with these settings but head back into the bubble and it seems to get worse, I don't know just wish they would get this fixed period.
 
Last edited:

As an idea, is it possible our Rift panels are 'wearing in'? Given several months of hard use (3-4 hrs per day in my case, so I'm up to nearly 400hours now).


i dont think so. the banding/black issues appeared for me after installing runtime 1.3. It affected elite and a few other titles. with the newer runtimes it makes no difference if i use my cv1 or dk2 so its not the hardware.

ive not touched my pc config either, same installation of windows 10, same 980ti installed as when i was running 0.8.
im using an lcd tv as my monitor, thats the only part of my setup i could think is non standard(but i was using it on 0.8 too and it was fine).
 
Back
Top Bottom