Le 01/04/2012 01:49, Henri Verbeet a écrit :
My first guess would be to check if vertex buffers are perhaps
supposed to take a reference to the D3D interface.
Ok. I will write a test to check that.
On 2012-04-01, at 6:06 PM, Henri Verbeet wrote:
> Ideally applications wouldn't care at all about this and use the caps
> instead, though in practice applications might use the PCI IDs for
> workarounds for driver bugs or for capability detection.
Sounds good, so then are you okay with the patch
On Sat, Mar 31, 2012 at 12:42, Christian Costa wrote:
> Hi,
>
> I wrote a win16 exe test file using open watcom but I cannot submit it to
> winebot. I fails saying "Unricognized file type". This is a little annoying.
> Is this a known limitation of wine test bot ?
>
> Thanks
> Christian
http://wi
On 1 April 2012 19:08, Gaurav Jain wrote:
> However isn't it important for wine to still distinguish between models (if
> possible) if they have different minimum memory sizes across models? Are
> there any other significant differences across models that wine need to be
> aware of?
>
In genera
On Sun, Apr 1, 2012 at 10:43 PM, David Adam wrote:
> +*mesh = polygon;
> +
> +if (adjacency)
> +{
> +hr = D3DXCreateBuffer(3 * sides * sizeof(DWORD), &adjacency_tmp);
> +if (FAILED(hr)) return hr;
You should release the polygon mesh. Also, you probably shouldn't
touch
Hi Jacek,
First I'd like to put a disclaimer, that I'm extremely new to this, so please
forgive me if I don't understand most of the behaviours and dependancies. That
being said, I will try my very best to dig as much as I can to find out more.
On 2012-04-01, at 7:08 AM, Jacek Caban wrote:
> t
On 2012-04-01, at 6:57 AM, Henri Verbeet wrote:
> Does the Windows driver really distinguish
> between these?
I'm not sure if it does, if the matching is only on the vendor and device ID,
then it's unlikely.
However isn't it important for wine to still distinguish between models (if
possible)
Hi Gaurav,
On 3/31/12 9:22 PM, Gaurav Jain wrote:
shell32: Added stubs for IMarshal interface (resend)
Resending due to previous code freeze.
ShellLink_QueryInterface() did not have a lookup for the IMarshal Interface.
This resulted in an error message popping up in the Quest for Glory II (re
On 1 April 2012 01:55, Gaurav Jain wrote:
> Ahh... I didn't catch that the 6600M & 6750M was identical. Is there even a
> 6600M? My google search only found a 6630M, 6650M & 6670M. I believe 6600M is
> the series. I can remove the 6750M from the patch if you'd like. Please note
> that there is
Kusanagi Kouichi writes:
> On 2012-03-30 15:36:06 +0200, Alexandre Julliard wrote:
>> I don't think that's a good idea. There are many things in the structure
>> that don't make sense to have in the registry.
>
> Font cache lacks some information. Of course we can fix that, but that
> might occur
Am 01.04.2012 04:33, schrieb David Adam:
+ * Order is not limited by D3DXSH_MINORDER and D3DXSH_MAXORDER!
+ * All values will work, test from 0-7 [D3DXSH_MINORDER = 2,
D3DXSH_MAXORDER = 6]
+ * Exceptions will show up when out, in1 or in2 are NULL
+ */
+for (k = 0; k < 8; k++
11 matches
Mail list logo
