PC performance question...

[rag-time4]

Hey everyone.. just having problems with a couple games... Diablo II and Mame...

When I hit tab in Diablo II to open the automap or to open the menu in MAME, both games get super choppy....

Anyone have ideas as to what could be causing this?

[MissaFX]

Do they do this in fullscreen mode?  Or are you playing out of a window?

[rag-time4]

Mame does it in both, I'm currently reinstalling Diablo but I believe I was playing it full screen.

[MissaFX]

Mame does it in both, I'm currently reinstalling Diablo but I believe I was playing it full screen.

I have only seen this problem with diablo II on systems that had 32 megs of ram.  So my guess was you were playing it window'd and the performance was getting killed since I figured you were not using a PC that old.

[rag-time4]

Mame does it in both, I'm currently reinstalling Diablo but I believe I was playing it full screen.

I have only seen this problem with diablo II on systems that had 32 megs of ram.  So my guess was you were playing it window'd and the performance was getting killed since I figured you were not using a PC that old.

My PC has 1024 MB of RAM ... task manager tells me that about %50 of it is used...

[MissaFX]

Mame does it in both, I'm currently reinstalling Diablo but I believe I was playing it full screen.

I have only seen this problem with diablo II on systems that had 32 megs of ram.  So my guess was you were playing it window'd and the performance was getting killed since I figured you were not using a PC that old.

My PC has 1024 MB of RAM ... task manager tells me that about %50 of it is used...

What OS?

Oh and I am on chat right now, you could get live guesses via the shoutbox

[Kitsunexus]

Are you using MAME32? If so, it might be a DirectDraw issue?

[rag-time4]

What OS?

Oh and I am on chat right now, you could get live guesses via the shoutbox

I'm using the famous Windows Vista.

Are you using MAME32? If so, it might be a DirectDraw issue?

Yes MAME32... how do I find out of it's a DirectDraw issue? Could it be the same problem with Diablo II? In both cases the problem only occurs when I open up the tab menus.

[Kitsunexus]

What OS?

Oh and I am on chat right now, you could get live guesses via the shoutbox

I'm using the famous Windows Vista.

Try setting the program to only one CPU core. If that fails, it's gotta be a DirectDraw issue.

[MissaFX]

Run diablo II at 640X480 window'd and see if this still happens.  I am pretty sure in this mode it does not use direct draw.  I have not used vista for any length of time thankfully, but at least it is using close to the amount of ram it should.

[Kitsunexus]

Yes MAME32... how do I find out of it's a DirectDraw issue? Could it be the same problem with Diablo II? In both cases the problem only occurs when I open up the tab menus.

I think this might work... http://support.microsoft.com/kb/191660

[Kitsunexus]

Triple post, I'm sorry, but believe it or not, according to some sites I'm reading, it has less to do with Diablo's use of DirectDraw and more to do with Direct3D. Still no solution, but I'm continuing to look...


EDIT: Either run in Glide, or software (you will LOSE special effects if you run in software), and see if you get the same errors.

Run MAME32 in GDI mode, and see if that fixes it.


If this doesn't work, try the processor affinity settings.

If that doesn't work, make like us sensible people, uninstall Vista and run XP.

[MissaFX]

Triple post, I'm sorry, but believe it or not, according to some sites I'm reading, it has less to do with Diablo's use of DirectDraw and more to do with Direct3D. Still no solution, but I'm continuing to look...


EDIT: Either run in Glide, or software (you will LOSE special effects if you run in software), and see if you get the same errors.

Run MAME32 in GDI mode, and see if that fixes it.


If this doesn't work, try the processor affinity settings.

If that doesn't work, make like us sensible people, uninstall Vista and run XP.

There's a simply checkbox to disable direct3D in D2 unless I am mistaken as well.

[SignOfZeta]

I think you just need to ditch Vista and go back to XP.

[MissaFX]

I think you just need to ditch Vista and go back to XP 2000.

Fixed.