Missile Command Video issue

[ABArcade]

I upgraded the computer in my MAME cab and now Missile Command does not work.  All I see is horizontal lines.  All other games still work fine.  I have tried ddraw and d3d both have the same result.  I'm running MAME 115.  Anyone have any ideas?

[Tafoid]

You picked the one major version that had a regression in this particular game due to other changes.  The problem existed from MAME 0.114u4 to 0.115u1  -  http://www.mametesters.org/mantis/view.php?id=700

If you want that game playable, try 0.114 or 0.116.

[jasonbar]

Howdy-

Old old topic, but I'll continue posting here instead of starting a new thread.

I too fell into the MAME 115 Missile Command pitfall some time ago, but I'm also using MAME 133 for Missile Command & some other games.

When I set this up, I chose d3d instead of ddraw, because performance seemed to be better.  Oddly, when using d3d, the Tab menu is garbled, so I set things up in ddraw (set commands & dip switches & whatnot) & then switched the mame.ini file back to d3d after it was done.

Oddly, when I use MAME 133 to run Missile Command or Super Missile Attack with d3d, I just get a big blank white screen.  If I run those games with ddraw, they run great, but I think I might miss the mild performance gain on more intensive games.

Any ideas what's up here?

Thanks,
-Jason

[Tafoid]

I've had a garbled menu/font once.  I found that deleting the cached font UI.BDC then re-generating a new one helped me.  Some people needed to use a different UI.BDF or none at all for a run to 'clear' things.

Other than that - I'm not sure.  Sometimes driver changes can cause issues. 

[Gray_Area]

You can set display options per game.......

[jasonbar]

Tafoid, I've already tried messing w/ the ui fonts & didn't get anywhere.  No biggie--I don't need to go back into those games to change settings--that's just a side effect related to my current problem.

Gray_Area, thanks!!!  I forgot about that.  Duh!  So, I just made 2 little files: missile.ini & suprmatk.ini, which contained only the ddraw setting to override d3d, which is normally used.

Problem solved!


-Jason