| DMala |
|
Sleep is overrated
|
|
|
|
|
Reged: 05/09/05
|
|
Posts: 3989
|
|
Loc: Waltham, MA
|
|
|
|
Send PM
|
|
|
Crash using switchres?
#260123 - 07/17/11 05:59 AM
|
|
|
So I'm a little late to the .143 party, I'm just getting it set up now. With "switchres 1" in my INI file, MAME crashes instantly on two very different machines. (Core2Duo E8400/GeForce GTX 260/2GB RAM/Win7 x64 and Athlon64 X2 3800+/GeForce 6200/2GB RAM/Win7 x64) This happens with HLSL and all of the new options off. Is anyone else seeing this?
Even with switchres off, I'm also having zero luck with HLSL. When I turn it on on the Intel box, I get the usual warning screens, then a black screen with a white border and nothing happens. I do have the latest NVIDIA drivers on this system, maybe it's related to this? I haven't had a chance to roll them back yet.
On the Athlon, I turn it on and games run, but nothing is different. I see no difference in the image, and I don't even see any of the slider controls. I wasn't expecting miracles with my crappy GeForce 6200, but I thought *something* would happen. The card seems to meet the bare minimum requirements, as far as Directx and Pixel Shader 3.0 go. I'm also using an older driver on this system (191.07). Am I missing something here?
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3137
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: Crash using switchres?
[Re: DMala]
#260134 - 07/17/11 02:36 PM
|
|
|
> So I'm a little late to the .143 party, I'm just getting it set up now. With
> "switchres 1" in my INI file, MAME crashes instantly on two very different machines.
> (Core2Duo E8400/GeForce GTX 260/2GB RAM/Win7 x64 and Athlon64 X2 3800+/GeForce
> 6200/2GB RAM/Win7 x64) This happens with HLSL and all of the new options off. Is
> anyone else seeing this?
>
>
> Even with switchres off, I'm also having zero luck with HLSL. When I turn it on on
> the Intel box, I get the usual warning screens, then a black screen with a white
> border and nothing happens. I do have the latest NVIDIA drivers on this system, maybe
> it's related to this? I haven't had a chance to roll them back yet.
>
> On the Athlon, I turn it on and games run, but nothing is different. I see no
> difference in the image, and I don't even see any of the slider controls. I wasn't
> expecting miracles with my crappy GeForce 6200, but I thought *something* would
> happen. The card seems to meet the bare minimum requirements, as far as Directx and
> Pixel Shader 3.0 go. I'm also using an older driver on this system (191.07). Am I
> missing something here?
Read through the MINI-FAQ that is provided at the top of this forum. Run -verbose on command line to see what is happening and address any issues that show up.
HLSL will not activate unless you have everything MAME needs for it. HLSL and -switchres both work fine here (my machine is much like your second setup, except a 4400 and running on XP.. with on-board Geforce 6100 and it works fine here, albeit slowly.
|
|
|
| DMala |
|
Sleep is overrated
|
|
|
|
|
|
Reged: 05/09/05
|
|
Posts: 3989
|
|
Loc: Waltham, MA
|
|
|
|
Send PM
|
|
|
Re: Crash using switchres?
[Re: Tafoid]
#260191 - 07/18/11 06:40 AM
|
|
|
> Read through the MINI-FAQ that is provided at the top of this forum. Run -verbose on
> command line to see what is happening and address any issues that show up.
> HLSL will not activate unless you have everything MAME needs for it. HLSL and
> -switchres both work fine here (my machine is much like your second setup, except a
> 4400 and running on XP.. with on-board Geforce 6100 and it works fine here, albeit
> slowly.
HLSL problem is solved, I was missing the DirectX End User Runtime SDK. Thanks!
-switchres still blows up for me, though. If I leave the resolution set to "auto" and launch, say, Pacman, it picks 640x480@70hz, and that seems to work more often than not. If I force a specific resolution (800x600@85 in this case), it crashes every time.
Verbose output from a crash doesn't seem to show much:
Parsing mame.ini
Parsing mame.ini
Parsing vertical.ini
Video: Monitor 0000000000010001 = "\\.\DISPLAY1" (primary)
Video: Monitor 0000000000010003 = "\\.\DISPLAY2"
Direct3D: Using Direct3D 9
Direct3D: Configuring adapter #1 = NVIDIA GeForce 6200
Direct3D: Selecting video mode...
1024x 768@ 60Hz -> 63.044792
1024x 768@ 70Hz -> 96.990555
1024x 768@ 72Hz -> 81.465240
1024x 768@ 75Hz -> 65.741272
1024x 768@ 85Hz -> 2000.780640
640x 480@ 60Hz -> 63.906185
640x 480@ 70Hz -> 97.851944
640x 480@ 72Hz -> 82.326630
640x 480@ 75Hz -> 66.602661
640x 480@ 85Hz -> 2001.641968
720x 480@ 60Hz -> 63.715534
800x 600@ 60Hz -> 2062.264160
800x 600@ 70Hz -> 2096.209961
800x 600@ 72Hz -> 2080.684570
800x 600@ 75Hz -> 2064.960693
800x 600@ 85Hz -> 4000.000000
800x 600@ 56Hz -> 2017.837769
1152x 864@ 60Hz -> 62.928600
1152x 864@ 70Hz -> 96.874367
1152x 864@ 72Hz -> 81.349045
1152x 864@ 75Hz -> 65.625076
1280x 720@ 60Hz -> 62.935749
1280x 768@ 60Hz -> 62.914768
1280x 800@ 60Hz -> 62.901497
1280x 960@ 60Hz -> 62.842518
1280x1024@ 60Hz -> 62.821880
Direct3D: Mode selected = 800x 600@ 85Hz
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Device created at 800x600
Direct3D: Max texture size = 4096x4096
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #0: Logitech USB Wheel Mouse
Input: Adding Gun #0: Logitech USB Wheel Mouse
Input: Adding Kbd #0: Standard PS/2 Keyboard
DirectInput: Using DirectInput 7
Input: Adding Joy #0: XBOX 360 For Windows (Controller)
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
Starting Driver Device 'root'
Direct3D: Error 88760868 during device present call
(missing dependencies; rescheduling)
Starting Z80 'maincpu'
Starting Video Screen 'screen'
Starting Speaker 'mono'
(missing dependencies; rescheduling)
Starting Namco 'namco'
Starting Driver Device 'root'
(missing dependencies; rescheduling)
Starting Speaker 'mono'
Starting Driver Device 'root'
Direct3D: resetting device
|
|
|
|
Previous 
Index 
Next 
Threaded 
Crash using switchres?
Reply
[Re: 