Re: d3dx9: Replace M_PI by its D3DX equivalent

Nozomi Kodama writes: > What is the problem with patch: > http://source.winehq.org/patches/data/97500 > > M_PI is never used in D3DX (moreover it is deprecated in C99) It's used all over the place, and we have portability macros for it. There's no reason to avoid it.

d3dx9: Replace M_PI by its D3DX equivalent

Hello What is the problem with patch http://source.winehq.org/patches/data/97500 M_PI is never used in D3DX. Nozomi

d3dx9: Replace M_PI by its D3DX equivalent

What is the problem with patch: http://source.winehq.org/patches/data/97500 M_PI is never used in D3DX (moreover it is deprecated in C99) Nozomi

Re: Google Summer of Code Project: Implement missing D3DX libraries

Am Donnerstag, 5. April 2012, 23:25:02 schrieb Alexander Mezin: > I want to contact possible mentor to discuss > what parts of the libraries must be implemented, but I can't find his > e-mail, wiki says that his page isn't created. You can find the current state of our d3dx li

Google Summer of Code Project: Implement missing D3DX libraries

Hello. I want to participate in GSoC and work on project "Direct3D: Implement missing D3DX libraries", listed at http://wiki.winehq.org/SummerOfCode. I have experience of developing for Windows using Direct3D 9 and D3DX, so I think I'm the one who you need for this project. About

Request for comments: d3dX : wined3d implicit enum conversion warnings and resolution

Hi guys, while trying to compile wine with clang, I get a whole bunch of "implicit conversion from enumeration type FOO to different enumeration type WINED3DFOO" (and conversely) warnings when an enum value of type A is assigned to a var of enum type B. In order to tackle those, instead of using

fyi d3dx work

I did end up going with a github repo as I've finally figured out git pretty well (thanks a lot to you guys!) It is here: http://github.com/misha680/wine/commits/master In any case, feel free to peruse if interested. Hopefully when 1.2 is done I can start submitting to wine. Henri especially has

Re: d3dx: need someone to test on Windows box

On Mon, May 31, 2010 at 5:33 AM, Henri Verbeet wrote: > On 31 May 2010 12:29, Andrew Nguyen wrote: >> I have taken the liberty of submitting your patch for you, and found >> no test failures: >> >> https://testbot.winehq.org/JobDetails.pl?Key=2397 >> > Yeah, but that's because it's skipping the t

Re: d3dx: need someone to test on Windows box

On 31 May 2010 12:29, Andrew Nguyen wrote: > I have taken the liberty of submitting your patch for you, and found > no test failures: > > https://testbot.winehq.org/JobDetails.pl?Key=2397 > Yeah, but that's because it's skipping the tests.

Re: d3dx: need someone to test on Windows box

On Sun, May 30, 2010 at 11:48 PM, David Adam wrote: > Hello, > > I tried these tests with my Vista box. All they passed. > Can anyone test on a real Windows XP box or a real Windows box? > > Thanks in advance > > David > You can submit tests to the WineTestBot service for execution in various Win

Re: d3dx: should NULL defines be accepted?

Luis Busquets wrote: > However I see nothing wrong in calling any of those functions with defines > being NULL. Actually, usually defines are NULL and it is only in specific > cases when they are set. > > Is this a bug? If not, please let me know why. Write a test case? -- Dmitry.

d3dx: should NULL defines be accepted?

The current code for the functions: D3DXCreateEffectFromFileExW D3DXCreateEffectFromFileExA D3DXCreateEffectFromResourceExW

Re: winetricks: update d3dx redist package.

2009/3/29 Rico Schüller : > Hi, > > this patch updates the DirectX redist package in winetricks to version > Mar09. Please rediff against http://winezeug.googlecode.com/svn/trunk/winetricks. A lot has changed since the last winetricks release (the one on kegel.com). -- -Austin

winetricks: update d3dx redist package.

Hi, this patch updates the DirectX redist package in winetricks to version Mar09. Cheers Rico update_d3d_redist_package.patch Description: application/mbox

Re: Effects in D3D10 and D3DX

