This with only effect on, and everything else disabled, and only a single lite enbeffect.fx file as additional shader. There is a slight decrease using the latest version however. Nah I did understand what you meant, I just wanted to make sure that the overhead of just having ENB in was not different from version to version. I don't mind a 5 fps loss but 12 (or sometimes even 15) is unacceptable. Been like 2 hours of trial and error now, and the fps loss is still the same. It's just so strange that I can't for the life of me figure out how to get it to work with the latest enb. Would stil likle to use ENBoost on top of it, but since I'm testing a pack with parallax stuff and it is stable atm I guess I can leave it as it is for now. However in the last 3 days, using Safety Load, I have not crashed a single time - which is a personal record :P The other disadvantage is that Boris started building in ENBoost functionality from 0.221 onwards, so I unfortnately don't have that. Parallax itself doesn't have any FPS loss, or at least it is less than 1 FPS on my system.ÂĪlthough I would like to use a newer enb due to the new fixes, using 0.119 has its advantages: There is full hardware AA support. But I have fiddled quite a bit with them before and I'm sure that I did disable everything. I didn't use ENB for a month so I got a bit out of the running. Yeah such overhead also used to be largely unnoticable as well for me, but on older enb versions.
0 Comments
Leave a Reply. |