... as I mentioned to Haze in another thread, Advancemame apparently already had the feature.
Advancemame doesn't work with many videocards under windows, and Advancemame only works with OLDER versions of Mame.
First off, the thing you're missing is that the starfield way back in Advancemame .106 appears to be correct. Did he re-write the driver? What did he do? Haze seems to be ignoring this.
Next, all the cards I've tried work just fine, both ATI and Nvidia over a range of models. I think it's not understanding how to initially configure Advancemame, which is well-documented but not well-presented, that gets people. My experience over time went from, 'How the hell does this work?!', to, "I can get
this work....", to, "I can pretty much get it to do anything".
Like the night before where I was having conflicts between games because having a pclock of 5-50 got me better results and a more usable device_video_format than 0-50. However, for a few games - for example, the Mr. Do series - I just made the following entry for:
(ie) dowild/device_video_clock 0-50 / 15.72-18 / 50-90
Whereas before this I was using the sdl mode 240x240, now I was getting a generated mode that worked right off. However, I might go back and see if maybe I was wrong on the 0-50 pclock not working as well. I dunno...it's weird, but I swear some things have changed over time, despite no hardware changes. (Wrong thing to say, heh.)
Another possible issue is there might be some conflicts between cards and mobos. An ATI card I have that ran flawlessly in a 1.5ghz P4 had some troubles with a different make P4 computer. However, all my nvidia's work fine in all the computers I've tried.