EvilDeadAsh34 Posted April 30, 2014 Share Posted April 30, 2014 (edited) Just tried the official ENB (v0256/0.13) for DS2 and i randomly get crashes when new areas load or when i go to a loading screen for a new area. I'm not doing anything crazy intensive, i just have "force LOD" jacked up to -4.0 and i darkened it a bit. I originally thought that SSAO was causing the crashes but i am still getting them even when the effect is off. BTW, I have an AMD 6970 card and had a solid 60fps even when i maxed out all the effects. Is this a known issue or am i just lucky? P.S. I'm not using GeDoSaTo. Edited April 30, 2014 by EvilDeadAsh34 Link to comment Share on other sites More sharing options...
Guest Dro Posted May 1, 2014 Share Posted May 1, 2014 YES. no matter what enb version. AMD 290 on Win 8.1 here. Crashes when teleporting. Using Wrapper edition, the other one wasnt working at all Link to comment Share on other sites More sharing options...
EvilDeadAsh34 Posted May 1, 2014 Author Share Posted May 1, 2014 (edited) Still crashing after updating my drivers and using the newest version of ENB... This is tiring. And it seems Boris is being diificult with not wanting to be bothered with it. Hopefully he'll change his mind but for now it seems i'll not be using ENB's at all for the foreseeable future. Here's my specs if it matters, but i've seen that some NVidia users are also having the same crashing issues.Windows 7 x64amd 6970 (not crossfired currently)Catalyst 14.4ENB 0.257 (tried 0.256 as well)7200 rpm driveWasn't trying to use it with GeDoSaTo That's all i can think of. Edit: I just saw that he updated 0.257 without a version change, but alas i am still crashing when i warp. I didn't crash on launch this time surprisingly but it never crashes the very first time you install it in my experience. It only seems to crash after you change a setting or enable something. Edited May 1, 2014 by EvilDeadAsh34 Link to comment Share on other sites More sharing options...
cicala Posted May 2, 2014 Share Posted May 2, 2014 its not a client issue its something boris needs to fix... I'm testing workarounds but its code issue Link to comment Share on other sites More sharing options...
Recommended Posts