Main > Main Forum

Issue with Windows 7 and native resolutions.

<< < (3/10) > >>

bitbytebit:
Yeah so far from what I've tried, nothing alters it, always comes out looking crappy compared to ddraw.  Has broken lines and messed up looking digits on pacman for example.  That is any of the current basic settings of that prescale option and the type of rendering being done changed from POINT to NONE for filtering, and also the stretch support option being turned off and using the alternative method instead of using the StretchRect methods.

I've got cleanstretch, rewritten actually so it works with changeres better, in groovymame already.  Ah it does fix it, well then why not just use cleanstretch and d3d with the ArcadeVGA 3000 :).  Oddly cleanstretch does some strange things sometimes I guess from reports, with games like gorf, but maybe with d3d it works well and that's the only place it should be used.  Probably using it on ddraw or in SDL, were not so great of places to use it, that makes more sense now.  I just had ported it into the Linux side and changed it to work with changeres and still allow scaling/stretching if desired.

krick:
So It looks like I have two options for Windows 7 + ArcadeVGA 3000:


1) run MAME in DDRAW mode and have the frontend switch the desktop resolution to 640x288 before launching MAME and switch it back after exiting.

2) run a MAME build with CleanStretch in D3D mode.


I'll have to get everything set up and see which looks the best and/or has the least issues.

bitbytebit:

--- Quote from: krick on April 10, 2011, 11:19:42 am ---So It looks like I have two options for Windows 7 + ArcadeVGA 3000:


1) run MAME in DDRAW mode and have the frontend switch the desktop resolution to 640x288 before launching MAME and switch it back after exiting.

2) run a MAME build with CleanStretch in D3D mode.


I'll have to get everything set up and see which looks the best and/or has the least issues.

--- End quote ---

I'm uploading a groovymame 012c which turns on cleanstretch now only when d3d is selected as the video type (usually off by default).  Seems like that makes the most sense, otherwise cleanstretch messes with ddraw and SDL stretching, but seems to always do the right thing in d3d.

Also I'm planning on having an option like -avga3000 to groovymame which will have that just basic heightXwidth@refresh list the .ini generators use to create all the little .ini files, but instead have groovymame do it all for you, check if we need throttle in some cases where the refresh rates don't match, do all the other stuff it does with registry modelines currently but instead it'll know that the fixed list of 30 or so resolutions are available to base the calculations of options upon.

ark_ader:
Isn't that Arcade VGA just a modified ATI 7000 card?

Is the Arcade VGA WDDM 1.1 compliant?

That might explain the resolution issues.

bitbytebit:

--- Quote from: ark_ader on April 10, 2011, 11:55:34 am ---Isn't that Arcade VGA just a modified ATI 7000 card?

Is the Arcade VGA WDDM 1.1 compliant?

That might explain the resolution issues.

--- End quote ---

No it's a ATI HD2600 (AVGA 3000 that is, earlier ones are from the 9200 series, maybe ones inbetween using that model, seems like one used the HD2400) card that was developed by both Andy and ATI together for the special modelines that it has built in and driver access methods of using those, like with the special AVGA Drivers and Arcade Perfect utility. 

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version