Find content
Male
Thanks for the info guys. I'm guessing I'll pass on EE for the time being.
Slight detour, since you mentioned lag in BG - I played a MegaMod install in 2009, and did a lot of work on stutter/lag. My results are in this thread:
http://www.shsforums...ad-please-help/
I found that a large part of it was just a numbers game with the number of global variables in baldur.bcs. My solution was to trim the BG1 variables that were not needed in BG2. There were a lot of them.
Has progress been made on stopping stutter in megamods by trimming global variable count?
We did some investigation regarding stuttering in infinity engine. The whole thing I attempted and discovered is documented here: http://www.shsforums...e-stuttering/
Long story short: there were different kinds of things that caused stuttering such as loopy scripts, a lot of unoptimized inventory checks, etc. But Ascension64 optimized inventory checks, all scripts seemed to be optimized yet sometimes even vanilla game started stuttering. As it turned the most mysterious kind of stuttering happened sooner or later during every playthroug when amount of variables reached about ~2k and regular scripts simply started to execute like 10-100 times slower than they are supposed to. And the reason was a very poor strategy of handling script variables when they reach certain numbers like 1024, 2048 and 4096. So when your game has 2040 variables it starts stuttering horribly. But if you add 10 more this kind of stuttering will disappear. That's what most workarounds do. Ascension64 fixed this properly in TobEx since then and similar fix is included to EE.
Bottom line is: it's not the amount of variables that cause stuttering. The engine can easily handle thousands of them. It's poor variable container design that starts working really slow when number of variables approches large power of two numbers like 2048 and 4096. The issues is fixed two years ago with TobEx.
