wine users - May 2011 - Crysis first level load crash.

Hi 
I more or less followed the AppDB how to
(http://appdb.winehq.org/objectManager.php?sClass=version&iId=10107&iTestingId=59999)
for Crysis.  Copying in the DLLs failed to solve the problem, so I rather
installed directX9 from the latest winetricks as suggested in the other Crysis
version
(http://appdb.winehq.org/objectManager.php?sClass=version&iId=13890&iTestingId=31830&bShowAll=true)
on AppDB.

Unfortunately, the games still doesn't load the first level successfully. 
Main menu works.  The movie after the Loading of the game works (After you start
single player game). After that wine crashes with the log output:


Code:
fixme:cursor:SetSystemCursor (0x1008e,00007f04),stub!
fixme:cursor:SetSystemCursor (0x10092,00007f02),stub!
fixme:process:GetLogicalProcessorInformation ((nil),0x515ad4): stub
fixme:ntdll:NtQueryInformationProcess (process=0xffffffff) Unimplemented
information class: ProcessDeviceMap
fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_HANDLE_INFORMATION
fixme:ntdll:NtQueryObject Unsupported information class 3
err:rpc:I_RpcGetBuffer no binding
fixme:win:EnumDisplayDevicesW ((null),0,0x52dce8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x52dc14,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x52dd0c,0x00000000), stub!
fixme:d3d:swapchain_init Add OpenGL context recreation support to
context_validate_onscreen_formats
fixme:d3d:swapchain_init Add OpenGL context recreation support to
context_validate_onscreen_formats
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in
the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in
the format lookup table
fixme:win:EnumDisplayDevicesW ((null),0,0x52d9a0,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 0x434f5441 (as fourcc: ATOC)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x434f5441) in
the format lookup table
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0xa0c77d0,0xa0c76d0): stub
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0xa0c7890,0xa0c7790): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Pro Audio",0x52df74): stub
fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS)
fixme:system:SystemParametersInfoW Unimplemented action: 53 (SPI_SETTOGGLEKEYS)
fixme:system:SystemParametersInfoW Unimplemented action: 51 (SPI_SETFILTERKEYS)
fixme:d3d:state_zfunc D3DCMP_NOTEQUAL and D3DCMP_EQUAL do not work correctly
yet.
fixme:faultrep:ReportFault 0x52dbc8 0x0 stub
err:mmtime:TIME_MMTimeStop Timer still active?!
err:d3d:wined3d_wndproc Window 0x40022 is not registered with wined3d.




On wine-1.3.18 on Gentoo. No patches applied to wine.
Nvidia drivers 270.41.03
It is the "EA value games" edition of Crysis.

Solved it.
Applied the patch http://bugs2.winehq.org/attachment.cgi?id=27310 to wine
1.3.18. And with MouseWarpOverride=force in the registry
(http://wiki.winehq.org/UsefulRegistryKeys) it is nice and playable.

Also reading this comment (http://bugs.winehq.org/show_bug.cgi?id=18799#c37)
helped me understand it is essentially a memory bug in Crysis.

On 5/15/11 12:44 PM, drbergie wrote:
> Solved it.
> Applied the patch http://bugs2.winehq.org/attachment.cgi?id=27310 to wine
1.3.18. And with MouseWarpOverride=force in the registry
(http://wiki.winehq.org/UsefulRegistryKeys) it is nice and playable.
>
> Also reading this comment
(http://bugs.winehq.org/show_bug.cgi?id=18799#c37) helped me understand it is
essentially a memory bug in Crysis.
>
Glad you solved it.  Now, can you create an entry in the Applications 
Database for this program and your workaround.  Also, please update the 
bug report to let the developers know that another program is affected 
by these bugs.

James McKenzie

Thanks mate. Been looking for someone to check for an up-to-date solution (heh,
heh not that I'm lazy).

I'll test this and cross post on the Ubuntu forums today (someone was asking
there).

I'll test out on a WINE version that actually works (i.e. not 1.3.20!!) and
confirm on AppDB.

Bob

drbergie wrote:
> Solved it.
> Applied the patch http://bugs2.winehq.org/attachment.cgi?id=27310 to wine
1.3.18. And with MouseWarpOverride=force in the registry
(http://wiki.winehq.org/UsefulRegistryKeys) it is nice and playable.
> 
> Also reading this comment
(http://bugs.winehq.org/show_bug.cgi?id=18799#c37) helped me understand it is
essentially a memory bug in Crysis.

Hi all,

Just a heads-up to say the latest WINE Git master compiled, with the memory-leak
patch applied, no longer needs the MouseWarpOverride settings to be changed from
default. The mouse cursor works perfectly in the main menus and in game you can
turn >360 degrees.

Looking sweet!  8) 

Bob