Ganondor/Raistel's Lag Fix

[Abemore]

Damn, took me forever to find this thread.
I\'m going to try this and report back.

[Abemore]

Testing Complete

I see no noticable improvements.  No lack of graphical/rendering/texture loading lag.  In short, nothing has changed.  (cept that missing fence texture)

How did I measure?  I only used myself.  I went in expecting this to work, expecting things to be smoother.  I tested in the barrel room exiting the dungeon, the plaza, and just general moving about.  All the lag seemed to be in all the same places.

I see now why this thread got buried.
*sigh* oh well.

-Abe

[lostprophet]

It does work! It cut my lag in half. It\'s not promising to remove lag, and places like the temple will still run slow, but you should have noticed some kind of change as long as you followed the instructions right.

[Abemore]

I did correctly follow the instructions.
Maybe the effectiveness of this lag fix is dependent on system specs?  Mine are:

1.0Ghz Athlon
512MB DDR
64MB Geforce2 MX400

What are yours?

I have the ability to turn the \"lag fix\" on and off by renaming a file, so maybe I will run a few more tests.

[Isgrimnur]

Hmm when I tried this the game wouldn\'t even load but crashed out at start-up. This may have had something to do with one of the zip files failing to unzip properly even after I\'d downloaded it again.

[Abemore]

Nope.  The zip file you are refering to is dungeon.zip, and it is a fence texture that fails to extract.  You can see the results of that in this screen.  But this does not affect game crashing.

The instructions were poorly written.  This could be your problem.

[lostprophet]

I have way worse stats than that abemore, not sure but defintiely under 1ghz. I get slowdown but I play all my games on 640x480 anyway so I\'ve learnt to live with 5fps frame rates. I\'ll be getting a new video card soon so I can play enter the matrix, so I\'ll report back then.

[JawaSlayer]

I\'m also getting the error unzipping a certain file (dungeon.zip), and I get the following error while loading the client:

The instruction at \"0x0bc82608\" referenced memory at \"0x00000000\". The memory could not be \"read\".


I DID however notice a considerable performance jump in the parts of the client that I could access...it seems like it would work like a charm if only I got around this error.

Edit:
I\'m running Win 2k Pro with a 2ghz pentium 4, GeForce 4 card with 64 mb of ram, and 512mb system RAM.

[JiLT]

The man is right actually, it\'s very bad to run through zip files, but a load of extra strain on the computer processes.

[Skain]

well I never, against everything i thought would happen it worked a charm, my all round fps is up by about 5 - 10 but the main thing is it doesnt randomly drop anymore as a texture is loaded.

[lostprophet]

Hurrah thats scientific proof that it works. Devs take note.

[bbum]

i wonder if converting all the textures to jpg would fasten anything up

[Vengeance]

For the people whose performance improves from this fix, please post exactly what kind of computer you have and CPU in particular.

[Skain]

Win98 (until i find my goddamn winXP book)
PIII 1ghz
256Mb ram
geforce2 gfx

Edit: oh its worth saying i never d/l\'ed any of the files listed first, I could not access the dls, all ive done is got rid of the .zips and changed the paths to folders instead.

[Abemore]

After looking through the .cfg files included in the config.zip archive, I have come to the conclusion that the author of this \"fix\" is an idiot.

Many of the values set in the configuration files seem to have been changed at random and without justification.  Some keys have been set well outside acceptable range causing them to default to their original values.  Even the values of disabled/commented keys have been pointlessly changed.  

In addition, I see no reason to edit vfs.cfg or extract awsdef.zip.

Just as a note, if you\'re going to modify something, you might want to know what you\'re doing.