"fract" vs "integ" scalling (gorf)

[billfor]

I'm running windows XPx64 with crtemu 1.2b.

I noticed that gorf seems to play differently on versions of groovymame, with the exact same options.   After version 147 it doesn't seem to find the correct resolution and if I force (newer versions) to the resolution that 147 chooses  then it will play except for some blurriness in the graphics.

For the chosen resolution in 147 log I get:

SwitchRes: [ 512]x[ 384]_(60=59.9930Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  512 x 384_60.054p 25.643 [integ] scale(1, 1, 1) diff(0.27, 8.43, 0.0000) ratio(2.133, 1.091)
   rng(3):  512 x 384_60.054p 29.006 [integ] scale(1, 1, 1) diff(0.27, 6.63, 0.0000) ratio(2.133, 1.091)
   rng(4):  out of range
   rng(5):  out of range

Now anything past 147, such as 164 or v171 will show this in the log:

SwitchRes: [ 512]x[ 384]_(60=59.9930Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  512 x 384_60.054p 25.643 [fract] scale(1, 1, 1) diff(16.67, 8.43, 0.0000) ratio(2.133, 1.091)
   rng(3):  512 x 384_60.054p 29.006 [fract] scale(1, 1, 1) diff(16.67, 6.63, 0.0000) ratio(2.133, 1.091)
   rng(4):  out of range
   rng(5):  out of range

So "fract" instead of "integ".

Does anyone know why this is? Also if I don't force the resolution to be 512x384 on the new versions of gmame then it default to the desktop resolution and plays at 150% speed. 

Thanks!

--- Bill

[billfor]

I fixed my problem but don't understand it completely. I found the modeline that 147 had picked, and then on version shigher than 147 I use that modeline directly but also had to change d3d to ddraw and set hwstretch to 0 in order for it to appear sharp.