Software Support > GroovyMAME
Updated driver for AMD APU (Radeon HD 6410D)?
ahofle:
Still no luck. Booting into 640x480, the monitor won't sync (maybe it's trying progressive?). I also wasn't able to get an image on the CGA monitor using ArcadeOSD. Finally, attached the crash report from gmame. It seems to behave differently depending on my deskop res. It also seems to mess up the video driver as it thinks it's in some kind of safe mode now. Weird. I'm guessing this is a losing proposition.
caskad:
Hello,
i've just test with catalyst last driver, it works fine under Xp 32 bits !
--- Quote ---; VideoModeMaker - Options
; ------------------------
; 1. MAME
; -------
; Path for Mame executable, in case we want to extract xml information from it.
MameExe = "\Emuladores\Mame\mame.exe"
; Path for Mame ini folder, in case we want to create an ini file for each game.
; Important: existing ini files will be overwritten.
IniPath = "\Emuladores\Mame\ini\"
; Mame options.
ListFromXML = 0 ; Processes Mame XML and get video mode list from it
GenerateXML = 0 ; Extracts XML from Mame (only needed once)
GenerateInis = 0 ; Creates an ini file for each Mame game, in the IniPath folder
SDLMame = 0 ; Use SDLMame specific options
; Monitor orientation
MonitorHorizontal = 0 ; 0 = Rotating monitor: horizontal and vertical games at their native resolution
; Suitable for users that physically rotate their CRTs
; 1 = Horizontal monitor: horizontal games run at their native resolution and
; vertical games are rotated to fit in horizontal monitor
RotatingDesktop = 0 ; Specifies if both desktop and monitor are rotated
; Aspect ratio for vertical games on horizontal monitor
; 4:3 (keeps original aspect ratio)
; 3:3 (stretches to square format)
; 3:4 (stretches to full screen)
; h:v (custom aspect ratio)
VerticalAspect = "4:3"
; 2. MONITOR
; ----------
; Monitor Type. Valid types: D9800, D9400, D9200, EGA, VGA, MULTI, H9110, PAL, NTSC, GENERIC, CUSTOM
MonitorType = "H9110"
; Monitor CUSTOM. These values will be used if MonitorType = "CUSTOM"
;
; monitor_specs_0-6 = "HfreqMin-HfreqMax, VfreqMin,VfreqMax, HFrontPorch, HSyncPulse, HBackPorch, VfrontPorch, VSyncPulse, VBackPorch, HSyncPol, VSyncPol, ActiveLinesLimit, VirtualLinesLimit"
;
; * HfreqMin-HfreqMax: Minimum and maximum horizontal frequency, in Hz. Defines the range of horizontal frequencies the monitor is capable to sync.
; The higher the horizontal frequency, the higher the vertical resolution available for the same vertical refresh.
; The higher the horizontal frequency, the higher the vertical refresh available for the same vertical resolution.
; The higher the horizontal frequency, the lower the horizontal amplitude of active video (narrower picture).
;
; * VFreqMin-VfreqMax: Minimum and maximum vertical frequency, in Hz, Defines the range of vertical frequencies the monitor is capable to sync.
;
; * HFrontPorch, HSyncPulse, HBackPorch: Horizontal timing and geometry, values in µs
;
; * VfrontPorch, VSyncPulse, VBackPorch: Vertical timing and geometry, values in ms
;
; * HSyncPol,VSyncPol: polarities, not in use! defaults to negative.
;
; * ActiveLinesLimit: Vertical resolutions until ActiveLinesLimit value included, are generated as progressive, regardless the possibility
; of obtaining the required vertical refresh value.
;
; * VirtualLinesLimit: Vertical resolutions above ActiveLinesLimit and below VirtualLinesLimit are virtualized, that is, an interlaced resolution
; bigger that the native one is generated, with the right refresh, and "hardware stretch" is applied.
; Vertical resolutions above VirtulaLinesLimit are generated as interlaced, without any stretching.
monitor_specs_0 = "15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.160, 1.056, 0, 0, 288, 448"
; monitor_specs_0 = "29100-70000, 50-160, 1.000, 1.000, 3.000, 0.014, 0.044, 0.524, 0, 0, 1024, 800"
; Tolerance for horizontal frequency, in kHz, enables extending the range defined by [ HfreqMin, HfreqMax ]
; The resulting allowed frequency range will be [ HfreqMin - HfreqTolerance, HfreqMax + HfreqTolerance ]
HfreqTolerance = 0.010
; 3. MODELINE GENERATOR
; ---------------------
; Total number of modelines to generate. Here are the recommended values for each driver version:
; CRT_Emudriver, based on Catalyst 6.5: 160 modes (accepts up to 200, but above 160 HyperSpin will refuse to load)
; CRT_Emudriver, based on Catalyst 9.3: 120 modes (accepts some more but above 120 you can get some blue screens)
; Regular Catalyst : 60 modes (won't accept any more)
TotalModes = 120
; If enabled, only creates modes with 32 bits per pixel color depth
Only32BPPModes = 0
; Method for mode table generation. If Mame xml is processed, that will create a lot of different video modes, so the mode table
; will be optimized keeping the most relevant ones, and dropping the rest, to keep below the TotalModes value.
ModeTableMethod = 1 ; 0 = Static table: modelines are generated keeping their original vertical refresh. This
; method is intended to be used in combination with ini files for each game.
; 1 = Dynamic table: a table of dummy modes is created using xres and yres values while ignoring
; vfreq. This method is intended to be used in combination with Switchres or Groovymame. No ini
; files are required using this method (you should disable the GenerateInis option).
; Minimum resolution values (these will be used instead of lower values)
XresMin = 184
YresMin = 192
; XresMin = 512
; YresMin = 400
; Minimum dotclock value allowed by the video card, in MHz (i.e. DotClockMin = 7.010)
DotClockMin = 0
; Number of iterations used by the mode generator [0,5]. The higher the number of iterations, the bigger the accuracy of the vertical
; refreshed obtained, normally at the cost of increasing the horizontal frequency strictly required.
Iterations = 0
; Specifies if the refresh label is multiplied by 10 before rounding (experimental).
VFreqLabelx10 = 0
; 4. DRIVER
; ---------
; Path for the driver folder
DriverPath = ".\Driver\"
; If UpdateRegistry is enabled, UpdateDriver will only work if the driver version found in DriverPath matches the one installed
; in the system.
UpdateRegistry = 1 ; Specifies if the video card registry section will be updated with the new video modes
; (will only work in combination with CRT_EMUDriver).
UpdateDriver = 0 ; Specifies if the driver files in DriverPath will be updated with the new video modes, for
; future installations.
AnyCatalyst = 1 ; Allows modelines to be installed for any Catalyst version. This option is experimental and
; known to produce some problems.
--- End quote ---
test mario with 1234*240 works fine but grey line on arcad_osd ... with any resolution, so, test failed? (looks Ok !)
Calamity:
--- Quote from: ahofle on January 11, 2012, 09:21:53 pm ---Still no luck. Booting into 640x480, the monitor won't sync (maybe it's trying progressive?). I also wasn't able to get an image on the CGA monitor using ArcadeOSD. Finally, attached the crash report from gmame. It seems to behave differently depending on my deskop res. It also seems to mess up the video driver as it thinks it's in some kind of safe mode now. Weird. I'm guessing this is a losing proposition.
--- End quote ---
Yes, it seems that's the issue with ATI generations from HD 5000, they will go into a safe mode if they don't recognize an EDID attached.
The modelines reported by the system are still wrong, I guess that's because of the safe mode too.
So how did you manage to test with Arcade_OSD if you couldn't get the monitor to sync? Did you plug the LCD in the middle?
The crash in GM happens because d3d can't use a resolution that's "hidden" by the system. Using -video ddraw instead *should* prevent that crash (although it's not a fix for this anyway).
Our last hope is that by using this registry hack we could prevent the drivers to perform screen detection and thus to enter in safe mode:
http://forum.arcadecontrols.com/index.php?topic=116790.0
Calamity:
--- Quote ---test mario with 1234*240 works fine but grey line on arcad_osd ... with any resolution, so, test failed? (looks Ok !)
--- End quote ---
What card are you using for your test? Monitor?
Please get me a log of mario so I can see how your system is set up.
caskad:
Ho well, sorry for spec:
Athlon 5000+
Winxp 32 bits
hd4870
I will make you the log. But seems to be fine (unless widescreen problem with 1234Xxxxx resolution and calibrate my gun suck;))
and i 've made a test previsously who's failed with the same Ati driver (11.2 i guess)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version