[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: Re: [PATCH 05/10] wined3d: Add compute shaders cb/samplers state updates.
From:       Józef Kucia <joseph.kucia () gmail ! com>
Date:       2017-01-30 17:59:40
Message-ID: CAKF0LCUFhg+mvCkoZ5-p9AaiyL4p_po2eE+3KCzaFfi3zeoA+w () mail ! gmail ! com
[Download RAW message or body]

On Mon, Jan 30, 2017 at 5:26 PM, Guillaume Charifi
<guillaume.charifi@sfr.fr> wrote:
> Thank you for your feedback.
> WineD3D/D3D11/OpenGL are complex APIs with lots of tricky details.
> I know my implementation is far from perfect, but it seems that you learn
> better by working, trying, so I do.
> I have a basic but (likely) working tessellation implementation and I'll
> submit it soon. But it's quite dirty, so I expect feedbacks to improve it
> (if you haven't done it locally yet).

Sure, a tessellation shaders implementation would be welcome. I
haven't done much work on tessellation shaders, just some hacks to run
a very basic tessellation shaders. I think that it might be a good
idea to implement stream output/transform feedback first. Stream
output should make writing tests for tessellation shaders so much
easier. Basic support for stream output should also be easier to
implement than tessellation shaders.

>
> Btw, I think you should write down somewhere who is currently working on
> what at Crossover, to avoid useless duplicated work.

This could be improved, but the truth is that we do not have much
contributions to wined3d besides the work of core wined3d team. You
can always write to wine-devel that you are interested in implementing
a particular feature.



[prev in list] [next in list] [prev in thread] [next in thread]