Something To [R]educe Lag xD

in the ini folder.. theres one file call Common <- ini file
wen u open it..
it shows things like this
wif extra lines on the bottom so dun anyhow copy and paste from here! so.. u have to edit urself

[MEM128]
3DMotionLife=15000
3DTextureLife=15000
3DEffectLife=15000
PuzzleLife=15000
PuzzlePreloadSize=1
ReadThreadPriority=0

[MEM256]
3DMotionLife=30000
3DTextureLife=30000
3DEffectLife=30000
PuzzleLife=30000
PuzzlePreloadSize=1
ReadThreadPriority=1

[MEM512]
3DMotionLife=60000
3DTextureLife=60000
3DEffectLife=60000
PuzzleLife=60000
PuzzlePreloadSize=1
ReadThreadPriority=1

as u can see.. if u max mem is lower the 3d text and stuff goes lower.. so lousier graphics if im not wrong..

so.. i set mine to 1000 those 60000 stuff then it skipped many animations and the screen keep blinking so i set to 2000 sometimes it will have too.. but i think it reduces a lot of lag so 2000-5000 is the best my current one looks like this

[MEM128]
3DMotionLife=2000
3DTextureLife=2000
3DEffectLife=2000
PuzzleLife=2000
PuzzlePreloadSize=1
ReadThreadPriority=0

[MEM256]
3DMotionLife=2000
3DTextureLife=2000
3DEffectLife=2000
PuzzleLife=2000
PuzzlePreloadSize=1
ReadThreadPriority=1

[MEM512]
3DMotionLife=2000
3DTextureLife=2000
3DEffectLife=2000
PuzzleLife=2000
PuzzlePreloadSize=1
ReadThreadPriority=1

[MEM768]
3DMotionLife=2000
3DTextureLife=2000
3DEffectLife=2000
PuzzleLife=2000
PuzzlePreloadSize=1
ReadThreadPriority=1

added 768 coz my mem 768 xDDD

duno if it works though.. hoping it helps ppl who need them :cool:

here the one editied wif 2000.. if someone know this doesnt work pls post here im stupid =(

btw i duno set higher better or set lower :( 7500 should be average

the life just means how long textures stay in memory after having been used... i'd say a minimum of 10k...

you may have just found the fix to that (usually divine hare) 3dtexturememory crash/bug...

but i thought it reduce lag huhuhu..
cuz.. it saves memory rite :cry:

but i try in tg save a lil lag or onli i imagining thingx

=P isnt he adorable ?

putting it down to 2k doesn't remove lag it creates it because so many more textures need to be loaded from hard disk into memory. You wouldn't notice in tg because you dont move in tg so the same textures stay in memory (so you're either imagining the speedup or you've done something else to speed it up).

Also, i'm near-certain adding [MEM768] won't do anything since the proggy's not looking for it, and 128 means 128+, 256 means 256+ and 512 means 512+.

what about if you do the opposite and bump the numbers up a lil so more textures are stored in memory not a huge amount just a lil granted it will take up a lil more memory but it will eliminate the transfer from hd to mem could be wrong just an idea

yeah so everything no use :(

Quote:

Originally posted by pappawolfie@Jun 19 2005, 08:48 what about if you do the opposite and bump the numbers up a lil so more textures are stored in memory not a huge amount just a lil granted it will take up a lil more memory but it will eliminate the transfer from hd to mem could be wrong just an idea

that's what you'd think but the dh crash tells me otherwise. I dont know if you use dh much but my trojan's actually had that crash himself (it happens typically when you traverse several maps using many different textures; it's that Cannot Create D3DTexture or whatever crash).

The bigger it is, the faster it will be if you run in big circles. But if you're going from one portal to another it wont help much at all (unless you use an insanely low number like 2000 - assuming it's milliseconds...)

and it does haev some use i think it can reduce crashes if you reduce the numbers a bit to say 2/3 the original numbers.