2012-02-10, 18:21
From the Wiki:
<allowd3d9ex>
Applies only to Windows Vista and up. Values: true/false.
Allows xbmc to use Direct3D 9Ex, which is a bit more stable and robust than Direct3D 9.
Default value: true.
<allowd3d9ex>true</allowd3d9ex>
and:
<forced3d9ex>
Windows only: XBMC attempts to detect drivers released for a version earlier than Vista,
to avoid using advanced features which are often not emulated correctly. The detection may be incorrect and this setting allows forcing the
using of D3D9Ex.
<forced3d9ex>false</forced3d9ex>
* Basically allow/force Direct3D9 Extensions. Your mileage may vary - as you can see from my earlier post I have turned off.
<useddsfanart>
This settings allows XBMC to use your GPU rendering fanart and some other images. This will make loading images considerably faster, especially on systems with slower processors (e.g. atom based systems).
To enable dds fanart in xbmc, add the following to your advancedsettings.xml:
<advancedsettings>
<useddsfanart>true</useddsfanart>
</advancedsettings>
* Use hardware (GPU) acceleration of fanart display.
People have had varying success with dirtyregions - devs tend to advise a comprimise of setting 3 for compatibility - experiment when you're bored. I use setting 1 for speed but get some flickering of text boxes if I linger over them. In all cases lowers CPU/GPU power consumption at idle, which is defined by the timeout <nofliptimeout>xxxmsec</nofliptimeout>.
Glad some noticed the speed difference - I use Transparancy most which can be a tad laggy - not with this build
Depending on what people report & what commits I see being useful I may do another build for Eden final, maybe not. From what I've seen the biggest beta 3 issue to date has to do with database upgrades. I'm more interested in AE myself, but this is something folks have been waiting patiently for and AE simply isn't ready yet for mainstream.
I do have some ideas on what's happening with TrueHD, but would rather apply the time to AE as it already supports 24bit, and there is a perfect workaround here passing it as LPCM. So unless other's get busy patching for TrueHD and 24bit output this may be as good as it gets for a while. That might change again if someone adapts the ALSA sink for Linux hint hint.
<allowd3d9ex>
Applies only to Windows Vista and up. Values: true/false.
Allows xbmc to use Direct3D 9Ex, which is a bit more stable and robust than Direct3D 9.
Default value: true.
<allowd3d9ex>true</allowd3d9ex>
and:
<forced3d9ex>
Windows only: XBMC attempts to detect drivers released for a version earlier than Vista,
to avoid using advanced features which are often not emulated correctly. The detection may be incorrect and this setting allows forcing the
using of D3D9Ex.
<forced3d9ex>false</forced3d9ex>
* Basically allow/force Direct3D9 Extensions. Your mileage may vary - as you can see from my earlier post I have turned off.
<useddsfanart>
This settings allows XBMC to use your GPU rendering fanart and some other images. This will make loading images considerably faster, especially on systems with slower processors (e.g. atom based systems).
To enable dds fanart in xbmc, add the following to your advancedsettings.xml:
<advancedsettings>
<useddsfanart>true</useddsfanart>
</advancedsettings>
* Use hardware (GPU) acceleration of fanart display.
People have had varying success with dirtyregions - devs tend to advise a comprimise of setting 3 for compatibility - experiment when you're bored. I use setting 1 for speed but get some flickering of text boxes if I linger over them. In all cases lowers CPU/GPU power consumption at idle, which is defined by the timeout <nofliptimeout>xxxmsec</nofliptimeout>.
Glad some noticed the speed difference - I use Transparancy most which can be a tad laggy - not with this build
Depending on what people report & what commits I see being useful I may do another build for Eden final, maybe not. From what I've seen the biggest beta 3 issue to date has to do with database upgrades. I'm more interested in AE myself, but this is something folks have been waiting patiently for and AE simply isn't ready yet for mainstream.
I do have some ideas on what's happening with TrueHD, but would rather apply the time to AE as it already supports 24bit, and there is a perfect workaround here passing it as LPCM. So unless other's get busy patching for TrueHD and 24bit output this may be as good as it gets for a while. That might change again if someone adapts the ALSA sink for Linux hint hint.