Daube
SOH-CM-2026
In the meanwhile, I performed more tests that confirmed the responsibity of the ENB Bloom in the OOM crashes.
Basically, as long as I fly without activating the bloom, everything is fine and I can fly as much as I want. But if I activate it, the amount of used memory starts growing dramatically and when it reaches 2.3 Gb, the sim performance crawls and the OOM popup comes... or the sim crashes directly.
I was using an old version of the ENB module, one of the old 0.74 versions for GTA San Andreas. I have replaced it by the 0.75 for Oblivion, and it works a bit better. The memory consumption still raises to critical amount, but as soon as I disable the bloom, the amount of used memory goes back to a normal level. So that's at least a temporary solution/workaround for me.
The real origin of the problem is still unknown though. The ENB 0.74 GTASA has been working fine for me since more than 3 years, and that's already 1 year on my new computer. This leads me to think that the problem might come from my new video drivers that I updated two weeks ago or something like that... I'll have to investigate more.
Basically, as long as I fly without activating the bloom, everything is fine and I can fly as much as I want. But if I activate it, the amount of used memory starts growing dramatically and when it reaches 2.3 Gb, the sim performance crawls and the OOM popup comes... or the sim crashes directly.
I was using an old version of the ENB module, one of the old 0.74 versions for GTA San Andreas. I have replaced it by the 0.75 for Oblivion, and it works a bit better. The memory consumption still raises to critical amount, but as soon as I disable the bloom, the amount of used memory goes back to a normal level. So that's at least a temporary solution/workaround for me.
The real origin of the problem is still unknown though. The ENB 0.74 GTASA has been working fine for me since more than 3 years, and that's already 1 year on my new computer. This leads me to think that the problem might come from my new video drivers that I updated two weeks ago or something like that... I'll have to investigate more.
