View Full Version : An unsolved mystery...
ryanwigginton
03-02-11, 08:06 AM
I've been afflicted with this one on and off for as long as I can remember playing GWX+OLC. I know threads have come and gone in the past but did anyone ever figure this out? After some time away, I've come back, and again I'm suffering with the flat sun. I can add the rest of Rubini's recommended settings with success. At the moment though, with the latest nvidia drivers on the GTX280M, I can't add ANY anti-aliasing without getting the flat sun. With no AA the game looks nasty. And yet the glare is a lovely effect I don't want to be without. Must I choose one or the other or does someone have the answer to this timeless mystery?
If anyone is using a similar nvidia card and has OLC, anti-aliasing and sun glare all working in harmony, I would really appeciate your control panel settings. Thanks.
did you try OLC's "flat sun fix" ?
ryanwigginton
03-02-11, 08:38 AM
Yes, I did. Without it, I have flat sun on default nvidia control panel settings. With it, I get glare, providing I don't turn on the AA.
java`s revenge
03-02-11, 11:18 AM
Maybe these settings works also for you,
nisotropic Filtering = 16x
Antialiasing - Gamma Correction = On
Antialiasing = 8XQ
Antialiasing - supersampling
Conformant Texture Clamp = use hardware > normally "on"
Extension Limit = Off
Force Mipmaps = disable.
Multi-Display/mixed - single display performance mode
Texture filtering - off for better graphics
Texture filtering - Negative LOD bias = clamp
Texture filtering - high Quality
Texture Filtering - Trilinear Optimization = off
Triple Buffering = Off > on if you're using / forcing V-sync.
Vertical Sync = "application".
ryanwigginton
03-02-11, 12:12 PM
@java's revenge Which GPU do you have? I thought it was well known the glare effect only worked with AA up to x4.
EDIT: Also, which driver? As I don't have force mipmaps in my settings.
java`s revenge
03-02-11, 01:53 PM
I have used the a/m settings a time ago and it worked.
The gpu is a Nvidia gtx 260 and the driver version was 196.xx
drakkhen20
03-02-11, 01:58 PM
in some curious pondering slushing around in my skull.... do you have any screen shots of this "flatsun" thingy with and without the settings you described. because ive been hearing about this since i joined this site and im a huge fan of nvidia and i dont know if im missing out on this or what. because i've always had halos and glare around my sons. i just dont want to be missing something here. i need visuals to compare with mine on my computer. you say you have a gtx280M<---- the M means Mobile right so this is a laptop we are talking about here?
Frontier359
03-02-11, 03:37 PM
Turning off AA Gamma Correction in nHancer resolved the issue for me when I last ran into it.
ryanwigginton
03-03-11, 12:31 AM
I've stopped using nhancer since their updates became less frequent. Turning off my gamma correction in nvidia control panel doesn't work though -I know it has in the past.
Two comparison images:
Glare in OLC environment -no AA or nvidia tweaks.
http://img39.imageshack.us/img39/2391/sh3glare.th.jpg (http://img39.imageshack.us/i/sh3glare.jpg/)
AA and tweaks but no glare.
http://img233.imageshack.us/img233/5346/sh3noglare.th.jpg (http://img233.imageshack.us/i/sh3noglare.jpg/)
ryanwigginton
03-03-11, 03:26 AM
Ok, after adding removing mods and changing nvidia control panel settings repeatedly, it seems to be working again. I'm almost certain I'd tried these exact settings before and not sure why it suddenly decided to work again. Settings here:
AF 16x
Gamma Correction Off
AA Mode Overide
AA 4x
Transparency Super
Anisotropic Optimisation Off
LOD Bias Clamp
Texture Quality High
Trilinear Optimisation Off
Triple Buffer On
Any setting not mentioned left on default
I'm using driver version 266.58.
Still would be interesting to know why we can't go above 4x anti-aliasing.
drakkhen20
03-05-11, 03:39 PM
hhm. thats wierd because i've always had the halo unless i'm messing around with some numbers in mods. but normally i've always had it and i've had my settings on high quality and aa to 16 and all that. wierd, but atleast you figured it out. if its not broke now dont fix it i guess. lol.:D
:salute:
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.