|
Upgraded Mame from .147 to .157 -- not getting any video signal
#336449 - 01/28/15 09:43 AM
|
|
|
Hi guys,
I recently upgraded my Mame romset on my cab with the .157 release. To my dismay, I am not getting any video upon launching Mame -- it just sits on a black screen. If i press enter, I can get whatever game that is at the top of the list to load, but only the sound.
I tried my older version, .147 and it fired right up with no problems. I am using an older Dell, from 2009 or so, with onboard graphics instead of a graphics card; is this due to the newest version of Mame requiring much more video ram? It seems like a direct 3d problem, but if so, why is the older version working still?
Any help resolving this would be great!
Tyler
|
|
|
| redk9258 |
|
Regular
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 3968
|
|
Loc: Troy, Illinois USA
|
|
|
|
Send PM
|
|
|
Re: Upgraded Mame from .147 to .157 -- not getting any video signal
[Re: tylerwerrin]
#336452 - 01/28/15 01:08 PM
|
|
|
Try this:
mame pacman -verbose >output.txt
Post the contents of output.txt here.
|
|
|
|
Re: Upgraded Mame from .147 to .157 -- not getting any video signal
[Re: redk9258]
#336461 - 01/28/15 08:17 PM
|
|
|
Will do. I can also post my mame.ini file -- perhaps there is a setting which is not compatible with my computer?
|
|
|
|
Re: Upgraded Mame from .147 to .157 -- not getting any video signal
[Re: redk9258]
#336467 - 01/28/15 11:21 PM Attachment: output.txt 2 KB (0 downloads)
|
|
|
Hi,
here is the contents of my output file:
Video: Monitor 0000000000010001 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #0 = Intel(R) Q35 Express Chipset Family
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 1920x1200
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Mouse #2: HID-compliant mouse
Input: Adding Gun #2: HID-compliant mouse
Input: Adding Kbd #0: HID Keyboard Device
DirectInput: Using DirectInput 7
Input: Adding Joy #0: GP-Wiz40
Unable to load winpcap: 7e
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 ':proms' created
Region ':namco' created
It looks like my adapter doesnt support pixel shader 3.0, could this be the problem?
|
|
|
| redk9258 |
|
Regular
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 3968
|
|
Loc: Troy, Illinois USA
|
|
|
|
Send PM
|
|
|
Re: Upgraded Mame from .147 to .157 -- not getting any video signal
[Re: tylerwerrin]
#336476 - 01/29/15 03:47 AM
|
|
|
What OS do you have? Do you have DirectX installed? I think there is a version that gets installed in addition to the one that comes in Windows 7. I don't know about Windows 8.
Do you have HLSL enabled? If so, try disabling it.
|
|
|
|
Right in the beginning, and exactly what I thought....
[Re: tylerwerrin]
#336478 - 01/29/15 03:55 AM
|
|
|
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #0 = Intel(R) Q35 Express Chipset Family
Direct3D: Warning - Device does not support Pixel Shader 3.0, falling back to non-PS rendering
I've had the same issue with an embedded chipset. DD will display, but not D3D. You need a video card.
|
Scifi frauds. SF illuminates.
_________________
Culture General Contact Unit (Eccentric)
|
|
|
Re: Upgraded Mame from .147 to .157 -- not getting any video signal
[Re: tylerwerrin]
#336487 - 01/29/15 06:38 AM
|
|
|
> Will do. I can also post my mame.ini file -- perhaps there is a setting which is not
> compatible with my computer?
When you upgraded your MAME version, did you create a brand new mame.ini file? You can backup the old one for reference by changing the name to mame_ini.bak or something like that.
To create a new mame.ini, you run this command in your mame directory...
Code:
mame.exe -cc
...you should subsitute whatever your mame exe is named in the command above.
|
GroovyMAME support forum on BYOAC
|
|
| Sune |
|
Connected
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 5648
|
|
Loc: Lagoa Santa, Brasil
|
|
|
|
Send PM
|
|
|
|
> I am using an
> older Dell, from 2009 or so, with onboard graphics instead of a graphics card; is
> this due to the newest version of Mame requiring much more video ram?
No. Download and run this: http://www.microsoft.com/en-us/download/details.aspx?id=35 then try again.
If it still doesn't work, open mame.ini with notepad, scroll down to where it says
#
# DIRECT3D POST-PROCESSING OPTIONS
and set HLSL_enable to 0.
S
|
|
|
|
Wow. I get to totally eat poop there......
[Re: Sune]
#336827 - 02/10/15 03:03 AM
|
|
|
> No. Download and run this: http://www.microsoft.com/en-us/download/details.aspx?id=35
> then try again.
>
> If it still doesn't work, open mame.ini with notepad, scroll down to where it says
>
> #
> # DIRECT3D POST-PROCESSING OPTIONS
>
> and set HLSL_enable to 0.
>
> S
Turns out my ini had 1. I thought I checked it. I dunno. Anyways, goodness.
|
Scifi frauds. SF illuminates.
_________________
Culture General Contact Unit (Eccentric)
|
|
Previous 
Index 
Next 
Threaded 
Upgraded Mame from .147 to .157 -- not getting any video signal
Reply
[Re: 
