Definitely. XBMC had a particularly bad reaction to the Intel chipset. It would hardlock to the point that not only could you not End Task it, but it would prevent OS shutdown.
Obviously, forcing it to nVidia fixed it.
I revisited a benchmark out of curiosity. The natural resolution of this laptop's display is 1366x768. I used a SLIGHTLY modified version of JohnIV's settings as provided at http://www.mameworld.info/ubbthreads/sho...part=1&vc=1
Something odd happened when I benchmarked the HLSL-- on the first try, HLSL ran at a steady 50% on the Intel, but on a second try it was running significantly faster. A third try showed no change from the second one.
sf2ceua Street Fighter II': Champion Edition (USA 920313)
Without HLSL:
nVidia: 1165.62% Intel: 956.05%
With HLSL:
nVidia: 1270.11% Intel: 50.01% (first try) Intel: 1125.20% (second try)
I've doublechecked the settings in the nVidia control panel and it didn't change the hard-set setting I put into place for "intel.exe" at all.
Therefore, either there's something a bit odd with the benchmarks or even the Intel is capable of handling HLSL at the resolution of the laptop display!
It really looks like anything up to the top "killer" hardware sets are essentially "solved"-- any semi-modern rig should be able to handle it, and in most cases even HLSL with it.
Final final note:
I just used the Optimus testing tool provided at http://forums.laptopvideo2go.com/topic/2...950#entry130950 to determine if my settings were being overridden. They aren't. The Intel HD3000 onboard *IS* capable enough for 1366x768. I'm hesitant to try it at 1920x1080, but you never know, I might just end up hooking it up to my TV one of these days.
So there you have it. Intel HD3000 is good enough for MAME under at least SOME circumstances.
---
Try checking the MAME manual at http://docs.mamedev.org
Edited by Firehawke (05/10/12 12:46 AM)
|