|
|
The Armory
Diablo II Strategy and Tactics
The forum for strategy questions and answers, strategy guides, and tactics discussion for Diablo II.
Questions? Read the Forum FAQ and please obey the Forum Rules.
Subject: "Bad...frames....eyes...twitching.....fist....in....monitor....."
|
Archived thread - Read only
Previous Topic |
Next Topic |
TempestTenor
Charter Member
|
14-Apr-01, 01:13 PM (GMT) |
|
"Bad...frames....eyes...twitching.....fist....in....monitor....."
|
This is killing me. The frames on D2 are very bad for me. Whenever I go to town or go to any new place, my frames will drop to about 2 for 10 seconds or so. And for about 7 of those 10 seconds, the screen is just completely frozen. But that part is all right for I can't get killed in town. But...not only does the frame rate drop when I enter a new "environment," it also drops when I encounter enemies!!! GOD DAMMIT!!! All the time!!! I'm on my merry way exploring the scenic landscape of Act 4 Hell and suddenly the screen freezes, I hear my computer making that "working" or "processing" sound, then 10 seconds later my carcass is surrounded by venom lords and corpulents. I don't have a 3d card so I've got it on software rendering. I've turned the music off, I've turned all the video options to their lowest settings. I've copied that .mpq file to my DiabloII directory. My computer is an Intel Celeron 566Mhz with 64MB of RAM and 11MB of it allocated to video memory. And as my computer savvy friend pointed out, that basically means that I have 53MB of RAM...Please...can somebody help me? Is getting more RAM the only solution to this problem??? |
|
|
Printer-friendly page | Top |
|
|
Targetam
Charter Member
|
14-Apr-01, 01:43 PM (GMT) |
|
1. "More RAM"
In response to message #0
|
My set up is similar - Celeron 500, all files copied over, music turned off, and play in 2D mode. However, I have 256MB of RAM, and rarely get into trouble with low frame rates, except when *everyone* is experiencing the lag. Heavy fire graphics will knock down my machine, but if there is that much fire on the screen, it's my own . RAM is the most likely answer, alas. -T -- Maintainer of the Unofficial Diabloii.net Amazon Forum FAQ. If you spot anything wrong in or missing from the FAQ, please let me know about it. I do accept Submissions, also. |
|
|
Printer-friendly page | Top |
|
|
|
|
vor_lord
Member since 21-Jan-03
|
14-Apr-01, 04:03 PM (GMT) |
|
3. "RE: Bad...frames....eyes...twitching.....fist....in....monitor....."
In response to message #0
|
I had a Celeron 266 (o/c to 400).... i.e. the old cacheless Celeron with 64Meg of RAM. I too ran in software mode, but with the music on. I did have a 4Meg Video card. Things would occasionally slow down (put a few necros with skeleton armies and it would be bad) and loading levels was slow, but not as bad as you describe. Allocating 11Meg of your system RAM to video RAM isn't the same as having video RAM. What is your video card? |
|
|
Printer-friendly page | Top |
|
|
|
|
BountyH
Charter Member
|
15-Apr-01, 00:12 AM (GMT) |
|
6. "Its the new 1.05B patch...."
In response to message #0
|
Ever since that came in even in Single Player the game lags like mad. I'm using a 1 GHz Thunderbird, 128MB, etc. and further more, I'm running on No-CD and Single Player still lags for about 3-5 secs at a time and is very jerky throughout the "new area loadings". Even if I TP up and down to areas I'm currently doing, the game still lags. The only consolation is there is no "freeze up, and then speed up" latency in Single Player. Blizzard wanted to make Duriel easier by preloading areas. But I think they might have accidentally pre-loaded the entire Act at a time. I'm not sure if more RAM will help. But I hope Blizzard puts it back the way it was. I'd much rather sacrifice a hireling in Duriel's Orafice than lag my entire game from Act 1 to 4. Your 64MB RAM is just minimal for Multiplayer. Maybe you can free up your system resources up somemore. I assume you know the routine to End all tasks on your computer except "Explorer" & "Systray". But you should also look into your "Network Neighborhood" to see how many Profiles you have running. eg. TCP/IP, IPX/SX, Dialup adapter, etc. Make sure that all you need there is being used to play Diablo2 (eg. Dialup if you're using modem, TCP/IP for Internet, etc) having extras of those things comsumes your system resources as well. You can also drop your graphics settings in Diablo2's Options. Hardware-wise, you can either get more RAM or get a 2D/3D Graphic card. Even some adventure games require 3D acceleration nowadays. But I'm not sure how reusable DRAM will be once P4s start using DDR and RAMBUS. That's why I got a TB instead so I can stretch the life of my RAM as well. But the main culprit is the pre-loading code in 1.05B. Blizzard just made it worst throughout game. Duriel still lags a bit (no tactical advantage, at most it gives you an extra second or 2, most players have learned to live with it already, so there is no improvement.) Just ask yourself what is the likelihood that Blizzard will set it back, then take a deep breath and next time don't take the "scenic route" in Act 4 Hell and keep your guard up.
|
|
|
Printer-friendly page | Top |
|
|
|
|
|
Mavfin
Charter Member
|
15-Apr-01, 12:22 PM (GMT) |
|
9. "RE: Its the new 1.05B patch...."
In response to message #8
|
Yeah. 256 was better, but 384 takes pretty much all of it out for me. (G4/500, 7200 RPM drive, 384 MB) Also, a P3/800, 16 MB Rage Pro 128 (nothing special) 256 MB, with a 7200 RPM drive is almost as good as the above. It's all in the configuration. It's not *just* the processor and video card. --Mavfin |
|
|
Printer-friendly page | Top |
|
|
|
|
Ajax
Charter Member
|
16-Apr-01, 03:02 AM (GMT) |
|
12. "RE: Its the new 1.05B patch...."
In response to message #6
|
I think I experienced a similar problem when the 1.05 patch was released. I have a G3 Mac with a RAGE 128 video card, and when 1.05 came out the RAGE video rendering was compatible with DII. I selected it in the options dialogue, and began drooling at the "glow" of the waypoints, and the blue/green tint on the player screen when chilled/posioned. However, I began to experience that horrible "lag" you guys are speaking of. For example, my paly would charge somebody, and when they would go to shatter, the screen would hold long enough for me to skip like 6 tracks on my stereo. I mean, it was bad. My solution? I switched the rendering from RAGE back to Software. I haven't noticed this agonizing pausing stuff any more. Hope this helps. --Ajax "Never would he die on foreign soil, Without advancing beyond his men and his peers. His head would be turned towards the enemies' land, And he would end his days as a conqueror."(2865-2868)
|
|
|
Printer-friendly page | Top |
|
|
|
FoxBat
Charter Member
|
15-Apr-01, 05:13 PM (GMT) |
|
11. "Possible Solution"
In response to message #0
|
Ack, its the 64 megs :/ From what I heard, 92 is pretty much essential for enjoyable multiplay. This might help, but I dunno if it will work for your low mem setup: First, defrag your HD. Then, go set your virtual memory to a fixed min and max of 1.5 the size of your actual memory (so 100 megs for your system). Then, download http://www.analogx.com/contents/download/system/cb.htm and choose "gaming" preset, apply changes and reboot. This fixed my load-lag problems. BTW, doesen't this belong in the Lounge rather than the Armoury? |
|
|
Printer-friendly page | Top |
|
|
|
|
|