Diablo II verrrrry slow

[Guyver]

It appears that there is a common thread amongst the slow-downs.

Try creating a fixed 256MB (or larger - I use 512MB) permanent swap file.

No problems here, ever.. Under Win2K.

Guyver

[TK421]

I have tried both sizes - to no avail.
My computer is normally set to 256 perm.

An odd occurence - when hosting a multiplayer game I can get framrates in the 60s and 70s????? (SP maxes @ 25)?

Though the slow downs can be even worse in battle....

[TheMorg]

How do you get the framerate up, then? It looks smooth enough (although I do get the occasional disk-thrash), but I can't quote figures.

Great gameplay, pity about the low res graphics!

[Zoe]

Single-player mode is limited to a 25 fps cap. This is the way Blizzard wanted it, because the game speed is directly connected to frames per second. If you want to see what I mean, add this parameter to a diablo2.exe shortcut. Example:

'c:\diablo2\diablo2.exe' -fr ##

where ## is your desired FPS. I tried it at 50 and 75, and the whole game sped up like crazy. BTW, it runs very well on my system/G400.

[PeTe]

Just got the game and have played it only about 1.5hours, but no problems with w2k ( 128mb memory, 256mb pagefile ) so far..

So does someone have this problem in W2k ? or is it only w9x swappything ? =)

Pe-Te

They should have made the game in 800x600, 19" monitor ... you know what i'm talking about. =)

[orangejulius]

Yes, as mentioned above I get huge swappage after exiting Diablo II after 2 hours of solid gaming. In Win2K.

Much like the Adobe's suite of memory leaking programs, Diablo II seems to not release about 50MB of memory after exiting. But at least Adobe programs don't thrash the hard drive for 40 seconds after you exit them.

In any case, it looks like the game code is at fault and not Matrox drivers.

[[paradox]]

Indeed i found D2 to be on the slow side, but id say stick with the software (directdraw if u will) i think it looks better and is quicker than the pathetic implementation of direct3d. Cant comment on glide support though.

all i have further to say is.... 640x480 ? tsk tsk tsk.... i thought they had more brains...

[paradox]


------------------
WinME, AMD K6-2/450, GA-5aa (bios 1.3), 64Mb PC-100, Millenium G200 16Mb (bios 2.7) - (pd5.41), Quantum Fireball EL 10.2Gb, Pioneer 10x DVD, Realtek 8029AS, Vibra16, Mitsubishi Diamond View 17"

[This message has been edited by [paradox] (edited 08 July 2000).]

[Sanjuro Makabe]

I hope this will fix the error... http://www.blizzard.com/support/diab...on/patch.shtml
version 1.02 patch for Diablo 2...

List of fixes can be found here... http://www.voodooextreme.com/files/d2102.txt

------------------
Sanjuro Makabe

P!!!550E @ 733Mhz
ASUS P3V4X 1005, 4in1 4.22, AGP 4.03
128Mb PC100 C2 Ram
Matrox G400Max PD6.00 beta
SBLive! LW3.0
WinMe 4.90.2535

[shyguy]

I've played Diablo2 on two different computers, and what I found was you gotta have at least 128MB of RAM to play. My Celeron 500 with 64MB had constant swapping problems to the point of being unplayable, but I dropped in another 64MB, and problems went away.

Patch 1.02 supposedly fixed memory leak problems, but I still get them. Before I start up D2, Norton Utilities says 53.3 MB of RAM is being used. When D2 starts swapping a lot after about an hour of gameplay, I see that 160MB of RAM is being used... not good if you have 128MB of RAM.