2009/3/3 "Luis C. Busquets Pérez" : >  I have seen that Henri Verbeet has begun the implementation of > ID3D10Effect. Since there is a ID3DX9Effect interface I wonder of the > possibility of creating something like wined3deffect and refer > ID3DXEffect and ID3D10Effect to that wined3deffect impleme

Effects in D3D10 and D3DX

I have seen that Henri Verbeet has begun the implementation of ID3D10Effect. Since there is a ID3DX9Effect interface I wonder of the possibility of creating something like wined3deffect and refer ID3DXEffect and ID3D10Effect to that wined3deffect implementation.

RE: MaxVertexBlendMatrices, multi-matrix vertex blending and D3DX

> The only other option I'm aware of is to await the shader-based fixed > function pipeline replacement which might contain an implementation of > the D3DRS_VERTEXBLEND renderstates. I worked on a pipeline replacement using GL_ARB_vertex_program a few months ago but hit some roadblocks, so I never

MaxVertexBlendMatrices, multi-matrix vertex blending and D3DX

, they both show an odd behaviour where if the device caps report MaxVertexBlendMatrices <= 2 (or <2 maybe) then the d3dx apparently generates odd behaviour and unrecognised vertex entries, the upshot being that the character's vertices all end up on the ground at the model's worl

Re: Implementing textures functions of d3dx using an extern library.

On Thu, Aug 28, 2008 at 5:20 PM, Jérôme Gardou <[EMAIL PROTECTED]> wrote: > FreeImage : Quite easy to use, the only files not supported are DIB and > PFM... Not so widely represented. I had to recompile it, as packages for it > are not available for 32 bits. (I use a 64 bits ubuntu system). I thin

Implementing textures functions of d3dx using an extern library.

It appears this mail did not get in, so I resend it... -- Forwarded message -- From: Jérôme Gardou <[EMAIL PROTECTED]> Date: 2008/8/26 Subject: Implementing textures functions of d3dx using an extern library. To: wine-devel@winehq.org D3DX supports a wide range of file typ

Re: Implementing textures functions of d3dx using an extern library.

; +#ifdef HAVE_PNG_H +#include +#endif +#include "wine/debug.h" +#include "d3dx9_36_private.h" + +WINE_DEFAULT_DEBUG_CHANNEL(d3dx); + +/*This ones are needed by libpng and libjpeg to simulate file reading when dealing with memory +and errors*/ +static void intern_read_from_memory

Re: Implementing textures functions of d3dx using an extern library.

Henri Verbeet a écrit : > 2008/8/29 Jérôme Gardou <[EMAIL PROTECTED]>: > >> If you want, I have an implementation of this same function for png... This >> one is not commented at all, and need some rework. Get it for comparison. >> >> > As you said, it needs some cleanup etc, but at least i

Re: Implementing textures functions of d3dx using an extern library.

2008/8/29 Jérôme Gardou <[EMAIL PROTECTED]>: > > If you want, I have an implementation of this same function for png... This > one is not commented at all, and need some rework. Get it for comparison. > As you said, it needs some cleanup etc, but at least it doesn't look fundamentally broken to me.

Re: Implementing textures functions of d3dx using an extern library.

Jérôme Gardou a écrit : Henri Verbeet a écrit : 2008/8/28 Jérôme Gardou <[EMAIL PROTECTED]>: D3DX supports a wide range of file types for textures. Instead of rewriting everything from scratch, the best would certainly be to use some image processing library to handle them. As a bonus

Re: Implementing textures functions of d3dx using an extern library.

Henri Verbeet a écrit : > 2008/8/28 Jérôme Gardou <[EMAIL PROTECTED]>: > >> D3DX supports a wide range of file types for textures. Instead of rewriting >> everything from scratch, the best would certainly be to use some image >> processing library to handle them

Re: Implementing textures functions of d3dx using an extern library.

2008/8/28 Jérôme Gardou <[EMAIL PROTECTED]>: > D3DX supports a wide range of file types for textures. Instead of rewriting > everything from scratch, the best would certainly be to use some image > processing library to handle them. As a bonus, this would allow lighter > code.

Re: Implementing textures functions of d3dx using an extern library.

Juan Lang a écrit : >> Here is an implementation of D3DXGetImageInfoFromFileInMemory using >> FreeImage. >> > > Is the license compatible? FreeImage is dual-licensed with the GPL > (which Wine cannot use) and their own license. I'd be surprised if > their license were LGPL compatible. > --Ju

