so in theory also a combination of values could clash and crash the old ENBs and you wouldn't be able to find out which ones are responsible ?
surely i wont try to find out which maybe 2 or x combinations of function values crash the old ENBs from my side impossible but as i said i first try to recreate my .ini with my current values to see if some of the commenting maybe is causing it as i indeed use //[function]=[value,boolean] also but that never crashed before either and non of this comments crashes 192
so it sounds like somekind of parsing issue @ least i hope it is and i can get my .ini to run after it's reconstruction with the the old ENBs.
Last edited by CruNcher on 20 Jul 2013, 13:31, edited 6 times in total.
_________________
85% of graphics research is about who can finally make Sponza look good.
Jasper Bekkers EA/DICE
Perfection is the greatest enemy of photorealism.
Jorge Jimenez Activision Blizzard
Sorry I disappear early yesterday, major headache ><
Can someone post their settings for Skyrim Perf Monitor? I instantly CTD/crash with it on everytime either on load or just starting game, enb alone everything seem fine.
I guess I set a wrong setting or something :\
_________________ Intel i7-5960X @4.6GHz EK Water Cooling^^/EVGA X99 Classified/2x Asus 980ti 6GB SLI Samsung U28D590D @2160p/16GB G.Skill (DDR4)/Win10 Pro 64bit
jones81
No, the problem is different, even with 1 gb vram memory fix work good (i set limit 256 or 128 mb, don't remember), but for nvidia. As i understood, first version of the fix worked for AMD also, but by unknown reason some textures was not filled properly by game.
CruNcher
All combinations of parameters work properly, the problem is variables themselves. It's simple to find by binary search, copy half of config file from my official and run the game. Then after test copy 1/4 or remove 1/4 from copied, etc till variable will be detected.
ENBSeries wrote:jones81
No, the problem is different, even with 1 gb vram memory fix work good (i set limit 256 or 128 mb, don't remember), but for nvidia. As i understood, first version of the fix worked for AMD also, but by unknown reason some textures was not filled properly by game.
CruNcher
All combinations of parameters work properly, the problem is variables themselves. It's simple to find by binary search, copy half of config file from my official and run the game. Then after test copy 1/4 or remove 1/4 from copied, etc till variable will be detected.
Not that easy my section ordering is different then yours through to the updates (most of the new stuff is right @ the bottom) i will replace the sections of yours with mines and try to pinpoint where the old ENBs crashing maybe i can find it i have to say im interested myself due to backward compatibility what causes this crash
[PROXY]
[GLOBAL]
are the same but when in yours it's [EFFECT] mine is [FIX] and [ANTIALIASING] and stuff is all @ the very bottom (new additions)
hmm could this slow the parsing/saving btw ? if the sections aren't in a specific serial load order expected ?
_________________
85% of graphics research is about who can finally make Sponza look good.
Jasper Bekkers EA/DICE
Perfection is the greatest enemy of photorealism.
Jorge Jimenez Activision Blizzard
vamp
Yes, videocards with bigger amount of vram (NVidia) have better results.
CruNcher
You shouldn't care about performance of config reading, this process in not per frame, so sections(categories) can be anywhere.
ryaneu
When memory fix enabled, then yes, for full screen game alt+tab is the known issue. Temporaly i'll fix it by making borderless window mode instead of fullscreen, later will work on actual fix.
