Existing users, 
 Diablo II Update Patch - 1.12aupdate for the real time action role playing game |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
RAVE in OS… 
- Version: 1.09d, 1/27/2003 05:27PM PST
(1 of 1 users found this comment useful)
Aetnaria
9 is flawless. D2 LOD v1.09d also runs well in classic (on OS 10.2.3) if you use Software for rendering (some things didn't display properly in RAVE on Classic, haven't bothered w/ OpenGL). I can't recall the last time it's crashed, but it's been ages... so maybe the product isn't *perfect* but that's not from lack of trying.
Everything looks great… 
- Version: 1.09d, 1/21/2003 11:21PM PST
inspired
over here, except...I notice that when claw vipers hit my character with their freeze-bash attack, my character will occasionally freeze (literally) in a painful-looking pose, unable to move at all, even after thawing. The only fix is to either 1) pray that I get hit again and knocked back into commission, or 2) save and quit. Oops.
This update doesn't… - Version: 1.09d, 8/21/2002 02:29AM PST
(0 of 1 users found this comment useful)
Merism
work under 10.2 jaguar.. blizzard do you even care about diablo 2 anymore, let alone the mac users? Sigh.
Addition to my… - Version: 1.09d, 11/22/2001 01:03PM PST
CynicalBug
previous comment: going back to the 1.0.9b patch, and then signing to to battle.net for the update worked, I can play again, and my version is now 1.0.9d. If you have access to battle.net, I'd try that instead of the version of the patch linked here at VersionTracker.
Something is really… - Version: 1.09d, 11/22/2001 09:44AM PST
CynicalBug
really wrong with this patch, last night I could play fine, today I can't play at all, quits with a strange not enough memory error. I'm going back to patch 1.0.9b
put it at… - Version: 1.09d, 11/21/2001 02:45PM PST
MysticalOS
software rendering, it's a flaw in the nvidia hardware, even PC's have the problem if they have a nvidia card. the nvidia hardware overuses clock cycles at drawing detailed texture tiles which is what all diablo II is, it runs SLOWER in opengl then it does in software rendering. This has almost no chance of ever being fixed, only solution is to go to an ati card or live with it. blizzard DID say when t he game is ported ot mac os x it would be a bit better however since it has a better opengl driver base but the hardware limitation in the nvidia card will always remain.
Re: jaymacgthree's comments… - Version: 1.09d, 11/21/2001 09:31AM PST
srhyne
-- it's my understanding that only OpenGL takes whatever memory is available/needed regardless of the allocation set in "Get Info." When using 3dfx or Rave, using "Get Info" is the only way to give the game more memory.
Guys- my iBook… - Version: 1.09d, 11/21/2001 07:45AM PST
jaymacgthree
300mhz maxes Diablo at 27fps with no hardware acceleration. It doesn't make a difference whether you have 1.5 gigs of ram or 128, Diablo takes what it need. I incidently have 96 megs. One thing to remember is NEVER use get info to change the ram allocation you will end up with it performing terribly and you will need to reset it to the default. OS X version is wanted badly over here Bliz.