Re: Implementing textures functions of d3dx using an extern library.

> Here is an implementation of D3DXGetImageInfoFromFileInMemory using > FreeImage. Is the license compatible? FreeImage is dual-licensed with the GPL (which Wine cannot use) and their own license. I'd be surprised if their license were LGPL compatible. --Juan

Implementing textures functions of d3dx using an extern library.

D3DX supports a wide range of file types for textures. Instead of rewriting everything from scratch, the best would certainly be to use some image processing library to handle them. As a bonus, this would allow lighter code. Some of those library are : SDL_Image : easy to use, but loading an

Re: Several patches for D3DX

On Sat, Apr 12, 2008 at 11:11 AM, Luis Busquets <[EMAIL PROTECTED]> wrote: > Thanks for your sincere response. I am aware that there are diverse styles > of writing the functions and all can be criticised: some for its complexity, > others for its unreadability, others for its length... Anyway at t

Re: Several patches for D3DX

Thanks for your sincere response. I am aware that there are diverse styles of writing the functions and all can be criticised: some for its complexity, others for its unreadability, others for its length... Anyway at this point in time , what I see as evident is that the three implementations t

Re: Several patches for D3DX

On Fri, Apr 11, 2008 at 6:20 PM, Luis Busquets <[EMAIL PROTECTED]> wrote: > Is there still any problem with each of the attached patches or are they > going to be committed? > +WINAPI DWORD D3DXGetShaderVersion(CONST DWORD *pFunction) +{ +DWORD ver; +if (!pFunction) + { + return 0

Several patches for D3DX

Is there still any problem with each of the attached patches or are they going to be committed? diff --git a/dlls/d3dx9_36/d3dx9_36.spec b/dlls/d3dx9_36/d3dx9_36.spec index 93ba132..1619f16 100644 --- a/dlls/d3dx9_36/d3dx9_36.spec +++ b/dlls/d3dx9_36/d3dx9_36.spec @@ -163,7 +163,7 @@ @ stub D3DXG

Re: d3dx: A few last questions...

when microsoft released updates of their D3DX library without renaming the dlls, were using a more actual dll could really lead to conflicts. Unbegrenzter Speicher, Top-Spamschutz, 120 SMS und eigene E-MailDomain inkl. http://office.freenet.de/dienste/emailoffice/produktuebersicht/power/mail/index.html

RE: d3dx: A few last questions...

a time which even prevents us from caring about this function. By the way, I think this function is just a leftover from the times, when microsoft released updates of their D3DX library without renaming the dlls, were using a more actual dll could really lead to conflicts. Unbegrenzte

RE: d3dx: A few last questions...

The function D3DXCheckVersion must not be forwarded from each d3dx9_xx file to the 36 because D3DX_SDK_VERSION changes for each file.

d3dx: A few last questions...

Hi, So far I have pretty much completed the d3dx9_24 dll. However, while writing the spec files I faced a few problems which I'd like to have solved befor submitting the patch: 1. With the d3dx9_31 dll, microsoft removed three functions from the SDK. I'm curious what to do with them. Should I

d3dx implementation senseless?

> Well, why then hasn't this patch been accepted? > http://www.winehq.org/pipermail/wine-patches/2007-November/047212.html Oh well, I see, corrupted... Seems like I'll spend the day on fixing that one :D

d3dx implementation senseless?

Well, why then hasn't this patch been accepted? http://www.winehq.org/pipermail/wine-patches/2007-November/047212.html

Re: d3dx implementation senseless?

Am Montag, 7. Januar 2008 17:30:40 schrieb [EMAIL PROTECTED]: > Okay, I have a bit time now and tomorrow, so I'll probably have submitted a > basic d3dx9 dll patch until Wednesday. So I'll create a new d3dx9 directory > inside dlls, but I'm not that familiar with Wine's makefile system (not > very

Re: d3dx implementation senseless?

Okay, I have a bit time now and tomorrow, so I'll probably have submitted a basic d3dx9 dll patch until Wednesday. So I'll create a new d3dx9 directory inside dlls, but I'm not that familiar with Wine's makefile system (not very much with makefiles in general honestly), so can anyone tell me how

Re: d3dx implementation senseless?

Am Montag, 7. Januar 2008 07:29:48 schrieb Maarten Lankhorst: > [EMAIL PROTECTED] schreef: > >> Since everybody agrees that we need a built-in d3dx9, we could begin to > >> implement it. In the last talk about it, no plan was found to implement > >> it: does one create a wined3dx or implement on th

Re: d3dx implementation senseless?

[EMAIL PROTECTED] schreef: >> Since everybody agrees that we need a built-in d3dx9, we could begin to >> implement it. >> In the last talk about it, no plan was found to implement it: does one >> create a wined3dx or implement on the top of the last d3dx9 >> dll? >> >> So, I think that a definiti

Re: d3dx implementation senseless?

> Since everybody agrees that we need a built-in d3dx9, we could begin to > implement it. > In the last talk about it, no plan was found to implement it: does one create > a wined3dx or implement on the top of the last d3dx9 > dll? > > So, I think that a definitive answer should be given very qu

RE : Re: d3dx implementation senseless?

Since everybody agrees that we need a built-in d3dx9, we could begin to implement it. In the last talk about it, no plan was found to implement it: does one create a wined3dx or implement on the top of the last d3dx9 dll? So, I think that a definitive answer should be given very quickly. David

Re: d3dx implementation senseless?

i understand it correctly, it of course means that there are no > > really free downloads on their web-page, as they all rely on a purchase > > of Windows. This makes the "free" download kind of expensive. > > > > For Wine it means that anything the user has to D/L from their homepage > > is a no-no. > > Oh well, I didn't think about that, sorry. > Then it of course is a good thing if we implement our own d3dx. > > > > > > > > > > > >

Re: d3dx implementation senseless?

Am Freitag, 4. Januar 2008 17:00:46 schrieb [EMAIL PROTECTED]: > Oh well, I didn't think about that, sorry. > Then it of course is a good thing if we implement our own d3dx. The directx license as far as I understand it, allows installing and using the dx runtime, which d3dx* is a

Re: d3dx implementation senseless?

ink about that, sorry. Then it of course is a good thing if we implement our own d3dx.

Re: d3dx implementation senseless?

s they all rely on a purchase of Windows. This makes the "free" download kind of expensive. For Wine it means that anything the user has to D/L from their homepage is a no-no. /p On Fri, 2008-01-04 at 13:46 +0100, [EMAIL PROTECTED] wrote: > Hi, > I enjoyed the current wi

Re: d3dx implementation senseless?

On Fri, Jan 04, 2008 at 01:46:22PM +0100, [EMAIL PROTECTED] wrote: > Hi, > I enjoyed the current wine development of the D3DX libraries and also tried > to implement an interface. > However, while testing it I noticed that Wine seems to fully support > everything when it has a nat

d3dx implementation senseless?

Hi, I enjoyed the current wine development of the D3DX libraries and also tried to implement an interface. However, while testing it I noticed that Wine seems to fully support everything when it has a native d3dx9.dll (though it even was able to run one of my games without any dll...). So I was

Re: D3DX

development should be done. That is to develop just > one dlls/d3dx/d3dx.spec together with the different dlls/d3dx/xx.c files > implementing those functions with the 349 functions that are used in all > those d3d extensions. Then, the spec files of each specific file > referring to d3

D3DX

development should be done. That is to develop just one dlls/d3dx/d3dx.spec together with the different dlls/d3dx/xx.c files implementing those functions with the 349 functions that are used in all those d3d extensions. Then, the spec files of each specific file referring to d3dx. Are you opposed to such

D3DX

Dear all and in particular Alexander and Louis, I have seen that the work d3dx8 has began and that a number of functions have been added to the spec. I know this is a recurring subject but I think something should be done now. As you know, the fowllowing files d3dx8.dll d3dx9_24.dll d3dx9_24.d

Re: d3dx: VertexBuffer should keep reference to the parent device object.

> ChangeLog: > d3dx: VertexBuffer should keep reference to the parent device object. That's probably the best solution for the moment. >+/* Parent reference */ >+LPDIRECT3DDEVICE9 parentDevice; However, the name parentDevice is somewhat misleading, in particula