[Bug 15839] New: Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Summary: Games for Windows Live fails to initialize, resulting
                    Fallout 3 crash
           Product: Wine
           Version: 1.1.7
          Platform: PC
               URL: http://www.gamesforwindows.com
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

When starting Fallout 3, Xlive.dll wants to create a warning message to
eventlog, this will cause later Fallout 3 crash after choosing new game in the
menu.

Eventlog entry:
fixme:advapi:RegisterEventSourceW ((null),L"XLive"): stub
fixme:advapi:ReportEventW
(0xcafe4242,0x0002,0x0000,0x80000002,(nil),0x0004,0x00000000,0x33e540,(nil)):
stub
warn:eventlog:ReportEventW L"Fallout3.exe"
warn:eventlog:ReportEventW L"1.0.0.12"
warn:eventlog:ReportEventW L"1.2.0241.0 C:\windows\system32\xlive.dll"
warn:eventlog:ReportEventW L"\n0x80004005\n\nGames for Windows LIVE
DLL\nC:\windows\system32\msidcrl40.dll 4.200.513.1"
fixme:advapi:DeregisterEventSource (0xcafe4242) stub

Mentioned crash occuring later:
wine: Unhandled page fault on read access to 0x00000000 at address 0xad8cdb
(thread 0024), starting debugger...
First chance exception: page fault on read access to 0xffffffff in 32-bit code
(0x013c92e3).

Backtrace:
=>1 0x013c92e3 in xlive (+0x892e3) (0x7b5bf8d8)
  2 0x006250e2 in fallout3 (+0x2250e2) (0x0322ece0)
  3 0x00000005 (0x00e8c008)
  4 0x009830d0 in fallout3 (+0x5830d0) (0x00ae4410)

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #1 from Andras Kovacs   2008-10-29 11:13:37 ---
Created an attachment (id=16967)
 --> (http://bugs.winehq.org/attachment.cgi?id=16967)
console + eventlog

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #2 from Austin English   2008-10-29 13:14:34 ---
Does:
$ regsvr32 Xlive.dll

help?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #3 from Andras Kovacs   2008-10-29 13:17:51 ---
not really, it has no DllRegisterServer method.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #4 from Andras Kovacs   2008-10-29 13:19:10 ---
fallout's setup installed it by official microsoft's setup. It should be
configured.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Mike Ellery  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Sergey Alirzaev  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #5 from Sergey Alirzaev   2008-10-30 03:38:26 ---
*** This bug has been confirmed by popular vote. ***

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #6 from Jo   2008-10-30 07:57:24 ---
Created an attachment (id=16985)
 --> (http://bugs.winehq.org/attachment.cgi?id=16985)
fallout hangs when loading from main menu

everything works perfectly but when i choose new game from main menu the game
hangs, sound keeps working, mouse cursor can be fixed with mousewarp disabled

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Sarunas  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #7 from Sarunas   2008-10-30 14:59:17 ---
not so sure if this is xlive..

Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x00ad8cdb).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:00ad8cdb ESP:79fed064 EBP:00000001 EFLAGS:00010206(   - 00      - RIP1)
 EAX:00000000 EBX:05b6ee40 ECX:3ad5c133 EDX:14f28258
 ESI:00000000 EDI:05ac4178
Stack dump:
0x79fed064:  0000001d 05ac4178 05ac4178 00000000
0x79fed074:  02f45a94 00000076 00000000 00000076
0x79fed084:  79fed1d8 740ddfee 767b1c1a 79fed358
0x79fed094:  7b3cdc63 00000001 00000000 00000076
0x79fed0a4:  00000000 73657275 00000018 00100300
0x79fed0b4:  00000000 000000bc 00000000 00000003
Backtrace:
0x00ad8cdb: movl        0x0(%esi),%eax
Modules:
Module  Address                 Debug info      Name (131 modules)
PE        340000-  356000       Deferred        xinput1_3
PE        400000- 133d000       Export          fallout3
PE       1340000- 1ced000       Deferred        xlive

if I read this correctly, 0x00ad8cdb address is in fallout3 (400000- 133d000)
if I am wrong, pls correct it :)

now.. do someone know how to use winedbg ?? my X is taken by Fallout3, which
wont give it back, so I have to (anyhow ??? ) use debugger wich breaks on this
exception and is accessable via terminal..

and wine is complaining like: "warn:file:wine_nt_to_unix_file_name
L"winedbg.exe" not found in" huh? is it exe ? I found only linux bin..

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Josko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #8 from Josko   2008-10-30 15:05:01 ---
(In reply to comment #7)
> my X is taken by Fallout3

Try to set Fallout to be Windowed, after this setting my X is still working
after crash...

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Tomas Klimek  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #9 from Tomas Klimek   2008-10-30 15:25:22 ---
> my X is taken by Fallout3

Another idea is using separate X session. Very usefull in this is
http://www.dolezel.info/projects/qgamex.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #16985|application/octet-stream    |text/plain
          mime type|                            |

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #10 from Sarunas Valaskevicius   2008-10-31 02:30:42 ---
> my X is taken by Fallout3, which wont give it back,

well, I myself though of a way to start wine in tty1 while exporting X to use
tty7, should help, not tried, (though 1st suggestion (to start wine in Windowed
mode, or even make wine virtual desktop) is easier :) )

also, will try to debug only having a bit more time... (tomorrow maybe)
ghmm  
movl        0x0(%esi),%eax
why is there a 0 ?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Erich Hoover  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #11 from Erich Hoover   2008-11-01 00:50:19 ---
I ran a full trace (-relay) and recorded the log, it looks to me like the game
doesn't crash until a LONG time after that reported event.  I don't have time
to look into it detail, but if I am reading the log correctly then wine is
giving the game a pointer to some vertex information where it's just released
that information:
0033:trace:d3d9:IDirect3DDevice9Impl_GetVertexDeclaration (0x153468) : Relay+
0033:trace:d3d:IWineD3DDeviceImpl_GetVertexDeclaration (0x185f58) :
ppDecl=0x7b4fe8c0
0033:trace:d3d_decl:IWineD3DVertexDeclarationImpl_AddRef (0x149d8068) : AddRef
increasing from 1
0033:trace:d3d9:IDirect3DVertexDeclaration9Impl_AddRef (0x149d8020) : AddRef
from 880
0033:trace:d3d_decl:IWineD3DVertexDeclarationImpl_GetParent (0x149d8068) :
returning 0x149d8020
0033:trace:d3d_decl:IWineD3DVertexDeclarationImpl_Release (0x149d8068) :
Releasing from 2
0033:trace:d3d9:IDirect3DDevice9Impl_GetVertexDeclaration (0x153468) :
returning 0x149d8020
0033:CALL xlive.5002() ret=006250e2

