Rolds Posted October 31, 2018 Share Posted October 31, 2018 See screenshot one, only a portion of my screen is affected by night vision, this applies to turret, isometric and binocular view. Screenshot 2 shows my graphics options. Link to comment Share on other sites More sharing options...
Rolds Posted November 9, 2018 Author Share Posted November 9, 2018 So this is starting to be a real drag, does anyone else using a single 1440 monitor get this? Link to comment Share on other sites More sharing options...
Robin_Hood Posted November 10, 2018 Share Posted November 10, 2018 Well, I tried and got this 2nd French Fighter Squadron Link to comment Share on other sites More sharing options...
Pawsie Posted November 10, 2018 Share Posted November 10, 2018 (edited) Not really the same, but I've gotten some weird stuff on pilot nvg's lately. Annoying as hell! I use normal 1920x1080 screen though 'Paws Edit: tried looking from ground perspective as well: more or less same result as both of you, Rolds and Robin_Hood. Makes night missions rather less interesting, imo, both flying and using ground units. Edited November 10, 2018 by Pawsie Link to comment Share on other sites More sharing options...
Pawsie Posted November 10, 2018 Share Posted November 10, 2018 (edited) Read something about SSAA setting in options. Let me guess: Rolds, you have SSAA set to 1.5x (not really guessing here), and Robin_Hood has 2x? I tried setting it to off, and I can see a slight shade difference in the IR image - but it works well enough to fly/drive (i-e- works both for air and ground units) Edit (again): Setting SSAA to off does not restart game. Not restarting the game left me that weird shade difference, as well as a bug that actually blocked parts of smoke etc. Set SSAA to off, restart and have another look for yourselves Edited November 10, 2018 by Pawsie Link to comment Share on other sites More sharing options...
Rolds Posted November 11, 2018 Author Share Posted November 11, 2018 Accurate note Pawsie, turning off SSAA and restarting DCS solves the problem, turning SSAA back on and restarting brings it back. Link to comment Share on other sites More sharing options...
Recommended Posts