Main > Monitor/Video Forum
Powerstrip writeup
Silver:
If you disable hws in mame to get great results with an Avga, how can it suddenly be slow with no hws with another card? Maybe there is some other setting?
Not sure what -flt option is - does not seem to exist for me, unless its abbreviated. Could be the -d3dfilter...?
relevant settings from mame.ini:
ddraw 0
direct3d 1
hwstretch 0
cleanstretch none
effect none
screen_aspect 4:3
### Windows Direct3D 2D video options ###
zoom 1 (this defaults to 2, try 1.. should be 1:1 zooming?)
d3dtexmanage 1
d3dfilter 0 (this is filtering which will have a blur effect - try 0)
d3dfeedback 0
d3dscan 100
d3dprescale none (try 'none' to disable - this is for scaling up)
d3deffect none
# d3dcustom <NULL> (not set)
# d3dexpert <NULL> (not set)
EDIT: d3dfilter 1 (default) has a massive effect. It's bilinear filtering, and smooths the entire screen. Great for running lo-res games at something higher, but based on what we are trying to do here, this should be 0 to make everything nice and blocky....right?
As for cards - I'm interested in the radeon 9xxx series as they are completely unviable with Advancemame and windows.
dabone:
--- Quote ---If you disable hws in mame to get great results with an Avga, how can it suddenly be slow with no hws with another card? Maybe there is some other setting?
--- End quote ---
I was trying to use clean stretch with hws disabled.
The avga is fast because there is no stretching going on, hardware or otherwise.
I've been playing on my desktop machine with the d3d and flt options.
These setting seem to get rid of the aa in the filter.
--- Quote ---### Windows video options ###
autoframeskip 1
frameskip 0
waitvsync 0
triplebuffer 0
window 0
ddraw 0
direct3d 1
hwstretch 1
# screen <NULL> (not set)
cleanstretch auto
resolution auto
refresh 0
scanlines 0
switchres 1
switchbpp 1
maximize 1
keepaspect 1
matchrefresh 0
syncrefresh 0
throttle 1
full_screen_brightness 0.000000
frames_to_run 0
effect none
screen_aspect 4:3
### Windows Direct3D 2D video options ###
zoom 2
d3dtexmanage 1
d3dfilter 0
d3dfeedback 0
d3dscan 100
d3deffectrotate 1
d3dprescale auto
d3deffect none
# d3dcustom <NULL> (not set)
# d3dexpert <NULL> (not set)
--- End quote ---
Tomorrow, I'll try it on the 9200.
(In the office I just use a 640x240 resolution to test)
Later,
dabone
Silver:
Let us know how it goes. Seeing as you have a 9200 I'd be interested to hear the results of both 320x240 and 640x240 compared.....(see if there is a noticeable difference or not).
Might be worth playing with the d3dzoom number as well (try 1 instead of 2) although this may have no effect if you are specifiying a resolution.
I don't believe cleanstretch has any effect with hardwarestretch off (clean stretch just restricts the stretching to positive integers)
desmatic:
--- Quote from: wpcmame on October 01, 2005, 02:42:52 pm ---
--- Quote from: desmatic on October 01, 2005, 05:04:22 am ---hey wpcmame, what the heck does the 7 stand for at the end of each modeline entry.
--- End quote ---
This is what it says in the powerstrip FAQ
*Timing string parameter definition:
1 = horizontal active pixels
2 = horizontal front porch
3 = horizontal sync width
4 = horizontal back porch
5 = vertical active pixels
6 = vertical front porch
7 = vertical sync width
8 = vertical back porch
9 = pixel clock in hertz
10 = timing flags, where bit:
1 = negative horizontal porlarity
2 = negative vertical polarity
3 = interlaced
5 = composite sync
7 = sync-on-green
all other bits reserved
(Note that flag bit 0 is reserved and that pixel clock is expressed in Khz not hertz)
--- End quote ---
Ok, I've done some more reading. I read the faq entry that you're referring to, searched the forums, and googled for more info, but I still haven't been able to figure out how to calculate the last column. From my research I'm guessing it's a 12 bit number with a few bits that are configurable, however, without knowing what the first bit should be, I really can't do anything. In some configuration files i've found on the net, it's turn on (like in yours) but in most it's turned off. I also can't find any info on doublescan modes.
So the big question is, and I'm not expecting any one to know the answer to this: should I set the first bit to, 1 or 0? Based on your config file I was going to set it to 1. Any ideas?
I've finished writing the next version of lrmc and was hoping to post the binaries today, but I just wanted to post first in case anyone knew anything.
wpcmame:
[quote author=desmatic link=topic=43728.msg414512#msg414512 Ok, I've done some more reading.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version