Dear all,
Since d3d10effect has advanced a lot during the latest weeks I was
wondering what are the next steps that you are planning to develop.
In particutar, I wonder about:
1. Do DepthStencil and RasterizerState present major differences in
terms of capabilities compared to D3D9? I mean th
I read several months ago that the itnetion was to create the assembler
inside the wined3d and then use its functionality inside the diverse
d3dx9 implementations. Has this changed? I think it was Stefan Dösinger
sho proposed it:
d3dx -> wined3d assembler
the wined3d will be re-usable and the
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.
derFromFileW,
D3DXCompileShaderFromFileExA) in d3dx9_32 for testing and now setting the code
on d3dx9_36 obviously. The tests have been ok.
Please let me know your comments and if you think that it can be submitted to
wine-patches.
Am Donnerstag, 13. März 2008 18:26:17 schrieb Luis C. Busquets Pérez:
Propo
Proposing another thing if implementing d3dx9_36.dll is too much I
propose to implement:
1 D3DXAssembleShader
2 D3DXAssembleShaderFromFileA
3 D3DXCompileShader
4 D3DXCompileShaderFromFileA
5 D3DXCreateCubeTextureFromFileExA
6 D3DXCreateCubeTextureFromFileI
Is ther eany problem with this patch?
---
dlls/d3dx8/d3dx8_main.c | 59
+-
1 files changed, 57 insertions(+), 2 deletions(-)
diff --git a/dlls/d3dx8/d3dx8_main.c b/dlls/d3dx8/d3dx8_main.c
index ee897a8..a1d37b8 100644
--- a/dlls/d3dx8/d3dx8_main.c
Please find attached some projects that could be in this Summer of Code:
1. Finishing the implementation of d3dx9_36. Since we have already the
forwarding d3dx9_xx there is just need for the this dll to be in our
system. With this fully dll implemented tehre would be no need.
2. msxml.dll, msxml
The number of functions reported in
http://www.winehq.org/site/winapi_stats
for the following dlls is
d3dx9_24308
d3dx9_25311
d3dx9_26315
d3dx9_27315
d3dx9_28320
d3dx9_29320
d3dx9_30320
d3dx9_31317
d3dx9_32322
d3dx9_33
There is a bug in the patch:
c19af910ebafa9b1928b0f67bee68f6b0b237e8e is first bad commit
commit c19af910ebafa9b1928b0f67bee68f6b0b237e8e
Author: Alexandre Julliard <[EMAIL PROTECTED]>
Date: Thu Jan 17 19:53:59 2008 +0100
winex11.drv: Don't create a win_data structure for the desktop
w
Why has this patch not been accepted?
Luis C. Busquets Pérez escribió:
> I have created a /dlls/d3dx8/texture.c file where to put all functions
> related to textures and d3dx8.
>
> I have included D3DXIMAGE_FILEFORMAT in the patch because it is
> referred by D3DXIMAGE_FILE
I have submitted a patch for this function and it is easily convertable
to the 13 different functions.
Anyway, propose another patch for it and let it be implemented.
[EMAIL PROTECTED] escribió:
The function D3DXCheckVersion must not be forwarded from each d3dx9_xx file to the 36 because D3DX_
The function D3DXCheckVersion must not be forwarded from each d3dx9_xx
file to the 36 because D3DX_SDK_VERSION changes for each file.
d3dx8tex.h with the mentioned name.
I should be done now. Please send comments if not.
---
dlls/d3dx8/Makefile.in |1 +
dlls/d3dx8/d3dx8.spec |8 ++--
dlls/d3dx8/texture.c | 86
include/d3dx8.h|1 +
include/d3dx8tex.h
d3dx8tex.h with the mentioned name.
I should be done now. Please send comments if not.
---
dlls/d3dx8/Makefile.in |1 +
dlls/d3dx8/d3dx8.spec |8 ++--
dlls/d3dx8/texture.c | 86
include/d3dx8.h|1 +
include/d3dx8tex.h
I have created a /dlls/d3dx8/texture.c file where to put all functions
related to textures and d3dx8.
I have included D3DXIMAGE_FILEFORMAT in the patch because it is referred
by D3DXIMAGE_FILEFORMAT which is referred in the function. If not
included, it would not compile. They both are now in
Find attached some data on d3dx8, d3dx9_xx and d3dx10_xx implementations:
dll files by d3dx extension:
d3dx8 1 dll files
d3dx9_xx 13 dll files
d3dx10_xx 4 dll files
Functions included in each d3dx:
DLL Number of functions
d3dx8 153
d3dx9_24 320
d3dx9_25
I am having problems with a bunch of three games that came together in
the same pack. They all abort qhen asking for installation with the
following line
wine: Call from 0x73ba1895 to unimplemented function
GDI32.dll.NamedEscape, aborting
Does anybody know what GDI32.dll.NamedEscape does?
Doe
I have not seen any patch committed beginning the implementation of
these libraries. Therefore, I was wondering which is the tree structure
for these dlls that all of you propose and Alexander is willing to commit.
I still do not see why it is not possible to have only one folder
dlls/d3dx9/ with the thirteen spec files inside. After all, the vast
majority of its code is repeated and it is the same system ctl3d,
ctl3d32 and ctl3dv2 use as the three specs are in dlls/ctl3d32
This is not creating subfolders
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_25.dl
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
The web page indicating the status of the wine API:
http://www.winehq.org/site/winapi_stats
is corrupted and indicates an SQL error. I assume that there is some
information in the database corrupted:
Warning: mysql_num_fields(): supplied argument is not a valid MySQL
result resource in /home
I understand that for some people the mailing list is a far better thing. May
be for some other, a forum is better.
Why not having both? Running a forum does not exclude continuing with the
mailing lists and could add users and developpers who find more easy coordinate
through a forum.
Config
23 matches
Mail list logo
