zelayasrevenge301 Posted March 10, 2016 Posted March 10, 2016 For a while now I've been using Vividian enb with no real issues, and always used the SMAA that came as an option during the FOMOD installation.  Then out of nowhere I start up skyrim and the brightness/gamma is completely screwed up, looking way brighter than it should. I checked the skyrimprefs.ini file to see if fGamma was changed at all but it was at the 1.000 as I set before and as was instruced on the enb's nexus page. I tried a fresh reinstall of vividian and kept getting the same issue. After changing various options, I realized that when EnableProxyLibrary was set to true with ProxyLibrary=d3d9_smaa.dll, I would get the brightness issue. When EnableProxyLibrary was set to false, the brightness would be normal but I wouldn't get the antialiasing that I'd gotten used to from SMAA.  Is there any reason for this to be happening? My best guess is that it has to do with the fact that I'm using the latest version of enbseries (v. 305) and that there may be conflicts with this version since vividian is designed around v 269 (though I used 305 with vividian before without any issues, and the author says it can be used with the latest ENB).  Here's what my enblocal looks like right now:  [PROXY]EnableProxyLibrary=falseInitProxyFunctions=trueProxyLibrary=d3d9_smaa.dll  [GLOBAL]UsePatchSpeedhackWithoutGraphics=falseUseDefferedRendering=trueIgnoreCreationKit=true  [PERFORMANCE]SpeedHack=trueEnableOcclusionCulling=true  [MEMORY]ExpandSystemMemoryX64=falseReduceSystemMemoryUsage=trueDisableDriverMemoryManager=falseDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=768VideoMemorySizeMb=11564EnableCompression=falseAutodetectVideoMemorySize=false  [THREADS]DataSyncMode=2PriorityMode=3EnableUnsafeFixes=false  [MULTIHEAD]ForceVideoAdapterIndex=falseVideoAdapterIndex=0  [WINDOW]ForceBorderless=trueForceBorderlessFullscreen=true  [ENGINE]ForceAnisotropicFiltering=trueMaxAnisotropy=16ForceLodBias=falseLodBias=0.0AddDisplaySuperSamplingResolutions=falseEnableVSync=trueVSyncSkipNumFrames=0  [LIMITER]WaitBusyRenderer=falseEnableFPSLimit=falseFPSLimit=59.900002  [iNPUT]//shiftKeyCombination=16//f12KeyUseEffect=123//homeKeyFPSLimit=36//num /      106KeyShowFPS=106//print screenKeyScreenshot=44//enterKeyEditor=13//f4KeyFreeVRAM=115//BKeyBruteForce=66  [ADAPTIVEQUALITY]Enable=falseQuality=1DesiredFPS=20.0  [ANTIALIASING]EnableEdgeAA=trueEnableTemporalAA=falseEnableSubPixelAA=true  [FIX]FixGameBugs=trueFixParallaxBugs=trueFixParallaxTerrain=trueFixAliasedTextures=trueIgnoreInventory=trueFixTintGamma=trueRemoveBlur=trueFixSubSurfaceScattering=trueFixSkyReflection=trueFixCursorVisibility=trueFixLag=false  [LONGEXPOSURE]EnableLongExposureMode=falseTime=1.0BlendMax=0.0
Serithi Posted March 10, 2016 Posted March 10, 2016 I'm getting the same issue. Did you just install the latest NVIDIA drivers? It only seemed to start with that for me.
zelayasrevenge301 Posted March 10, 2016 Author Posted March 10, 2016 No I haven't done that yet. Mangaclub said that Vividian 8 will be released shortly so maybe this issue will be addressed then.
Serithi Posted March 11, 2016 Posted March 11, 2016 It only started for me after updating the drivers, i didn't make any other changes, and disabling the smaa .dll fixes it the same as you.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.