Dan Kegel d...@kegel.com writes:
Ladies and gentlemen, I believe it's time
for a 64 bit winetest.exe to be added to the daily build,
and for 64 bit test data to start showing up at http://test.winehq.org.
I'm working on that. I haven't uploaded the results but the current
status is that there
Hi Scott,
I'm trying to install Wine, but I cannot connect to the server. Just thought
I would let you know.
Regards,
Dustin
Hi folks,
it seems odd to me that Wine doesn't have a tool like
dxdiag yet. We often have people complain that
graphics aren't working, and we have to ask them
to do things like run glxgears as diagnostics.
Would it make sense to implement our own
dxdiag.exe program?
This seems like it
On Sunday 28 December 2008 03:02:34 am Roderick Colenbrander wrote:
On Windows the main task of dxdiag is to show some diagnostic info and to
run some very basic network, sound and 3d tests. In case of Wine 3D testing
would be the most important feature but I'm not sure if it is that useful.
Chris Robinson chris.kcat at gmail.com writes:
I think such a thing could still be useful. It'll help figure out what kind
of
info apps are getting from a given system, and help determine if problems are
app-specific or more general system/wine-related. It can also serve as a
basic
Thanks a lot for your hints, Reece and Dmitry. I didn't realize the
difference between WndProcs and DlgProcs.
I send a new try and hope everything is okay now :)
http://www.winehq.org/pipermail/wine-patches/2008-December/066762.html
--
Andre
2008/12/28 Francois Gouget fgou...@free.fr:
-FIXME(No free constant found to load environemnt bump mapping
matrix into the shader. texbem instruction will not apply bump mapping\n);
+FIXME(No free constant found to load environement bump mapping
matrix into the
2008/12/28 Dan Kegel d...@kegel.com:
Hi folks,
it seems odd to me that Wine doesn't have a tool like
dxdiag yet. We often have people complain that
graphics aren't working, and we have to ask them
to do things like run glxgears as diagnostics.
Would it make sense to implement our own
2008/12/28 Andrew Fenn andrewf...@gmail.com:
+void WINAPI XInputEnable(bool enable)
Does this compile? bool is a C++ type. Also, don't forget to add the
prototype to the header, I noticed they're missing for all the other
xinput functions as well.
2008/12/28 Vincent Pelletier plr.vinc...@gmail.com:
+WARN((%p) Creating an oversized surface: %ix%i\n, This,
This-pow2Height, This-pow2Width);
pow2Height and pow2Width are unsigned, so you'd want to use %u there.
On Sun, Dec 28, 2008 at 6:24 AM, Henri Verbeet hverb...@gmail.com wrote:
... I think the main use of such an application would be
dumping information like supported caps, texture formats, etc in case
of D3D and supported extensions, pixelformats, various limits, drivers
strings, etc. for
Le Sunday 28 December 2008 15:46:46 Henri Verbeet, vous avez écrit :
pow2Height and pow2Width are unsigned, so you'd want to use %u there.
Done, thanks.
Also, git didn't commit half of the change (I'm too used to subversion
commiting files in the state they are when changelog is saved...). They
Hi.
Attached patch is enough to cure the failure in Operation Flashpoint when
its menu is displayed on my little i945GM card.
As the oversised case is (was) explicitely treated as a failure, I think there
is some reasone for it. Does someone remember what it is for ?
Regards,
--
Vincent
2008/12/28 Dan Kegel d...@kegel.com:
On Sun, Dec 28, 2008 at 6:24 AM, Henri Verbeet hverb...@gmail.com wrote:
... I think the main use of such an application would be
dumping information like supported caps, texture formats, etc in case
of D3D and supported extensions, pixelformats, various
On Sa, 2008-12-27 at 23:20 -0800, Dan Kegel wrote:
Hi folks,
it seems odd to me that Wine doesn't have a tool like
dxdiag yet. We often have people complain that
graphics aren't working, and we have to ask them
to do things like run glxgears as diagnostics.
Would it make sense to implement
Le Sunday 28 December 2008 16:21:25 Vincent Pelletier, vous avez écrit :
Attached patch is enough to cure the failure in Operation Flashpoint when
its menu is displayed on my little i945GM card.
It also fixes mipmap test in d3d9/tests/visual.c, removing the need for a
patch I sent earlier
2008/12/28 Vincent Pelletier plr.vinc...@gmail.com:
Hi.
Attached patch is enough to cure the failure in Operation Flashpoint when
its menu is displayed on my little i945GM card.
As the oversised case is (was) explicitely treated as a failure, I think there
is some reasone for it. Does
Le Friday 26 December 2008 22:35:18 Vincent Pelletier, vous avez écrit :
I'm not sure where to add it. I've added some line in
d3d9/tests/visual.c:pointsize_test (attached too). As I wrote that
test to succeed on wine and did not run it on any windows version, I
would be happy if someone could
2008/12/28 Vincent Pelletier plr.vinc...@gmail.com:
Le Sunday 28 December 2008 16:21:25 Vincent Pelletier, vous avez écrit :
Attached patch is enough to cure the failure in Operation Flashpoint when
its menu is displayed on my little i945GM card.
It also fixes mipmap test in
On Sun, Dec 28, 2008 at 6:24 AM, Henri Verbeet hverb...@gmail.com wrote:
... I think the main use of such an application would be
dumping information like supported caps, texture formats, etc in case
of D3D and supported extensions, pixelformats, various limits, drivers
strings, etc. for
On Sun, Dec 28, 2008 at 7:43 AM, Roderick Colenbrander
thunderbir...@gmx.net wrote:
Also, isn't it annoying that native dxdiag always says
the graphics card is X Windows? Why is that, and
should we change Wine so that the true card's info
is reported by native dxdiag?
Native dxdiag is
On Sun, Dec 28, 2008 at 7:43 AM, Roderick Colenbrander
thunderbir...@gmx.net wrote:
Also, isn't it annoying that native dxdiag always says
the graphics card is X Windows? Why is that, and
should we change Wine so that the true card's info
is reported by native dxdiag?
Native dxdiag
This patch is wrong; You can't use oversized surfaces for 3D texturing
because the driver doesn't support the given size.
What is the texture size limit on your card, and what texture size does the
game try to use?
However, the oversize surface stuff is kinda hacky and poorly integrated. I
think
Also, isn't it annoying that native dxdiag always says
the graphics card is X Windows? Why is that, and
should we change Wine so that the true card's info
is reported by native dxdiag?
I don't know, but if I were to guess I'd say it probably doesn't get
that information from d3d, but
Also, isn't it annoying that native dxdiag always says
the graphics card is X Windows? Why is that, and
should we change Wine so that the true card's info
is reported by native dxdiag?
I don't know, but if I were to guess I'd say it probably doesn't get
that information from
On Sun, Dec 28, 2008 at 8:43 AM, Roderick Colenbrander
thunderbir...@gmx.net wrote:
Native dxdiag is checking the name of the display driver which in our case
winex11.drv and I guess this is just the identifier of Winex11.drv. Inside
winex11.drv we don't really have the knowledge about the 3d
Le Sunday 28 December 2008 16:53:44, vous avez écrit :
This patch is wrong; You can't use oversized surfaces for 3D texturing
because the driver doesn't support the given size.
So it seems fixing the crash I get requires to make CreateSurface fail when
texture is marked as oversized (currently
I think we should stay as close to the way the windows tools work and avoid
inventing too much wine-specific things. This is how I understand the
windows tools:
* dxdiag.exe: Prints DLL information, has very simple tests for ddraw, d3d,
dsound, dmusic, dplay. The tests just show that a device can
On Sun, Dec 28, 2008 at 8:43 AM, Roderick Colenbrander
thunderbir...@gmx.net wrote:
Native dxdiag is checking the name of the display driver which in our
case
winex11.drv and I guess this is just the identifier of Winex11.drv.
Inside
winex11.drv we don't really have the knowledge
On Sunday 28 December 2008 07:43:57 am Roderick Colenbrander wrote:
Native dxdiag is checking the name of the display driver which in our case
winex11.drv and I guess this is just the identifier of Winex11.drv. Inside
winex11.drv we don't really have the knowledge about the 3d hardware we are
On Sun, Dec 28, 2008 at 9:39 PM, Henri Verbeet hverb...@gmail.com wrote:
Also, don't forget to add the prototype to the header, I noticed they're
missing for all the other xinput functions as well.
I think I have added the prototypes correctly to the header file.
Could you have a quick look at
It tries to create a 1024x1024 texture, and my card (Intel 945GM) is
limited
to 512x512:
glxinfo -l | grep GL_MAX_TEXTURE_SIZE
GL_MAX_TEXTURE_SIZE = 512
Wow, that is small. Even my pretty old radeon 9000 supports 2048x2048
textures...
I recommend to check the max texture size on
I can't imagine that being inaccessible by X apps.. and I believe I've
seen
some apps report this info. It's something gdi32/user32 can then get
for a
particular screen/adapter by calling into winex11.drv (if not also
something
wined3d can use), instead of reporting X Windows for the card
it's almost that. but it needs some changes.
first you put the prototypes after the defines and typedefs, they may be needed
for the prototypes.
second you don't put variable names in the protypes, it should be something
like:
DWORD WINAPI XInputGetState(DWORD, XINPUT_STATE*);
see the
On Sunday 28 December 2008 07:43:57 am Roderick Colenbrander wrote:
Native dxdiag is checking the name of the display driver which in our
case
winex11.drv and I guess this is just the identifier of Winex11.drv.
Inside
winex11.drv we don't really have the knowledge about the 3d hardware we
Andrew Fenn wrote:
I think I have added the prototypes correctly to the header file.
Could you have a quick look at my patch and tell me if I am doing that
right?
+XINPUT_CAPABILITIES* pCapabilities)
Missing semicolon.
Vitaliy.
2008/12/28 Stefan Dösinger ste...@codeweavers.com:
It tries to create a 1024x1024 texture, and my card (Intel 945GM) is
limited
to 512x512:
glxinfo -l | grep GL_MAX_TEXTURE_SIZE
GL_MAX_TEXTURE_SIZE = 512
Wow, that is small. Even my pretty old radeon 9000 supports 2048x2048
textures...
Le Sunday 28 December 2008 18:11:15, vous avez écrit :
Wow, that is small. Even my pretty old radeon 9000 supports 2048x2048
textures...
I recommend to check the max texture size on Windows(does the game work on
this card on Windows?). I'd say there's some driver problem here, 512x512
sounds
2008/12/28 Andrew Fenn andrewf...@gmail.com:
On Sun, Dec 28, 2008 at 9:39 PM, Henri Verbeet hverb...@gmail.com wrote:
Also, don't forget to add the prototype to the header, I noticed they're
missing for all the other xinput functions as well.
I think I have added the prototypes correctly to
Sorry guys, that was a really bad patch I submitted much better ones
to wine-patches already.
[1/2] xinput: Added prototypes to header file
[2/2] xinput: Added stub for XInputEnable
yup, the patches look good on a quick glance.
Date: Mon, 29 Dec 2008 02:30:26 +0700
From: andrewf...@gmail.com
To: hverb...@gmail.com; wine-de...@kievinfo.com; ricardo_barb...@hotmail.com
Subject: Re: xinput: Add stub XInputEnable
CC:
Le Sunday 28 December 2008 20:20:43 Vincent Pelletier, vous avez écrit :
I discussed with Thunderbird on IRC right after sending last reply. I
noticed that I was not using latest intel driver, so I'm building them atm
to give it a try. (Debian sid is quite outdated these days, because of work
Alexandre Julliard wrote:
While you are fixing it you should fix it properly by preserving the old
pointer on failure.
Thanks. Sent fixed patch.
Vitaliy
Louis wrote:
Wine needs a dxdiag.exe as some apps expect it to be present,
like for example GameShadow. I once gave it a shot already, see
http://bugs.winehq.org/show_bug.cgi?id=14118
Thanks for the link.
I refreshed your patch, and also added in the parsing
for the commandline options used by
Hi,
As there will be a new Gecko release soon, I'd like to give you a good
background over what's going on as I feel that there is some
misunderstanding on it that I'd like to clarify. I'm sorry for the long
mail.
First, let me give you a short history of the Gecko package.
As we started
Thanks, Jacek, we're really looking forward to it!
46 matches
Mail list logo
