Page MenuHomeFeedback Tracker

Blue Flicker in SLi
Closed, ResolvedPublic

Description

I am running 2 Nvidia 560 ti and whenever I enable SLi on the Nvidia control panel and launch ARMA 3 the game will flicker blue and the proper colour. This does not happen with any other game.

Details

Legacy ID
1614540225
Severity
Major
Resolution
Unable To Duplicate
Reproducibility
Have Not Tried
Category
Performance
Steps To Reproduce

Run SLi on the cards and Launch ARMA 3

Event Timeline

OsirisVM edited Steps To Reproduce. (Show Details)Mar 9 2013, 2:04 PM
OsirisVM edited Additional Information. (Show Details)
OsirisVM set Category to Performance.
OsirisVM set Reproducibility to Have Not Tried.
OsirisVM set Severity to Major.
OsirisVM set Resolution to Unable To Duplicate.
OsirisVM set Legacy ID to 1614540225.May 7 2016, 11:57 AM

Same issue with crossfire of HD5850 !

I have to add that I had absolutely no problem the first couple of days with my rig playing arma 3 alpha. I didn't change anything, and this flicker problem appeared from itself.

This may not be an issue with the game. A blue flicker usually indicates either a bad SLI bridge, or an improperly seated SLI bridge. Try the following:

  1. Reseat both connections on the SLI bridge and retry.
  2. If you still get flicker? Flip the SLI bridge around and try the game again
  3. Still get flicker? Replace the SLI bridge with a new one

I got this in other games and flipping the SLI bridge around worked for me. Hope this helps

EDIT: I hope this doesn't have to be stated, but please make sure you shut down your PC before attempting any of this.

Well it was not doing it with any other games at all only this one and this week it seems to have miraculously fixed itself, whether new alpha patch or the new Nvidia beta drivers now supports arma 3 I do not know

Problem solved by taking out the crossfire bridge and putting it back in, in the other way round.

Unable to reproduce in the latest dev build. Closing, since this ticket is very old and it is possible that the issue was fixed in the mean time.

However, if you are still able to reproduce the issue, please create a new ticket requesting this one be re-opened.