f0tz!baerchen
Member
ok.. if high priority is useful depends on your computer.. but as said.. you can simply disable it.. ^^
but the smooth antilag should work fine now, doesnt it?
I tried it with a lot of other processes in the background (photoshop, winamp, aol, trillian, etc... winamp still played fine music, too
) and it worked properly..
well.. the smooth antilag will be useful specially for people who have lagging problems at some points because there are too many events or something similar..
when I started to make this script I simply wanted to improve Nears Event AntiLag Script because there where some things which could have been done better.. the methods werent aliased but rewritten, the sprite coordinates were checked, although this is slower than only checking the event coordinates (I tested this
) and you could not declare events which are updated even if they're not on the screen..
btw.. I changed something again..
but the smooth antilag should work fine now, doesnt it?
I tried it with a lot of other processes in the background (photoshop, winamp, aol, trillian, etc... winamp still played fine music, too
well.. the smooth antilag will be useful specially for people who have lagging problems at some points because there are too many events or something similar..
when I started to make this script I simply wanted to improve Nears Event AntiLag Script because there where some things which could have been done better.. the methods werent aliased but rewritten, the sprite coordinates were checked, although this is slower than only checking the event coordinates (I tested this
btw.. I changed something again..
Code:
$antilag.max_cpu_utilization = 70 # the maximum CPU utilization, the script
# try to stay under this value during changing
# changing the frame rate. The lower this
# value the higher will be the lag reduction
# (and the smoothness, too), [b]a value > 100
# will disable this feature completely[/b]