Software Support > GroovyMAME

Setting up for Win7, LCD, and Nvidia Card??

<< < (12/17) > >>

lettuce:
Cheers Calamity!

Any development on the problem with HLSL not working?

Calamity:
Hi lettuce, have a look at these threads:

http://forum.arcadecontrols.com/index.php?topic=113006.0

http://www.mameworld.info/ubbthreads/showflat.php?Cat=&Number=264168&page=0&view=expanded&sb=5&o=&vc=1

I don't think it's the same issue but might point to some direction.

Do you remember, by any chance, which subversion of MameUI did you test (u1, u2, u5, etc.)? GroovyMAME is based on plain v0.143 with no update patch applied, so it should be tested against a regular plain v0.143 MAME. If this bug is MAME itself related, hopefully it we'll be fixed when we update the patches for v.0144.

lettuce:
I will try your latest build on my laptop which has an ATI card to see if i get the same problem on an ATI based system. This is the info i got back from the moninfo program:

Monitor
  Manufacturer............. Samsung
  Plug and Play ID......... SEC5541
  Data string.............. 156AT05-T02
  Serial number............ n/a
  Manufacture date......... 2009, ISO week 0
  Filter driver............ None
  -------------------------
  EDID revision............ 1.3
  Input signal type........ Digital
  Color bit depth.......... Undefined
  Display type............. RGB color
  Screen size.............. 340 x 190 mm (15.3 in)
  Power management......... Not supported
  Extension blocs.......... None
  -------------------------
  DDC/CI................... Not supported

Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2.20
  Red chromaticity......... Rx 0.620 - Ry 0.355
  Green chromaticity....... Gx 0.300 - Gy 0.580
  Blue chromaticity........ Bx 0.150 - By 0.090
  White point (default).... Wx 0.313 - Wy 0.329
  Additional descriptors... None

Timing characteristics
  Range limits............. Not available
  GTF standard............. Not supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 1366x768p at 60Hz (16:9)
    Modeline............... "1366x768" 72.330 1366 1414 1446 1526 768 770 775 790 -hsync -vsync

Standard timings supported

Report information
  Date generated........... 28/09/2011
  Software revision........ 2.60.0.964
  Data source.............. Real-time 0x0100
  Operating system......... 6.1.7600.2

Raw data
  00,FF,FF,FF,FF,FF,FF,00,4C,A3,41,55,00,00,00,00,00,13,01,03,80,22,13,78,0A,CE,85,9E,5B,4C,94,26,
  17,50,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,41,1C,56,A0,50,00,16,30,30,20,
  25,00,58,C1,10,00,00,19,00,00,00,0F,00,00,00,00,00,00,00,00,00,1E,--BINGO! Either that, or I was attempting to say "before" but it was too many letters to type--,02,74,00,00,00,00,FE,00,53,
  41,4D,53,55,4E,47,0A,20,20,20,20,20,00,00,00,FE,00,31,35,36,41,54,30,35,2D,54,30,32,0A,20,00,B8

What modeline do i need to add in the mame.ini file, what other options do i need to enable in the mame.ini for a laptop running win 7 with an ATI card?

Calamity:
That monitor doesn't have frequency ranges information available, so let's try with these values:

monitor_specs0            31000.00-50000.00,50.00-70.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,768,768

As usual, use these options: -ps -monitor lcd -video d3d

Good luck!

lettuce:
Cheers for that. I have tried it on my laptop now and still get the same problem with HLSL. I have uploaded a video of final fight (using FRAPS) to show the problem...



Any ideas??? Its as if the screen has just zoomed into 1 pixel of the screen as when i start to mojavascript:void(0);ve the character the screen changes colour or in this case pixel!

I have also downloaded standard mame 0.143, from mamedev.org/downloader.php?file=releases/mame0143b.exe if i enable HLSL then it works with standard mame, so must be a problem with grooyMAME??

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version