> For several years I've been using a legacy P4 2.4 GHz PC with a built-in Intel(R)
> 82845G/GL/GE/PE/GV Graphics Controller to compile and run MAME under WinXP. Somewhere
> between versions 0.148 and 0.149 I can no longer "run" the MAME executable without
> the graphics engine completely locking up the PC in full-screen mode. The video
> screen just shows garbage graphics after launching the application and the CPU
> immediately goes to 100% (I can still kill the process by switching over to
> taskmanager).
>
> Checking the other forums for similar issues, it was suggested that users update
> their DirectX 9.0c installation -- which I have done -- and everything appears fine
> there; no issues or missing/damaged files. There haven't been any updates to the PC's
> video driver or chipset in many, many years.
>
> Here's the verbose output I receive from MAME 0.149 (both mame0149b.exe and
> mame0149b_i686.exe downloaded from the official release site) when attempting to run
> Mr. Do!:
>
> Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
> Direct3D: Using Direct3D 9
> Direct3D: Configuring adapter #0 = Intel(R) 82845G/GL/GE/PE/GV Graphics Controller
> Direct3D: Warning - Device does not support Pixel Shader 3.0, falling back to non-PS
> rendering
> Direct3D: Using dynamic textures
> Direct3D: YUV format = UYVY
> Direct3D: Max texture size = 2048x2048
> Direct3D: Device created at 1280x1024
> DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
> RawInput: APIs detected
> Input: Adding Mouse #0: PS/2 Compatible Mouse
> Input: Adding Gun #0: PS/2 Compatible Mouse
> Input: Adding Kbd #0: Hewlett-Packard Extended Keyboard
> DirectInput: Using DirectInput 7
> Input: Changing default joystick map = s8.4s8.44s8.4445
> s8888888s
> 4s88888s6
> 44s888s66
> 444555666
> 444555666
> 444555666
> 44s222s66
> 4s22222s6
> s2222222s
> Input: Changing default joystick map = s8.4s8.44s8.4445
> s8888888s
> 4s88888s6
> 44s888s66
> 444555666
> 444555666
> 444555666
> 44s222s66
> 4s22222s6
> s2222222s
> Region ':maincpu' created
> Region ':gfx1' created
> Region ':gfx2' created
> Region ':gfx3' created
> Region 'roms' created
> Starting Mr. Do! ':'
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> (missing dependencies; rescheduling)
> Starting Z80 ':maincpu'
> Starting Video Screen ':screen'
> Starting Speaker ':mono'
> (missing dependencies; rescheduling)
> Starting U8106 ':u8106_1'
> Starting U8106 ':u8106_2'
> Starting Mr. Do! ':'
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> (missing dependencies; rescheduling)
> Starting Speaker ':mono'
> Starting Mr. Do! ':'
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> Optional shared pointer 'paletteram2' not found
> Optional shared pointer 'paletteram' not found
> Direct3D: resetting device
>
> Would anyone know if my issue could be a problem within MAME's "non-PS rendering"
> source or if there are some other parameters I need to use to force the newer
> releases to use legacy video driver settings?
>
> Thanks
Usually, issues with Direct3D are due to DirectX being too old, or your graphics. Added to that is the fact that DirectX 9.0 is only supported in software-rendering in your hardware.
You're likely going to have to switch to using GDI or upgrade your graphics somehow.
|
Index 
Flat 
Re: MAME 0.149 DirectX Video Issue
Reply