(the exception and crash follow shortly thereafter)

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #12 from Mirek Slugen   2008-11-01 04:50:36 ---
Created an attachment (id=17024)
 --> (http://bugs.winehq.org/attachment.cgi?id=17024)
log with +snoop enabled

I start the game, try to continue from last position and then game crashed
while loading saved game.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Mirek Slugen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #13 from Mirek Slugen   2008-11-01 04:52:03 ---
> From the log above the  problem could be related to function

D3DXMatrixMultiplyTranspose() from d3dx9_38 library.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #14 from Mirek Slugen   2008-11-01 07:33:16 ---
It really might be something in D3D, not in xlive.dll:

important part exactly before crash (all-relay):

0029:trace:heap:RtlAllocateHeap (0x110000,0000000a,00000050): returning
0x15e76df8
0029:trace:heap:RtlAllocateHeap (0x110000,0000000a,00000096): returning
0x1de998a0
0029:trace:d3d:IWineD3DDeviceImpl_AddResource (0x1691c0) : Adding Resource
0x15e76df8
0029:trace:d3d:IWineD3DDeviceImpl_CreateIndexBuffer (0x1691c0) : Created
resource 0x15e76df8
0029:trace:d3d:CreateIndexBufferVBO Creating VBO for Index Buffer 0x15e76df8
0029:trace:d3d:ActivateContext (0x1691c0): Selecting context for render target
0x14720168, thread 41
0029:trace:d3d_surface:IWineD3DBaseSurfaceImpl_GetContainer (This 0x14720168,
riid {34d01b10-6f30-11d9-c687-00046142c14f}, ppContainer
0x7b07c008)
0029:trace:d3d_surface:IWineD3DBaseSurfaceImpl_GetContainer Relaying to
QueryInterface
0029:trace:d3d:IWineD3DBaseSwapChainImpl_QueryInterface
(0x1b2b70)->({34d01b10-6f30-11d9-c687-00046142c14f},0x7b07c008)
0029:trace:d3d:IWineD3DBaseSwapChainImpl_AddRef (0x1b2b70) : AddRef increasing
from 1
0029:trace:d3d:FindContext Rendering onscreen
0029:trace:d3d:IWineD3DBaseSwapChainImpl_Release (0x1b2b70) : ReleaseRef to 1
0029:trace:wgl:wglGetCurrentContext  returning 0x186ef238
0029:trace:d3d:ActivateContext Already using gl context 0x186ef238
0029:trace:d3d:CreateIndexBufferVBO Successfully created vbo 1738 for index
buffer 0x15e76df8
0029:trace:d3d:IWineD3DDeviceImpl_CreateIndexBuffer (0x1691c0) : Len=118,
Use=0, Format=(101,WINED3DFMT_INDEX16), Pool=1 - Memory@0x15e
76df8, Iface@0x1de998a0
0029:trace:d3d9:IDirect3DDevice9Impl_AddRef (0x169198) : AddRef from 6483
0029:trace:d3d9:IDirect3DDevice9Impl_CreateIndexBuffer (0x169198) : Created
index buffer 0x2075af60
0029:trace:d3d9:IDirect3DIndexBuffer9Impl_Lock (0x2075af60) Relay
0029:trace:d3d:IWineD3DIndexBufferImpl_Lock (0x15e76df8) : offset 0, size 118,
Flags=0
0029:trace:d3d9:IDirect3DIndexBuffer9Impl_Unlock (0x2075af60) Relay
0029:trace:d3d:IWineD3DIndexBufferImpl_Unlock (0x15e76df8)
0029:trace:d3d:ActivateContext (0x1691c0): Selecting context for render target
0x14720168, thread 41
0029:trace:d3d:IWineD3DIndexBufferImpl_Unlock glBindBufferARB call ok
indexbuffer.c / 187
0029:trace:d3d:IWineD3DIndexBufferImpl_Unlock glBufferSubDataARB call ok
indexbuffer.c / 190
0029:trace:d3d:IWineD3DIndexBufferImpl_Unlock (0x15e76df8): after
glBufferSubDataARB
0029:trace:d3d:IWineD3DIndexBufferImpl_Unlock (0x15e76df8): after LEAVE_GL
0029:trace:d3d:IWineD3DIndexBufferImpl_Unlock (0x15e76df8): before
MarkStateDirty
0029:trace:d3d:IWineD3DIndexBufferImpl_Unlock (0x15e76df8): after
MarkStateDirty
0029:trace:seh:raise_exception code=c0000005 flags=0 addr=0xad8cdb
0029:trace:seh:raise_exception  info[0]=00000000
0029:trace:seh:raise_exception  info[1]=00000000
0029:trace:seh:raise_exception  eax=00000000 ebx=07625dd4 ecx=c9307292
edx=16b03918 esi=00000000 edi=09d2d0a0
0029:trace:seh:raise_exception  ebp=00000001 esp=7b07c064 cs=0073 ds=007b
es=007b fs=0033 gs=003b flags=00210206
0029:trace:seh:call_stack_handlers calling handler at 0xc54070 code=c0000005
flags=0
0029:trace:seh:call_stack_handlers handler at 0xc54070 returned 1
0029:trace:seh:call_stack_handlers calling handler at 0xc32d8b code=c0000005
flags=0
0029:trace:seh:call_stack_handlers handler at 0xc32d8b returned 1
0029:trace:seh:call_stack_handlers calling handler at 0xc26758 code=c0000005
flags=0
0029:trace:seh:call_stack_handlers handler at 0xc26758 returned 1
0029:trace:seh:call_stack_handlers calling handler at 0xc6fa10 code=c0000005
flags=0
0029:trace:seh:call_stack_handlers handler at 0xc6fa10 returned 1
0029:trace:seh:call_stack_handlers calling handler at 0x7efc6a50 code=c0000005
flags=0
0029: create_event( access=001f0003, attributes=00000002, manual_reset=1,
initial_state=0, objattr={rootdir=(nil),sd={},name=L""} )
0029: create_event() = 0 { handle=0x164 }
wine: Unhandled page fault on read access to 0x00000000 at address 0xad8cdb
(thread 0029), starting debugger...
0029:trace:reg:NtOpenKey ((nil),L"Machine\Software\Microsoft\Windows
NT\CurrentVersion\AeDebug",f003f,0x7b07bb10)
0029: open_key( parent=(nil), access=000f003f, attributes=00000000,
name=L"Machine\Software\Microsoft\Windows NT\CurrentVersion\Ae
Debug" )
0029: open_key() = 0 { hkey=0x1e0 }
0029:trace:reg:NtOpenKey <- 0x1e0
0029:trace:reg:NtQueryValueKey (0x1e0,L"Debugger",2,(nil),0)
0029: get_key_value( hkey=0x1e0, name=L"Debugger" )
0029: get_key_value() = 0 { type=1, total=46, data={}

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #15 from Mirek Slugen   2008-11-01 09:56:48 ---
(In reply to comment #11)
> I ran a full trace (-relay) and recorded the log, it looks to me like the game
> doesn't crash until a LONG time after that reported event.  I don't have time
> to look into it detail, but if I am reading the log correctly then wine is
> giving the game a pointer to some vertex information where it's just released
> that information:

I think you are right, it looks like some problem in vertex shaders creation.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #16 from Vitaliy Margolen   2008-11-01 11:34:57 ---
Please do not paste logs! Attach them instead.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #17 from Mirek Slugen   2008-11-01 12:10:53 ---
Created an attachment (id=17031)
 --> (http://bugs.winehq.org/attachment.cgi?id=17031)
Interesting part from crash with WINEDEBUG="+all,-relay"

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Adrien Kwok  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from Adrien Kwok   2008-11-01 22:03:53 ---
WINE tells me that indeed xlive is causing many troubles in the game.

wine: Unhandled page fault on read access to 0x00000000 at address 0xad8cdb
(thread 0027), starting debugger...
First chance exception: page fault on read access to 0xffffffff in 32-bit code
(0x013c92e3).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:013c92e3 ESP:79de6898 EBP:79de68c8 EFLAGS:00010246(   - 00      -RIZP1)
 EAX:79de68b8 EBX:00000000 ECX:7ee85800 EDX:7ee85804
 ESI:1856de80 EDI:031cc398
Stack dump:
0x79de6898:  52845180 031cc398 1856de80 00000000
0x79de68a8:  031cc398 1856de80 79de6898 00000000
0x79de68b8:  79de69f8 0144edfd 2a21bb80 00000000
0x79de68c8:  031e06b0 006250e2 5285d1aa 7b855fb0
0x79de68d8:  00000017 00009474 7b890980 790169dc
0x79de68e8:  1856de80 0000003b c1c8e498 44796f00
Backtrace:
=>1 0x013c92e3 in xlive (+0x892e3) (0x79de68c8)
  2 0x006250e2 in fallout3 (+0x2250e2) (0x031e06b0)
  3 0x00000005 (0x00e8c008)
  4 0x009830d0 in fallout3 (+0x5830d0) (0x00ae4410)
  5 0xfffff598 (0xe8f18b56)
  6 0x00000000 (0x00000000)
0x013c92e3: int $0x1

The backtrace talks about

1 0x013c92e3 in xlive (+0x892e3) (0x79de68c8)
2 0x006250e2 in fallout3 (+0x2250e2) (0x031e06b0)

twice but in two different memory allocations.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #19 from Adrien Kwok   2008-11-01 22:05:52 ---
(In reply to comment #13)
> From the log above the  problem could be related to function
> D3DXMatrixMultiplyTranspose() from d3dx9_38 library.

should we run the library in native then?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #20 from Mirek Slugen   2008-11-02 04:13:02 ---
(In reply to comment #19)
> (In reply to comment #13)
> > From the log above the  problem could be related to function
> > D3DXMatrixMultiplyTranspose() from d3dx9_38 library.
>
> should we run the library in native then?

This library is not yet implemented in wine, so it is only native.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #21 from joaopa   2008-11-02 05:28:55 ---
Following the comment 13, this bug should be renamed in "Fallout needs a
d3dx9_38 dll". This would make clear what the wine developpers need to do to
fix this bug.

It is a quite easy task.

Joaopa

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #22 from Mirek Slugen   2008-11-02 06:51:50 ---
(In reply to comment #21)
> Following the comment 13, this bug should be renamed in "Fallout needs a
> d3dx9_38 dll". This would make clear what the wine developpers need to do to
> fix this bug.
>
> It is a quite easy task.
>
> Joaopa

We are not sure if crash is in d3dx9_38 dll

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Severin Heiniger  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jason Kraus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Mikael Åkersund  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #23 from Mikael Åkersund   2008-11-04 08:19:19 ---
(In reply to comment #21)
> Following the comment 13, this bug should be renamed in "Fallout needs a
> d3dx9_38 dll". This would make clear what the wine developpers need to do to
> fix this bug.
>
> It is a quite easy task.
>
> Joaopa

To get past the New Game crash edit Documents/My Games/FALLOUT.INI and set 
bUseFaceGenHeads=0

You'll be able to see the intro movie, your birth, customize your character 
and take your first steps. All characters won't have any heads and the game 
is very likely to crash soon after that.

The reason that Fallout3 crashes when starting a new game is that some of 
the shader effects added require SM 2.0 B or higher. 
Oblivion only required SM 2.0. Windows users with Radeon 9x00 cards or 
Intel 965 chipsets have similar crashes.

There's an effort over at http://www.oldblivion.com/sm/index.php?topic=5831.0 
to rewrite Fallouts shader effects to SM 2.0, much in the same way as was 
done with OldOblivion.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #24 from Erich Hoover   2008-11-04 09:20:39 ---
(In reply to comment #23)
> To get past the New Game crash edit Documents/My Games/FALLOUT.INI and set 
> bUseFaceGenHeads=0

Confirmed.
> The reason that Fallout3 crashes when starting a new game is that some of 
> the shader effects added require SM 2.0 B or higher. 
> Oblivion only required SM 2.0. Windows users with Radeon 9x00 cards or 
> Intel 965 chipsets have similar crashes.

I thought Wine had support for SM 2.0-3.0 (earlier than 2.0 not being
supported).  Is this not the case, did Wine skip 2.0b, or is this a bug in the
implementation?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #25 from Mirek Slugen   2008-11-04 13:07:40 ---
> To get past the New Game crash edit Documents/My Games/FALLOUT.INI and set 
> bUseFaceGenHeads=0

For me works too, so this bug should be renamed to "Fallout 3 crash because of
lack SM 2.0B support" or something similar.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #26 from Vitaliy Margolen   2008-11-04 21:34:32 ---
> > The reason that Fallout3 crashes when starting a new game is that some of 
> > the shader effects added require SM 2.0 B or higher. 
> > Oblivion only required SM 2.0. Windows users with Radeon 9x00 cards or 
> > Intel 965 chipsets have similar crashes.
>
> I thought Wine had support for SM 2.0-3.0 (earlier than 2.0 not being
> supported).  Is this not the case, did Wine skip 2.0b, or is this a bug in the
> implementation?

Before doing such claims you should check what drivers for those cards support.

Please everyone post what video card and driver version they have.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Sergey Alirzaev  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #27 from Sergey Alirzaev   2008-11-04 21:46:23 ---
(In reply to comment #26)
> > I thought Wine had support for SM 2.0-3.0 (earlier than 2.0 not being
> > supported).  Is this not the case, did Wine skip 2.0b, or is this a bug in the
> > implementation?
>
> Before doing such claims you should check what drivers for those cards support.
>
> Please everyone post what video card and driver version they have.

nVidia gF6600 
nvidia v177.80

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #28 from Erich Hoover   2008-11-04 21:52:07 ---
(In reply to comment #26)
> Before doing such claims you should check what drivers for those cards support.
>
> Please everyone post what video card and driver version they have.

I think you replied to the wrong person, as I was asking a question about the
level of support.  Personally, I have an nVidia GeForce 8600M GT (512 MB
edition), which should support up through SM 4.0.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

silverj  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #29 from silverj   2008-11-05 00:17:01 ---
ATI HD4870 with 8.542 drivers.

According to
http://www.bethsoft.com/bgsforums/index.php?showtopic=897531&st=20&s...
there's at least one guy (the guy mentioning the fix being me) who's probably
running windows, has the game crashing at "new game" and gets through the intro
with bUseFaceGenHeads=0.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jo  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #30 from Jo   2008-11-05 03:40:46 ---
don't know if this is useful, after reading the fallout 3 remake forum on
oldblivion, i got 2 pc's here one xp and one linux both with 8500 GT gfx cards,
the windows version runs flawlessly on my gf's pc (an old celeron 3ghz w 1mb
ram) but it won't on wine, at least not whenever combat is engaged and there is
no heads, so i don't see that it's the cards that dont support the shader
model?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #31 from Mirek Slugen   2008-11-05 04:30:24 ---
(In reply to comment #26)
> > > The reason that Fallout3 crashes when starting a new game is that some of 
> > > the shader effects added require SM 2.0 B or higher. 
> > > Oblivion only required SM 2.0. Windows users with Radeon 9x00 cards or 
> > > Intel 965 chipsets have similar crashes.
> >
> > I thought Wine had support for SM 2.0-3.0 (earlier than 2.0 not being
> > supported).  Is this not the case, did Wine skip 2.0b, or is this a bug in the
> > implementation?
>
> Before doing such claims you should check what drivers for those cards support.
>
> Please everyone post what video card and driver version they have.

I have two nVidia video cards: GF 7900 GT and GF 9600 GT.

I tried both cards, with same results: "crash when loading or starting new
game" and if I use bUseFaceGenHeads=0 the game will crash after few seconds. So
I think it is wine problem, because both of my cards supports SM 3.0.

Video drivers: 177.80 (latest stable)

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #32 from Mirek Slugen   2008-11-07 06:35:08 ---
I finaly get it working without any crashes, I have to patch wine, I will send
patch when it will be finished, but trust me it is working flawlessly! :)

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #33 from Mirek Slugen   2008-11-07 11:18:40 ---
Created an attachment (id=17130)
 --> (http://bugs.winehq.org/attachment.cgi?id=17130)
Patch for WineD3D to set Driver an Description

Patch for Fallout 3, the game has broken detection of graphic card
capabalities, wine actualy supports SM2.0b perfectly even SM3.0, but the game
used only SM2.0 which is broken (not in wine, but in this game).

After apply this patch you should set 2 new registry options in
Software\Wine\Direct3D:
"VideoDescription"="NVIDIA GeForce 9600 GT"
"VideoDriver"="nv4_disp.dll"

VideoDescription - set this option on the same value as the name of your card
(my is NVIDIA GeForce 9600 GT, but NVIDIA GeForce 7900 GT is tested as working
too).
VideoDriver - nv4_disp.dll for all nvidia based cards, ati is not tested

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #34 from Mirek Slugen   2008-11-07 11:25:58 ---
If someone else can confirm that the game works with my patch then this bug can
be closed as failed.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Alexander Varnin  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #35 from Alexander Varnin   2008-11-07 11:38:22 ---
I'm going to check it. Now i'm downloading wine git to compile new version.
Probably, it can also fix Medal of Honor Airborne problem. There was some
problems with shaders too.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #36 from Erich Hoover   2008-11-07 11:46:00 ---
(In reply to comment #34)
> If someone else can confirm that the game works with my patch then this bug can
> be closed as failed.

Wouldn't this mean that someone would need to write something to detect and
properly report the driver information for different cards? (and, I presume,
fallback to the current reported info if detection fails)

I would say that this isn't that the game fails to detect the card, it's that
Wine gives the game the "wrong" information.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #37 from Mirek Slugen   2008-11-07 11:48:17 ---
(In reply to comment #35)
> I'm going to check it. Now i'm downloading wine git to compile new version.
> Probably, it can also fix Medal of Honor Airborne problem. There was some
> problems with shaders too.

MoHA works perfectly, but i tested it only on GF 9600 GT which has better D3D
support in wine, than older cards.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #38 from Mirek Slugen   2008-11-07 11:50:03 ---
(In reply to comment #36)
> (In reply to comment #34)
> > If someone else can confirm that the game works with my patch then this bug can
> > be closed as failed.
>
> Wouldn't this mean that someone would need to write something to detect and
> properly report the driver information for different cards? (and, I presume,
> fallback to the current reported info if detection fails)
>
> I would say that this isn't that the game fails to detect the card, it's that
> Wine gives the game the "wrong" information.

I am not expert, but graphic detection shouldn't be based on used driver but on
avalaible Device Caps.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #39 from H. Verbeet   2008-11-07 13:35:20 ---
If the game seriously relies on the driver string, it's utter crap.
Nevertheless, I suppose we could add the driver string to the other card
detection code we already do.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #40 from Alexander Varnin   2008-11-07 13:50:44 ---
Created an attachment (id=17131)
 --> (http://bugs.winehq.org/attachment.cgi?id=17131)
Error log d3d "Unsupported format..."

It fails for me with output, attached here.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #41 from Josko   2008-11-07 15:07:46 ---
Created an attachment (id=17132)
 --> (http://bugs.winehq.org/attachment.cgi?id=17132)
Crash with patch applied

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #42 from Josko   2008-11-07 15:14:33 ---
(In reply to comment #33)
> Created an attachment (id=17130)

--> (http://bugs.winehq.org/attachment.cgi?id=17130) [details]
> Patch for WineD3D to set Driver an Description
>
> Patch for Fallout 3, the game has broken detection of graphic card
> capabalities, wine actualy supports SM2.0b perfectly even SM3.0, but the game
> used only SM2.0 which is broken (not in wine, but in this game).
>
> After apply this patch you should set 2 new registry options in
> Software\Wine\Direct3D:
> "VideoDescription"="NVIDIA GeForce 9600 GT"
> "VideoDriver"="nv4_disp.dll"
>
> VideoDescription - set this option on the same value as the name of your card
> (my is NVIDIA GeForce 9600 GT, but NVIDIA GeForce 7900 GT is tested as working
> too).
> VideoDriver - nv4_disp.dll for all nvidia based cards, ati is not tested

Everything was working fine Intro videos playing, heads visible, but after I
choosed character look Fallout Crashed: 
Attachment #17132
So I tryed to load savegames ffom PyNUX, at first it was working as well but
when I saved game in Megaton and then loaded it again Fallout was crashing
again same way as after character look selection.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #43 from Sarunas Valaskevicius   2008-11-07 16:01:28 ---
having ati 4670.

game is really slow... even on lowest settings..
also, screen flickers a lot. seems it is divided into to equal parts vertically
(from center) and both sides flicker..
after hurting my eyes looking @flickering, it stopped to respond after
character creation (when "I" was rolled out from doctor, when "bumped" into
wall..)

log gives a *lot* of:

fixme:d3d_shader:shader_glsl_load_constantsF >>>>>>>>>>>>>>>>>
GL_INVALID_OPERATION (0x502) from glUniform4fvARB() @ glsl_shader.c / 265
fixme:d3d_shader:shader_glsl_load_constants >>>>>>>>>>>>>>>>>
GL_INVALID_OPERATION (0x502) from glUniform4fvARB @ glsl_shader.c / 445

ghmm... what have I made wrong?..

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #44 from Josko   2008-11-07 18:41:49 ---
(In reply to comment #43)
> having ati 4670.
>
> game is really slow... even on lowest settings..
> also, screen flickers a lot. seems it is divided into to equal parts vertically
> (from center) and both sides flicker..
> after hurting my eyes looking @flickering, it stopped to respond after
> character creation (when "I" was rolled out from doctor, when "bumped" into
> wall..)
>
> log gives a *lot* of:
>
> fixme:d3d_shader:shader_glsl_load_constantsF >>>>>>>>>>>>>>>>>
> GL_INVALID_OPERATION (0x502) from glUniform4fvARB() @ glsl_shader.c / 265
> fixme:d3d_shader:shader_glsl_load_constants >>>>>>>>>>>>>>>>>
> GL_INVALID_OPERATION (0x502) from glUniform4fvARB @ glsl_shader.c / 445
>
> ghmm... what have I made wrong?..

I think that slowness and graphic artifacts are caused by poor ATI drivers in
linux (Try WoW for example - that is OpenGL and you will see if drivers are
good or not), because on my 8800 GT I have playable FPS also on High setting
and under Compiz in 1680x1050 fullscreen. But I have also GL_INVALID_OPERATION
errors soon before game crashes.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #45 from Mirek Slugen   2008-11-07 19:52:59 ---
(In reply to comment #42)
> (In reply to comment #33)
> > Created an attachment (id=17130)

--> (http://bugs.winehq.org/attachment.cgi?id=17130) [details] [details]
> > Patch for WineD3D to set Driver an Description
> >
> > Patch for Fallout 3, the game has broken detection of graphic card
> > capabalities, wine actualy supports SM2.0b perfectly even SM3.0, but the game
> > used only SM2.0 which is broken (not in wine, but in this game).
> >
> > After apply this patch you should set 2 new registry options in
> > Software\Wine\Direct3D:
> > "VideoDescription"="NVIDIA GeForce 9600 GT"
> > "VideoDriver"="nv4_disp.dll"
> >
> > VideoDescription - set this option on the same value as the name of your card
> > (my is NVIDIA GeForce 9600 GT, but NVIDIA GeForce 7900 GT is tested as working
> > too).
> > VideoDriver - nv4_disp.dll for all nvidia based cards, ati is not tested
>
> Everything was working fine Intro videos playing, heads visible, but after I
> choosed character look Fallout Crashed: 
> Attachment #17132 [details]
> So I tryed to load savegames ffom PyNUX, at first it was working as well but
> when I saved game in Megaton and then loaded it again Fallout was crashing
> again same way as after character look selection.

Do you have fbo registry settings?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #46 from Mirek Slugen   2008-11-08 04:36:33 ---
All my Direct3D registry settings:

"DirectDrawRenderer"="gdi"
"OffscreenRenderingMode"="fbo"
"PixelShaderMode"="enabled"
"SoftwareEmulation"="enabled"
"UseGLSL"="enable"
"VertexShaderMode"="hardware"
"VideoDescription"="NVIDIA GeForce 9600 GT"
"VideoDriver"="nv4_disp.dll"
"VideoMemorySize"="512"

Also, you should have latest nVidia stable drivers, latest wine, tested
yesterday with version 1.1.8 and at least GF 6600 or better.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #47 from Sarunas Valaskevicius   2008-11-08 11:58:56 ---
does anyone know how to tell fallout not only card name, but also, that it
*doesnt* have SLI? (ati HD 4670)

because now RendererInfo.txt gives:
SLI mode : yes

and there is very similar bug as in fallout bug list "vista + sli = garbage +
flickering"

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #48 from Josko   2008-11-08 16:24:20 ---
(In reply to comment #46)
> All my Direct3D registry settings:
>
> "DirectDrawRenderer"="gdi"
> "OffscreenRenderingMode"="fbo"
> "PixelShaderMode"="enabled"
> "SoftwareEmulation"="enabled"
> "UseGLSL"="enable"
> "VertexShaderMode"="hardware"
> "VideoDescription"="NVIDIA GeForce 9600 GT"
> "VideoDriver"="nv4_disp.dll"
> "VideoMemorySize"="512"
>
> Also, you should have latest nVidia stable drivers, latest wine, tested
> yesterday with version 1.1.8 and at least GF 6600 or better.

Now I have all settings as you and its fully working, but mouse is leaving game
window in fullscreen even with MouseWarpOverride disabled...

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

nyarlatothep  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #49 from nyarlatothep   2008-11-12 02:30:03 ---
is it just a dll that needs to get patched ?
someone who compiled it could submit it ?
or eventually, could i just get wine source, patch the dll, and stick it into
existing wine install ?

also about registry settings, where do i add this?

"DirectDrawRenderer"="gdi"
"OffscreenRenderingMode"="fbo"
"PixelShaderMode"="enabled"
"SoftwareEmulation"="enabled"
"UseGLSL"="enable"
"VertexShaderMode"="hardware"
"VideoDescription"="NVIDIA GeForce 9600 GT"
"VideoDriver"="nv4_disp.dll"
"VideoMemorySize"="512"

tnx

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #50 from Josko   2008-11-20 12:53:59 ---
Created an attachment (id=17374)
 --> (http://bugs.winehq.org/attachment.cgi?id=17374)
Error message after random freeze

After applying D3D patch and mouse patch towards wine 1.18 (Direct X 9
Installed and all registry settings set) I have Fallout 3 freezeing randomly
with this error message..

Any suggestions?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #51 from Mirek Slugen   2008-11-20 14:44:41 ---
(In reply to comment #50)
> Created an attachment (id=17374)

--> (http://bugs.winehq.org/attachment.cgi?id=17374) [details]
> Error message after random freeze
>
> After applying D3D patch and mouse patch towards wine 1.18 (Direct X 9
> Installed and all registry settings set) I have Fallout 3 freezeing randomly
> with this error message..
>
> Any suggestions?

You should play this game without HDR or BLOOM, and with low texture details.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #52 from Josko   2008-11-20 15:00:45 ---
(In reply to comment #51)
> You should play this game without HDR or BLOOM, and with low texture details.

That's pity HDR and Ultra High settings looks sooo nice, but thank you I'll try
it out without these nice settings... 
And what about czech localization could this cause problems?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #53 from Josko   2008-11-20 15:06:46 ---
(In reply to comment #51)
> You should play this game without HDR or BLOOM, and with low texture details.

Tryed, still freezes sometimes, especialy when exiting/entering buildings.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #54 from Josko   2008-11-20 15:07:12 ---
(In reply to comment #51)
> You should play this game without HDR or BLOOM, and with low texture details.

Tryed, still freezes sometimes, especialy when exiting/entering buildings.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Andrew Fenn  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #55 from Andrew Fenn   2008-11-20 18:57:03 ---
Your freezing could be the game when it's trying to autosave. On windows I get
freezes when saving.

Try turning off autosave and see it that stops the freezing when going in and
out of buildings.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #56 from Josko   2008-11-21 12:27:56 ---
Andrew Fenn:
No it's not a problem with autosaving, because it happends before I press e
wich meas that I actualy don't exit/enter building only go near door.

In my house in megaton every time when I go by door game freeze not only when I
attempt to open them... no matter of that I have ultra high quality or low
quality settings crases at same place.
 I tryed even go backwars to door but when I turned over to open door game
freezed again.  Sound is playing even after freeze wich means robot in my room
is talking, radio is still playing but screen is freezed

I don't know what am I doing wrong. I tryed also to remove .wine directory,
reinstall Fallout 3, install it again, but it's still freezing. 
btw. I have wine 1.18 with mouse and direct3d patch applyed, Ubuntu 8.10,
NVIDIA 8800GT and drivers: 177.80

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Artem Semendyaev  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Luke Bratch  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]     |

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Björn Krombholz  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Will Robertson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

--- Comment #59 from Will Robertson   2009-04-11 20:09:59 ---
Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an
Description for wine 1.1.18". This is a clean request for the exact feature
that this patch is for, to make it easier for devs to find, as well as for
other apps that may have a need to report as related to them.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Will Robertson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

--- Comment #59 from Will Robertson   2009-04-11 20:09:59 ---
Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an
Description for wine 1.1.18". This is a clean request for the exact feature
that this patch is for, to make it easier for devs to find, as well as for
other apps that may have a need to report as related to them.

--- Comment #60 from Jeff Zaroyko   2009-04-11 20:29:18 ---
*** Bug 18011 has been marked as a duplicate of this bug. ***

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Will Robertson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

--- Comment #59 from Will Robertson   2009-04-11 20:09:59 ---
Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an
Description for wine 1.1.18". This is a clean request for the exact feature
that this patch is for, to make it easier for devs to find, as well as for
other apps that may have a need to report as related to them.

--- Comment #60 from Jeff Zaroyko   2009-04-11 20:29:18 ---
*** Bug 18011 has been marked as a duplicate of this bug. ***

--- Comment #61 from John Whitlock   2009-04-12 02:38:46 ---
(In reply to comment #59)

The devs are very aware of this bug, but they've rejected the attached patch. 
They prefer that a good value is automatically picked for the device
description and driver name.  That's completely reasonable, but harder than the
registry override.  I'm working on it, and I'm sad we missed 1.1.19, but I'm
hopeful that this will be fixed in 1.1.20.

If you have a Windows box with Fallout 3 available, I could use some
information.  Please post the first few lines of  (Doc Folder)/My
Games/Fallout3/RendererInfo.txt.  On Wine, they look something like:

Renderer Device Information:
        Direct3D HAL
        Display
        RenderPath                      : BSSM_SV_2

On Windows, they'll look like:
Renderer Device Information:
        NVIDIA GeForce 7600 GT
        nv4_disp.dll
        RenderPath                      : BSSM_SV_2_A

Please include your OS (XP, Vista, etc.)

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Will Robertson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

--- Comment #59 from Will Robertson   2009-04-11 20:09:59 ---
Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an
Description for wine 1.1.18". This is a clean request for the exact feature
that this patch is for, to make it easier for devs to find, as well as for
other apps that may have a need to report as related to them.

--- Comment #60 from Jeff Zaroyko   2009-04-11 20:29:18 ---
*** Bug 18011 has been marked as a duplicate of this bug. ***

--- Comment #61 from John Whitlock   2009-04-12 02:38:46 ---
(In reply to comment #59)

The devs are very aware of this bug, but they've rejected the attached patch. 
They prefer that a good value is automatically picked for the device
description and driver name.  That's completely reasonable, but harder than the
registry override.  I'm working on it, and I'm sad we missed 1.1.19, but I'm
hopeful that this will be fixed in 1.1.20.

If you have a Windows box with Fallout 3 available, I could use some
information.  Please post the first few lines of  (Doc Folder)/My
Games/Fallout3/RendererInfo.txt.  On Wine, they look something like:

Renderer Device Information:
        Direct3D HAL
        Display
        RenderPath                      : BSSM_SV_2

On Windows, they'll look like:
Renderer Device Information:
        NVIDIA GeForce 7600 GT
        nv4_disp.dll
        RenderPath                      : BSSM_SV_2_A

Please include your OS (XP, Vista, etc.)

--- Comment #62 from [e-mail]  2009-04-12 03:20:41 ---
Created an attachment (id=20394)
 --> (http://bugs.winehq.org/attachment.cgi?id=20394)
RendererInfo.txt from Vista SP1

your efforts are very much appreciated. here is my rendererinfo.txt from vista
SP1. hope it can be of use.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Will Robertson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

--- Comment #59 from Will Robertson   2009-04-11 20:09:59 ---
Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an
Description for wine 1.1.18". This is a clean request for the exact feature
that this patch is for, to make it easier for devs to find, as well as for
other apps that may have a need to report as related to them.

--- Comment #60 from Jeff Zaroyko   2009-04-11 20:29:18 ---
*** Bug 18011 has been marked as a duplicate of this bug. ***

--- Comment #61 from John Whitlock   2009-04-12 02:38:46 ---
(In reply to comment #59)

The devs are very aware of this bug, but they've rejected the attached patch. 
They prefer that a good value is automatically picked for the device
description and driver name.  That's completely reasonable, but harder than the
registry override.  I'm working on it, and I'm sad we missed 1.1.19, but I'm
hopeful that this will be fixed in 1.1.20.

If you have a Windows box with Fallout 3 available, I could use some
information.  Please post the first few lines of  (Doc Folder)/My
Games/Fallout3/RendererInfo.txt.  On Wine, they look something like:

Renderer Device Information:
        Direct3D HAL
        Display
        RenderPath                      : BSSM_SV_2

On Windows, they'll look like:
Renderer Device Information:
        NVIDIA GeForce 7600 GT
        nv4_disp.dll
        RenderPath                      : BSSM_SV_2_A

Please include your OS (XP, Vista, etc.)

--- Comment #62 from [e-mail]  2009-04-12 03:20:41 ---
Created an attachment (id=20394)
 --> (http://bugs.winehq.org/attachment.cgi?id=20394)
RendererInfo.txt from Vista SP1

your efforts are very much appreciated. here is my rendererinfo.txt from vista
SP1. hope it can be of use.

--- Comment #63 from [e-mail]  2009-05-02 14:06:58 ---
Created an attachment (id=20871)
 --> (http://bugs.winehq.org/attachment.cgi?id=20871)
GeForce 8800 GTS on WinXP SP03

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Will Robertson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

--- Comment #59 from Will Robertson   2009-04-11 20:09:59 ---
Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an
Description for wine 1.1.18". This is a clean request for the exact feature
that this patch is for, to make it easier for devs to find, as well as for
other apps that may have a need to report as related to them.

--- Comment #60 from Jeff Zaroyko   2009-04-11 20:29:18 ---
*** Bug 18011 has been marked as a duplicate of this bug. ***

--- Comment #61 from John Whitlock   2009-04-12 02:38:46 ---
(In reply to comment #59)

The devs are very aware of this bug, but they've rejected the attached patch. 
They prefer that a good value is automatically picked for the device
description and driver name.  That's completely reasonable, but harder than the
registry override.  I'm working on it, and I'm sad we missed 1.1.19, but I'm
hopeful that this will be fixed in 1.1.20.

If you have a Windows box with Fallout 3 available, I could use some
information.  Please post the first few lines of  (Doc Folder)/My
Games/Fallout3/RendererInfo.txt.  On Wine, they look something like:

Renderer Device Information:
        Direct3D HAL
        Display
        RenderPath                      : BSSM_SV_2

On Windows, they'll look like:
Renderer Device Information:
        NVIDIA GeForce 7600 GT
        nv4_disp.dll
        RenderPath                      : BSSM_SV_2_A

Please include your OS (XP, Vista, etc.)

--- Comment #62 from [e-mail]  2009-04-12 03:20:41 ---
Created an attachment (id=20394)
 --> (http://bugs.winehq.org/attachment.cgi?id=20394)
RendererInfo.txt from Vista SP1

your efforts are very much appreciated. here is my rendererinfo.txt from vista
SP1. hope it can be of use.

--- Comment #63 from [e-mail]  2009-05-02 14:06:58 ---
Created an attachment (id=20871)
 --> (http://bugs.winehq.org/attachment.cgi?id=20871)
GeForce 8800 GTS on WinXP SP03

--- Comment #64 from [e-mail]  2009-05-02 14:34:06 ---
(In reply to comment #61)
> The devs are very aware of this bug, but they've rejected the attached patch. 
> They prefer that a good value is automatically picked for the device
> description and driver name.

Creating a situation where you must upgrade or patch/recompile wine simply to
update it with a currently unreleased card description is foolish. This does
not necessarily mean other changes to wine, for example new low/mid-class cards
could bring new combinations of existing capabilities. Since they obviously DO
rely on these magic strings, the best solution would be:

1. Check for manual overrides (your patch)
2. If empty, pick a good value automatically
3. Fallback to current dummy values

I realize they're pushing to make you write point 2. as well, but there's
absolutely no reason to reject having a manual failsafe, nor implementing that
one first before going for the fancy autodetection. Setting it manually could
be the testing method to update the automatic code with new cards. What am I
missing here?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Will Robertson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

--- Comment #59 from Will Robertson   2009-04-11 20:09:59 ---
Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an
Description for wine 1.1.18". This is a clean request for the exact feature
that this patch is for, to make it easier for devs to find, as well as for
other apps that may have a need to report as related to them.

--- Comment #60 from Jeff Zaroyko   2009-04-11 20:29:18 ---
*** Bug 18011 has been marked as a duplicate of this bug. ***

--- Comment #61 from John Whitlock   2009-04-12 02:38:46 ---
(In reply to comment #59)

The devs are very aware of this bug, but they've rejected the attached patch. 
They prefer that a good value is automatically picked for the device
description and driver name.  That's completely reasonable, but harder than the
registry override.  I'm working on it, and I'm sad we missed 1.1.19, but I'm
hopeful that this will be fixed in 1.1.20.

If you have a Windows box with Fallout 3 available, I could use some
information.  Please post the first few lines of  (Doc Folder)/My
Games/Fallout3/RendererInfo.txt.  On Wine, they look something like:

Renderer Device Information:
        Direct3D HAL
        Display
        RenderPath                      : BSSM_SV_2

On Windows, they'll look like:
Renderer Device Information:
        NVIDIA GeForce 7600 GT
        nv4_disp.dll
        RenderPath                      : BSSM_SV_2_A

Please include your OS (XP, Vista, etc.)

--- Comment #62 from [e-mail]  2009-04-12 03:20:41 ---
Created an attachment (id=20394)
 --> (http://bugs.winehq.org/attachment.cgi?id=20394)
RendererInfo.txt from Vista SP1

your efforts are very much appreciated. here is my rendererinfo.txt from vista
SP1. hope it can be of use.

--- Comment #63 from [e-mail]  2009-05-02 14:06:58 ---
Created an attachment (id=20871)
 --> (http://bugs.winehq.org/attachment.cgi?id=20871)
GeForce 8800 GTS on WinXP SP03

--- Comment #64 from [e-mail]  2009-05-02 14:34:06 ---
(In reply to comment #61)
> The devs are very aware of this bug, but they've rejected the attached patch. 
> They prefer that a good value is automatically picked for the device
> description and driver name.

Creating a situation where you must upgrade or patch/recompile wine simply to
update it with a currently unreleased card description is foolish. This does
not necessarily mean other changes to wine, for example new low/mid-class cards
could bring new combinations of existing capabilities. Since they obviously DO
rely on these magic strings, the best solution would be:

1. Check for manual overrides (your patch)
2. If empty, pick a good value automatically
3. Fallback to current dummy values

I realize they're pushing to make you write point 2. as well, but there's
absolutely no reason to reject having a manual failsafe, nor implementing that
one first before going for the fancy autodetection. Setting it manually could
be the testing method to update the automatic code with new cards. What am I
missing here?

--- Comment #65 from Jeff Zaroyko   2009-05-05 18:19:29 ---
*** Bug 18358 has been marked as a duplicate of this bug. ***

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Will Robertson  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Dario Corti  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Nicky  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Steve Dougherty  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #57 from Jeff Zaroyko   2009-03-22 21:47:48 ---
*** Bug 17827 has been marked as a duplicate of this bug. ***

--- Comment #58 from Wouter de Geus   2009-04-06 10:00:17 ---
Created an attachment (id=20312)
 --> (http://bugs.winehq.org/attachment.cgi?id=20312)
Updated Patch for WineD3D to set Driver an Description for wine 1.1.18

Since the "Patch for WineD3D to set Driver an Description" patch didn't apply
anymore for the -git version, I updated it so it works again.

--- Comment #59 from Will Robertson   2009-04-11 20:09:59 ---
Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an
Description for wine 1.1.18". This is a clean request for the exact feature
that this patch is for, to make it easier for devs to find, as well as for
other apps that may have a need to report as related to them.

--- Comment #60 from Jeff Zaroyko   2009-04-11 20:29:18 ---
*** Bug 18011 has been marked as a duplicate of this bug. ***

--- Comment #61 from John Whitlock   2009-04-12 02:38:46 ---
(In reply to comment #59)

The devs are very aware of this bug, but they've rejected the attached patch. 
They prefer that a good value is automatically picked for the device
description and driver name.  That's completely reasonable, but harder than the
registry override.  I'm working on it, and I'm sad we missed 1.1.19, but I'm
hopeful that this will be fixed in 1.1.20.

If you have a Windows box with Fallout 3 available, I could use some
information.  Please post the first few lines of  (Doc Folder)/My
Games/Fallout3/RendererInfo.txt.  On Wine, they look something like:

Renderer Device Information:
        Direct3D HAL
        Display
        RenderPath                      : BSSM_SV_2

On Windows, they'll look like:
Renderer Device Information:
        NVIDIA GeForce 7600 GT
        nv4_disp.dll
        RenderPath                      : BSSM_SV_2_A

Please include your OS (XP, Vista, etc.)

--- Comment #62 from [e-mail]  2009-04-12 03:20:41 ---
Created an attachment (id=20394)
 --> (http://bugs.winehq.org/attachment.cgi?id=20394)
RendererInfo.txt from Vista SP1

your efforts are very much appreciated. here is my rendererinfo.txt from vista
SP1. hope it can be of use.

--- Comment #63 from [e-mail]  2009-05-02 14:06:58 ---
Created an attachment (id=20871)
 --> (http://bugs.winehq.org/attachment.cgi?id=20871)
GeForce 8800 GTS on WinXP SP03

--- Comment #64 from [e-mail]  2009-05-02 14:34:06 ---
(In reply to comment #61)
> The devs are very aware of this bug, but they've rejected the attached patch. 
> They prefer that a good value is automatically picked for the device
> description and driver name.

Creating a situation where you must upgrade or patch/recompile wine simply to
update it with a currently unreleased card description is foolish. This does
not necessarily mean other changes to wine, for example new low/mid-class cards
could bring new combinations of existing capabilities. Since they obviously DO
rely on these magic strings, the best solution would be:

1. Check for manual overrides (your patch)
2. If empty, pick a good value automatically
3. Fallback to current dummy values

I realize they're pushing to make you write point 2. as well, but there's
absolutely no reason to reject having a manual failsafe, nor implementing that
one first before going for the fancy autodetection. Setting it manually could
be the testing method to update the automatic code with new cards. What am I
missing here?

--- Comment #65 from Jeff Zaroyko   2009-05-05 18:19:29 ---
*** Bug 18358 has been marked as a duplicate of this bug. ***

--- Comment #66 from Nicky   2009-05-14 15:07:29 ---
Shouldn't wine 1.1.20 fix this? My video card, at least, is correctly reported
now (my system ain't powerful enough to run that game, though...)

--- Comment #67 from Jeff Zaroyko   2009-05-14 19:25:01 ---
*** Bug 9202 has been marked as a duplicate of this bug. ***

--- Comment #68 from Jeff Zaroyko   2009-05-14 19:26:26 ---
(In reply to comment #66)
> Shouldn't wine 1.1.20 fix this? My video card, at least, is correctly reported
> now (my system ain't powerful enough to run that game, though...)

No, you might be referring to a different problem, Wine still reports Direct3D
HAL instead of the real information as of Wine 1.1.21-138-gaea6418

--- Comment #69 from Steve Dougherty   2009-05-15 05:53:21 ---
Renderer Device Information:
    ATI RADEON XPRESS 200 Series  
    ati2dvag.dll
    RenderPath                 : BSSM_SV_2_B96

This is on Windows XP SP 3. I now have an NVidia GeForce 9500, but for some
reason this file hasn't changed yet.

--- Comment #70 from Nicky   2009-05-15 09:37:02 ---
(In reply to comment #68)
> (In reply to comment #66)
> > Shouldn't wine 1.1.20 fix this? My video card, at least, is correctly reported
> > now (my system ain't powerful enough to run that game, though...)
>
> No, you might be referring to a different problem, Wine still reports Direct3D
> HAL instead of the real information as of Wine 1.1.21-138-gaea6418

I'm talking about this commit
http://source.winehq.org/git/wine.git/?a=commit;h=f2e2e3e49947490368900ef06a...
It makes my GeForceFX 5200 reported as such (at least by MaxPayne and MaxPayne
2)
http://i42.tinypic.com/2qvqas7.png - vanilla wine.

--- Comment #71 from Tymoteusz Paul   2009-06-03 04:03:45 ---
Created an attachment (id=21512)
 --> (http://bugs.winehq.org/attachment.cgi?id=21512)
Console output

With latest git wine using any of available patches does not solve the issue
and game still crashes after trying to start new game.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #72 from Henri Verbeet   2009-06-03 04:14:16 ---
We currently set the driver description, but not the driver name.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #73 from Jeff Zaroyko   2009-06-09 05:20:11 ---
*** Bug 18857 has been marked as a duplicate of this bug. ***

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #74 from Albert Lee   2009-06-16 16:17:09 ---
Created an attachment (id=21830)
 --> (http://bugs.winehq.org/attachment.cgi?id=21830)
Report typical Windows driver name for supported cards

This makes wined3d report the appropriate Windows driver name for the currently
supported NVIDIA and ATI cards. If you have a supported device, this makes the
workaround in attachment 20312 unnecessary. This also fixes a regression in the
recent driver description commit where the description is empty string for
unknown devices instead of "Display".

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Albert Lee  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #75 from Albert Lee   2009-06-18 03:14:53 ---
Thunderbird says he's working on reconciling the current tables with the fact
that the driver names/versions may need to be reported differently when winver
is set to WinXP or Vista.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

DL  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #76 from DL   2009-08-02 03:55:46 ---
I think the driver version needs to be reported as well (nv4_disp.dll for
nvidia cards), as Fallout 3 still crashes without the description patch, and
shadows under Oblivion still don't work.Unless the description patch is doing
something else additionally.

--- Comment #77 from Austin English   2009-10-04 21:16:20 ---
*** Bug 19275 has been marked as a duplicate of this bug. ***

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #78 from Austin English   2009-10-08 01:59:12 ---
(In reply to comment #76)
> I think the driver version needs to be reported as well (nv4_disp.dll for
> nvidia cards), as Fallout 3 still crashes without the description patch, and
> shadows under Oblivion still don't work.Unless the description patch is doing
> something else additionally.

Definitely still the case in 1.1.30. Fallout3 crashes unless
http://bugs.winehq.org/attachment.cgi?id=21830 is used, along with the
nv4_disp.dll registry entry.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20312|0                           |1
        is obsolete|                            |

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Federico Fissore  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #79 from Federico Fissore   2009-10-19 04:08:48 ---
still broken in 1.1.31

has anyone an updated patch?

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #80 from Federico Fissore   2009-10-19 08:09:53 ---
Created an attachment (id=24230)
 --> (http://bugs.winehq.org/attachment.cgi?id=24230)
1.1.31 patch? uhmm

I've tried to port the patch to version 1.1.31 but Fallout keeps crashing

I've skipped the first part of the patch, since I can't recognize the code it's
patching

Please have a look at it

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #81 from Thomas J. Moore   2009-10-22 21:39:21 ---
Created an attachment (id=24288)
 --> (http://bugs.winehq.org/attachment.cgi?id=24288)
Add nvidia/ati driver name

#80:  The parts you removed are the most important parts.

I've attached a slightly different take on this:  since there are only 2 driver
names, it chooses the name based on the description.  That should allow this
patch to work even when the table changes in future revisions.  It works for me
(ATI) in Oblivion and Fallout 3.

I'd actually prefer a combination of the first proposed patch and this one. 
That way you get autodetection, but also in case of games that require specific
cards, you can fake it.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Thomas J. Moore  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Thomas J. Moore  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #24288|0                           |1
        is obsolete|                            |

--- Comment #82 from Thomas J. Moore   2009-10-22 21:59:47 ---
Created an attachment (id=24289)
 --> (http://bugs.winehq.org/attachment.cgi?id=24289)
Add nvidia/ati driver name

Sent the wrong version.  Same patch, but relative to top dir + 1 this time.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #83 from Federico Fissore   2009-10-26 04:05:59 ---
working great here with wine 1.1.31 patched on gentoo linux amd64/nvidia
GeForce 8600M GS

sometimes the game "can't keep pace": I mean things like the pipboy not
displaying anything, or the VATS not showing targets or the screen flashing
happen. Don't know if it's game bug or whatever. Anyway, just restart it

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #84 from Henri Verbeet   2009-10-27 09:51:47 ---
How does this work with current git? 13c4fe72ad1e26eb492b10d87ac80f0363fffc2d
should help.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #85 from Austin English   2009-10-28 01:28:30 ---
(In reply to comment #84)
> How does this work with current git? 13c4fe72ad1e26eb492b10d87ac80f0363fffc2d
> should help.

Yes, seems fine. Before, I was using 1.1.30-287-g3c98992 along with
http://bugs.winehq.org/attachment.cgi?id=24289. I just changed my fallout
launch script to use the system (vanilla) wine, and fallout launches. I haven't
played enough to see if the random blank pipboys/other errors are fixed, but
the initial crash on launch is definitely fixed.

Thanks Henri!

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

--- Comment #86 from Austin English   2009-10-28 02:53:26 ---
Still get some errors when playing. Terminal shows:
fixme:d3d_texture:texture_init Failed to create surface 0x69f85b48, hr
0x8876017c
err:d3d9:device_parent_CreateSurface (0x178174) CreateSurface failed, returning
0x8876017c
fixme:d3d_texture:texture_init Failed to create surface 0x69f85b48, hr
0x8876017c
err:d3d9:device_parent_CreateSurface (0x178174) CreateSurface failed, returning
0x8876017c
fixme:d3d_texture:texture_init Failed to create surface 0x69f85b48, hr
0x8876017c
err:d3d9:device_parent_CreateSurface (0x178174) CreateSurface failed, returning
0x8876017c
fixme:d3d_texture:texture_init Failed to create surface 0x69f85b48, hr
0x8876017c
err:d3d9:device_parent_CreateSurface (0x178174) CreateSurface failed, returning
0x8876017c

Mostly occurs when changing locations. The game will still run, but your screen
no longer shows health/ammo/gun condition, and appears much brighter/off color.
If you shift your view, health/ammo/etc. return, but only when looking high
up/down. Reloading the game fixes the problem.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #87 from Austin English   2009-10-28 19:34:00 ---
Since it no longer crashes, I'm marking this fixed. The other problems should
be a separate bug.

[Bug 15839] Games for Windows Live fails to initialize, resulting Fallout 3 crash

http://bugs.winehq.org/show_bug.cgi?id=15839

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #88 from Alexandre Julliard   2009-11-13 12:43:21 ---
Closing bugs fixed in 1.1.33.

[Bug 15839] Microsoft Games for Windows Live (GFWL) 1.2.x fails to initialize, resulting Fallout 3 crash

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=15839

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                URL|http://www.gamesforwindows. |https://web.archive.org/web
                   |com                         |/20111126153535/http://down
                   |                            |load.microsoft.com/download
                   |                            |/5/0/5/505dd51c-ba8d-4569-a
                   |                            |1ec-40cf2c4ef331/XLiveRedis
                   |                            |t01.02.0241.00.msi
           Keywords|                            |download
            Summary|Games for Windows Live      |Microsoft Games for Windows
                   |fails to initialize,        |Live (GFWL) 1.2.x fails to
                   |resulting Fallout 3 crash   |initialize, resulting
                   |                            |Fallout 3 crash