| Re: [AD] d3d cache blender state optimisation |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
It was optimized, because was bottleneck. Each draw call setup D3D9
state. In very most cases those calls were redundant. Calls to D3D9
should be minimized, when possible.
Primitive add-on could use blender instead of direct D3D9 calls. Now
this is not expensive operation. It is possible?
On 12 January 2011 09:23, Peter Wang <novalazy@xxxxxxxxxx> wrote:
> Regarding the bug reported here:
> http://www.allegro.cc/forums/thread/605937/898164#target
>
> The problem is that the primitives addon calls
> IDirect3DDevice9_SetRenderState(device, D3DRS_BLENDOP, d3d_op);
> without invalidating the cached value in the ALLEGRO_DISPLAY_D3D.
> Similarly for other parameters.
>
> Is the optimisation actually worthwhile? If we fix the primitives
> addon, might user code want to do a similar thing?
>
> Peter
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>
--
thedmd, Michał Cichoń
Artifex Mundi
michcic@xxxxxxxxxx
http://www.artifexmundi.com