The particular issue may by now be fixed, but a google search had this as a top result, so I wanted to share my experience. I had whole screen flickering, and a blue tint to the entire screen, even on the intro screen with 2x 970's in SLI, occasionally getting the broccoli error. Swapping around the SLI cable fixed the blue shift, but the flickering, as if one card's rendered frame was not being displayed was constant. The fix was to add Destiny 2 to the Nvidia control panel, 3D settings tab, and change the SLI rendering mode to "Force alternative frame rendering 2". Fixed the flicker and both cards are running around 60% usage with max settings.

Hello Patch 1.1.4.0 Same shit, different patch.

Hello Patch 1.1.3.0 No Fix.

Patch 1.1.2.1 Still flickering. But the game is dead any way. So why bother.

Hello, Patch 1.1.2 is here. And ................................. https://youtu.be/Y-gRTFRvmfU Still flickering. It is even worse than with 1.1.1.3 patch. Seams nobody @Bungie gives a sh.... about this. PS: System is AMD 1950x with 32 GB RAM and 2x GTX 1080 SLI

Delete

Seem to have found a minor fix everyone. I currently have 2 1080s as well. Going into the program settings for destiny 2 in the Nvidia Control panel this is what I set: -I hard locked max pre rendered frames to 1 -I hard locked OpenGL rendering GPU to GPU 1 -I hard locked SLI to alternate frame rendering on GPU 2 -I did not change my process priority but I did change my core affinity to 0,2,4, and 6. Clearly its gonna give you a performance hit but I get 60 fps (with cvars cap enabled) and minor stutter but nowhere near as bad as the performance I was getting on default SLI settings (massive stuttering with a "frame rate" *BS in game frame counter* of 190 fps avg.) *That 60 fps is with max settings at 3840x1600 res, 85 on the FOV, and in game vsynch off* P.S. all drivers are up to date, no monitoring software running, Blizzard app set to close on game start, system set to max performance on power and performance mode in the windows settings (meaning no cool windows animations lmao). P.P.S. Vsynch on in game is a whole nother issue with me, only game I own (out of 195) that vsynch drops FPS globally by 30-40 frames when enabled in game. P.P.P.S. Can someone on the dedicated PC team who actually works on this game please figure this out.

January 12, 2018 This problem still exists. Two of our three gaming rigs that play Destiny2 have this problem. Only non-SLI performs without this issue. The basics of the two SLI machines involved here are: i7-8700K @5ghz Asus Maximus X MB 32gb ddr4 2x Asus Strix GTX 1080i 11g oc models gpu clocks=1.8Ghz Custom Loop liquid cooling. CPU and GPU's are liquid cooled. All temps are nominal and the machine is completely stable. I had been running the Vid cards at 2Ghz+ but slowed them just to be sure of stability for this exact problem. i5-3770K @4.8Ghz Asus Z77 based MB (cant recall offhand) 16gb ddr3 2x MSI GTX 970 4gb OC edition running a mild overclock. CPU uses a Corsair H115i closed loop cooling solution. GPU's Stock Air cooled from MSI with Thermal Paste upgraded to Thermal Grizzly. Again all temps nominal and machine has run completely stable for over a year. I have run both computers at stock speeds and with just about every setting in between and nothing seems to really help. I have made sure to eliminate all possible background software etc. as well and only run with Bnet and D2 executing. No antivirus... nothing. Both computers are completely stable and post extremely healthy benchmarking scores via 3DMark etc. and are solid with every benchmark and burn-in piece of software in my arsenal. I do not experience this effect in any other game of any kind. On my primary machine it runs Destiny2 in 4k at a minimum of about 150 fps and the lesser machine is no slouch at about a minimum of 90-100 fps at 4k resolutions. I have experienced the "flickering" or what seems to me to be out of sync memory tearing on each and every place mentioned by other posts before this one... and more. I would go farther and generalize that it is ALWAYS indoors, in a Dark fairly enclosed area. It can happen with or without enemies present and in or out of combat. Having said that having more enemies present and more visual effects simultaneously being displayed will DEFINITELY make it worse. It will also if allowed to continue long enough heat the GPU's up excessively and until I backed the speed on my main machine's gpu's down to 1.8Ghz if I tried to keep the effect going continuously it would heat the gpu's faster than my closed loop cooling could keep them cool and it would eventually lock up and crash the game. Which is impressive indeed as my closed loop system...is... a bit over engineered. I HAVE found one behavior in the game that will break the cycle for the moment and "reset" the issue. When it happens if I run up and stick my face right up against a dark wall for a moment or two the problem will cease for a bit until I have been back in the environment it originally began to occur for a few moments. I discovered this accidentally whilst hiding trying to get my health back during an intense battle. Also of interest. If I use a different monitor on the machine with the GTX970's and run it at the native resolution of 1920x1080 (1080p) @144hz the problem WILL NOT OCCUR. I will eventually test this on my main machine but the user of the other machine wouldn't appreciate me borrowing their monitor without just cause unexpectedly. This produces the mental question of "I wonder if it is actually just when SLI users are running at 4k resolutions or it it possible that it has to do with the frequency of the the display?" It would make sense as most SLI users are using SLI in Destiny2 in order to get really good frame rates with their 4K monitors. My troubleshooting intuition leads me to believe it may be only a problem with SLI users that are ALSO running at 4K. Many 4K monitors being used will only do 60hz at 4k resolutions so it is possible that the 60hz itself may be presenting a problem although I cannot for the life of me understand why the display frequency of the MONITOR would make the GPU itself overheat. I had not heard about turning off Gsync and turning on Vsync as a temp fix. I will try that for now, but it is a REAL problem in playing the game and completing some missions. Thanks Bungie for making a phenominal game, but I seriously hope you can get this fixed. We would be happy to help if you need more info. Just ASK US. I have been alpha and beta testing games since as far back as around 1995 and MPlayer days. Many of us know how to find and duplicate problems like this. We just need you to ask us exactly what you need us to find out for you. Thanks everyone who contributes to this thread. Bungie and anyone else can contact me on Bnet through my battletag: NeuroShock#11709 Hope this helps. -NeuroShock

Updates to new Nvidia driver today, did a complete clean install in safe mode. Fixed the flerking for like 30 minutes, it happens again. My temporary solution is to turn off GSync and use VSync instead. I have 2 x 1080 SLI 4K monitor at 100hz My GPU is powerful enough to run 100fps on 4K, so it kind fixes the issue. I'm not sure if it's a GSync issue or just driver issue overall but it is really annoying

Hello. I got the same issue with my 2x 1080 FTW I tried every driver from the NVidia 385.41 which is the Destiny 2 Beta driver until the newest 388.71. The issue can be triggered in the Tower as well. When you run to the hanger. Go in and out. It seams like it is an texture loading issue. First time you go in there is no issue. Ones you move in and out it will start to occure. My suggestion it is still aftermath of this memory leak in the game release. We have no memory leak in the sens of slowing down our FPS but it is still there. Probably to solve memory leak the game resets the memory every time you reenter the area. In lost sectors, ones you fast travel it loades everything. You move arround and it starts resetting the memory. SLI can not synchronise any more and the flickering occures. Update Destiny 2 Patch 1.1.1.2 Flickerin is still with us. This patch has not fixed the issue. https://youtu.be/jS0QrMIVy3o

it's December 28th already, im still having the same issue, has Bungie solved this yet?

My issue which is one of the cross posted ones comes and goes. Most recently I hadnt seen it in a while but then the Raid Lair had the issue appear about 3-4 times during the run. Glad you guys are looking into it because whenever it starts getting really bad it makes you want to just shut the game down.