Am Donnerstag 22 Februar 2007 16:46 schrieb Stefan Dösinger:
That said, this is a Direct3D7 application, where the window setup is done
BEFORE creating the Direct3D device(which calls Init3D in wined3d). So I
gather that SetupFullscreenWindow should not be called during Init3D in the
d3d7
On 21/02/07, Pavel Troller [EMAIL PROTECTED] wrote:
The last trace which appeared in the log is 2683, so
IWineD3DDevice_CreateAdditionalSwapChain() didn't return. I'm going bananas
from those names; where the hell this one grows :-) ? grep, as obvious,
shows
its calls only.
Am Donnerstag 22 Februar 2007 15:04 schrieb Pavel Troller:
So I commented out the SetWindowPos() call in ..._SetupFullscreenWindow
(on lines 12512 of the today's source) and... voilla, the game starts and
runs perfectly. My son has verified it and didn't find any problems.
Yeah, the
On 22/02/07, Pavel Troller [EMAIL PROTECTED] wrote:
OK, never mind. I can continue debugging tonight, just now the machine is
occupied by my son and his friend :-). I will look at SetWindowPos(). Could you
tell me in which file its source is ?
That's in dlls/user32/winpos.c, but I'm not sure
Am Donnerstag 22 Februar 2007 16:15 schrieb H. Verbeet:
On 22/02/07, Pavel Troller [EMAIL PROTECTED] wrote:
OK, never mind. I can continue debugging tonight, just now the machine is
occupied by my son and his friend :-). I will look at SetWindowPos().
Could you tell me in which file its
On Mi, 2007-02-21 at 20:31 +0100, Pavel Troller wrote:
Where is SetWindowPos located ?
You can find a function with findfunc
[EMAIL PROTECTED]:~/wine.cvs/src$ tools/findfunc SetWindowPos
dlls/user32/winpos.c:BOOL WINAPI SetWindowPos(
and also
dlls/winex11.drv/winpos.c:BOOL
OK, did it. Sending two traces: A bad one, and a good one made by wine just
before the above commit.
With regards, Pavel Troller
trace:d3d:IWineD3DDeviceImpl_SetupFullscreenWindow Old style was
9000,0008, setting to 9008,0008
trace:d3d:IWineD3DDeviceImpl_SetupFullscreenWindow Old style was
9000,0008, setting to 9008,0008
trace:ddraw:IDirectDrawImpl_FlipToGDISurface (0x19daf8)
This here seems strange. If you compare that to the good log you'll see that
IWineD3DDeviceImpl_Init3D was left way
You can do the following:
- Run the game in winedbg and see if it catches the execption and gives a
backtrace and crash position
There is no such exception, at least winedbg doesn't catch any. Is a special
action (command etc.)
Oops. Unfinished mail sent. I meant:
Is a special action
On 21/02/07, Pavel Troller [EMAIL PROTECTED] wrote:
I'm a bit confusd because I failed to find the code for
D3DCB_CreateAdditionalSwapChain(), I found only its call in device.c and its
definition in wined3d_interface.h.
That's D3D7CB_CreateAdditionalSwapChain() in dlls/ddraw/ddraw.c
On 21/02/07, Pavel Troller [EMAIL PROTECTED] wrote:
I'm a bit confusd because I failed to find the code for
D3DCB_CreateAdditionalSwapChain(), I found only its call in device.c and
its
definition in wined3d_interface.h.
That's D3D7CB_CreateAdditionalSwapChain() in dlls/ddraw/ddraw.c
Hi!
On 21/02/07, Pavel Troller [EMAIL PROTECTED] wrote:
The last trace which appeared in the log is 2683, so
IWineD3DDevice_CreateAdditionalSwapChain() didn't return. I'm going bananas
from those names; where the hell this one grows :-) ? grep, as obvious, shows
its calls only.
On 21/02/07, Pavel Troller [EMAIL PROTECTED] wrote:
The last trace which appeared in the log is 2683, so
IWineD3DDevice_CreateAdditionalSwapChain() didn't return. I'm going bananas
from those names; where the hell this one grows :-) ? grep, as obvious,
shows
its calls only.
On 20/02/07, Pavel Troller [EMAIL PROTECTED] wrote:
Hi!
I've tried 0.9.31 and it seems that there is a regression in at least two
games:
- Fallout Tactics (BOS.exe): Shows a dialog stating
C:\dev\phoenix\display\win32\win32_window.cpp(873): **fatal error**:
Could not create display buffers
Am Dienstag 20 Februar 2007 06:37 schrieb Pavel Troller:
- Steam based games, mainly HL2: During game load, the screen goes black.
Moving the cursor causes sound effects as it hovers across the menus and
buttons, so the program runs, but nothing can be seen.
This regression is known, and it
Hi!
Am Dienstag 20 Februar 2007 06:37 schrieb Pavel Troller:
- Steam based games, mainly HL2: During game load, the screen goes black.
Moving the cursor causes sound effects as it hovers across the menus and
buttons, so the program runs, but nothing can be seen.
This regression is known,
Am Dienstag 20 Februar 2007 21:55 schrieb Pavel Troller:
Hi!
Am Dienstag 20 Februar 2007 06:37 schrieb Pavel Troller:
- Steam based games, mainly HL2: During game load, the screen goes
black. Moving the cursor causes sound effects as it hovers across the
menus and buttons, so the
I don't know about this regression. Can you do a bisect?
Yes, done. It's the following commit:
commit 388499ff28616ef03bf8949a78e658e1bdb4e4fc
Author: Stefan DĂśsinger [EMAIL PROTECTED]
Date: Wed Feb 14 17:59:08 2007 +0100
wined3d: More fullscreen window fixes.
The
Hi!
I've tried 0.9.31 and it seems that there is a regression in at least two
games:
- Fallout Tactics (BOS.exe): Shows a dialog stating
C:\dev\phoenix\display\win32\win32_window.cpp(873): **fatal error**:
Could not create display buffers
and then another one about abnormal termination of the
19 matches
Mail list logo
