The problem I'm having is getting Diablo 2 LOD to start up in Directdraw mode. I'm running Windows 7 on a new Netbook(ASUS eeepc 1005HA). The game starts fine in D3D, but will slow down when a number of enemies are on the screen; it makes the game a lot less fun. The game will start in directdraw in windowed mode, but I don't want to play it in windowed mode because the screen on my netbook is only 10 inches.
The game WILL start in Directdraw in fullscreen, but it takes about 5-10 minutes to load and the colors are messed up. There is a lot of bright green where there shouldn't be. Also, during the load it displays random numbers and characters in the very top left corner of the screen. I've tried a couple combinations of compatibility modes and administrator privilege, but none seem to have any affect. Checking 640x480 causes the resolution to continually fluctuate. Finally, changing resolutions while in Windowed mode caused the game to crash.
I'm not expecting a cure all to all of these problems, but I would just like the game to load fullscreen in directdraw without having to wait 5 minutes. Does anyone have a solution or suggestion? Thanks in advance.
I also have problems with directdraw and direct3D! *Running windows 7 pro*
Almost the same as hacknslash. Messed up colors in directdraw and direct3d suddenly seems to be slower than before? hmm :/
I already turned on all compatibility options when running this game, have my latest videodrivers installed and applied all patches.
Furthermore, when I downloaded the webinstallers for the game, I couldn't seem to get the option to install the game, only to "play diablo 2" (while running the installer!?), clicking on it didnt result in anything.. The only other option that works is exit installer ;/
Anyone got a clue what this is all about?
Got an Nvidia G-Force 7900 GT
[quote name='dunhac82']I just installed 7 last week and have yet to try out D2...I will let you all know if I have problems and if I do what they are and if i fix them what i did.
update: not having any problems on my end; did the video test an it recommended direct 3D so that is what I'm using...sorry this doesn't help at all..maybe try contacting Blizz??
The problem is, that the game is poorly optimized for direct 3D. It wastes so much resources that it can stutter even on a quite good computer. Also the video test always recommends direct 3D, if your computer has 3d capability - as any computer that isn't coal-powered has.
Well, guess everything didn't work as expected.....my monitor tells me that I'm not at optimum resolution when playing and basically makes it impossible to play as this just turns off my monitor. Anyways, in contact with Samsung, Blizz and ATI right now trying to figure out how to fix it.
I do never ever post... Only read, BUT in this case i fighted a lot with that problem, with D1 and D2 to run in Windows 7, and theres no need to download / change new drivers ( Windows 7 now a days is very updated as its installation on its drivers( Original ).
And for god sake, Direct x10 is better then Direct x3 ( Diablo 1 required) and Direct x7 , and both of em never lost a function, only upgraded .
So for Windows 7 ONLY users, it may help Vista users, but again,
**** that SOLVES WINDOWS 7 PROBLEMS with OLD Diablos games ****
1- Right Click a blank area of your Background Desktop
2- Select "Resolutions of Screen"
3- Select "Advanced Configurations" -> Near bottom Right
4- It should be on "ADPTADORS" tab, if NOT choose it on the upper area, if it is, go on...
5- Click "List all Modes"
6- Choose 800x600 High Color (16-Bits), of the same REFRESH RATE your monitor is set at the moment ( Usually 60hrz )
7- Apply Changes, and play game !!!
8- Undo em to be normal again...
Hope it helps, some options may vary in names as i?m using Portuguese Windows 7, BUT the sense of their name will that...
The color problem, is solved with that ( 32-Bits on Vista and WIndows 7 gives problems with Diablos games, and changing back is harder then on XP )
Dx10 is not fixed function. 32bit Z is available to Shader targets
Dx7 is. 32bit Z is not available to Fixed targets. They restricted it to 24bit precision (reason why NFS4 runs slow, but the Porsche unleashed Dx7a file fixes it)
Diablo does not use DX10 regardless of the os you are using having it. Actually, the majority of Dx below 8 are emulated via Dx9 ever since XP, which is why Fixed targets lost the ability to use 32b Z with XP SP1.
[quote name='squall leonhart']Though i don't like your chances for playing it to much anyway as Windows 7 and DirectDraw have a freezing issue that occurs on pretty much any game at random.
Negatory, I've not had a problem with 7 across any of my games, nor have my circle. (Not trying to cock you, just attempting to help narrow down problems. )
Private Mod Note
Rollback Post to RevisionRollBack
Join the Irish Mob. We like almost everybody. Read Pants are Good. It's funny. You'll like it.
Also read Wintendo, as DINGBANG is attempting to play through 764 SNES games in a back catalog.
its verified across my own circle to occur in Age of Empires series, War2 BNE, Starcraft, Diablo, Worms Armageddon, Pharaoh, Majesty, HoMM, Simtunes and Fallout. I've verified the first 3 so far and a friend who was creating a app to automatically fix the colour issue by pausing explorer on the launch of a ddraw app has verified it with others.
Its a display and input freeze, while background tasks continue to work fine.
Accordingly, you can find plenty of info on it around the web by googling Starcraft Windows 7, or Age of empires windows 7.
Ah well, I've a contact that will notify the Nvidia driver team, who will work with the MSFT guys if they can't find a fix.
Bitch is its a random thing. Starcraft can freeze either at start, or 15 minutes into a mission. Age of empires doesn't freeze once you're in a mission, and Pharaoh is able to be closed without taking the system with it.