http://bugs.winehq.org/show_bug.cgi?id=14806
Summary: Devil May Cry 4 Does not Load/Initilize Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt AssignedTo: wine-bugs@winehq.org ReportedBy: thebozo1@hotmail.com
Created an attachment (id=15357) --> (http://bugs.winehq.org/attachment.cgi?id=15357) Devil May Cry 4 Console Output
After copying the required dll's to run Devil May Cry 4 (WMVCORE.dll & XINPUT1_3.dll) The game still does not Initilize! No black screen, no feedback at all!
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #1 from Lei Zhang thestig@google.com 2008-08-11 19:58:06 --- Does native msvcrt.dll help?
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #2 from Clerc Mathias tlarhices@gmail.com 2008-08-14 18:24:42 --- Created an attachment (id=15417) --> (http://bugs.winehq.org/attachment.cgi?id=15417) Console output for the new crash
http://bugs.winehq.org/show_bug.cgi?id=14806
Clerc Mathias tlarhices@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tlarhices@gmail.com
--- Comment #3 from Clerc Mathias tlarhices@gmail.com 2008-08-14 18:25:26 --- I have been able to 'start' the game with WMVCORE.dll, WMASF.DLL and XINPUT1_3.DLL. A black screen will show up with an error saying :
DDERR_OUTOFVIDEOMEMORY : IRender->getDevice()->CreateTexture(mSurfaceSize.w,mSurfaceSize.h, level,usage,(XFFORMAT)fmt,pool,&ptex,NULL)
The program will then go back to the desktop.
The log correspond to this attempt.
http://bugs.winehq.org/show_bug.cgi?id=14806
Andrew Fenn andrewfenn@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andrewfenn@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #4 from joaopa jeremielapuree@yahoo.fr 2009-01-08 01:07:32 --- Mathias, Can you try to incresase the amount of video memory with regedit to see if it fixes your crash?
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #5 from Clerc Mathias tlarhices@gmail.com 2009-01-08 05:03:22 --- Created an attachment (id=18578) --> (http://bugs.winehq.org/attachment.cgi?id=18578) Console output with wine-1.1.12-253-g8ca1ca2
In order to start I had to install a few more dlls than before and the output is different.
The repetitions at the end of the log were cut, I also had to kill the game as it was just showing a black screen for a long time.
The following line is repeated indefinitely (seems so at least) : err:d3d:IWineD3DDeviceImpl_SetTexture Current stage overflows textures array (stage 256)
And from time to time those 2 lines shows up: fixme:xinput:XInputSetState (0 0x32d808) Stub! fixme:xinput:XInputSetState (1 0x32d808) Stub!
To install it, you will need the xinput dll, I did it with winetricks directx9. And also : wmvcore.dll, wmasf.dll, drmclient.dll and wmidx.dll, I took them from the same Xp installation.
Changing video memory size does nothing to it.
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #6 from Andrew Fenn andrewfenn@gmail.com 2009-01-08 07:25:30 --- You don't need the native xinput.dll what it is doing here in wine's implementation is telling the game that you have no joysticks connected. From your output I can see that xinput hasn't got anything to do with your problem launching the game.
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #7 from Clerc Mathias tlarhices@gmail.com 2009-01-08 08:26:26 --- Created an attachment (id=18581) --> (http://bugs.winehq.org/attachment.cgi?id=18581) Console output with wine-1.1.12-253-g8ca1ca2
Andrew pointed out that XInput dll is now useless to start the game.
So I did a new log with a clean wine prefix, same dlls but without "winetricks directx9" this time (and so without installing an xinput dll other than the one from wine)
Still the same problem (black screen instead of the game) and approximately the same terminal output.
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #8 from zanko@daemontux.org 2009-06-05 19:27:34 --- Created an attachment (id=21586) --> (http://bugs.winehq.org/attachment.cgi?id=21586) Devil May Cry 4 output on wine-1.1.23
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #9 from zanko@daemontux.org 2009-06-05 19:29:59 --- (From update of attachment 21586) Same problem for me, with mostly similar output.
Joaopa, where is located the key containing the amount of video memory in regedit ?
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #10 from Vitaliy Margolen vitaliy@kievinfo.com 2009-06-05 21:22:11 --- Look for VideoMemorySize here: http://wiki.winehq.org/UsefulRegistryKeys
http://bugs.winehq.org/show_bug.cgi?id=14806
zanko@daemontux.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zanko@daemontux.org
--- Comment #11 from zanko@daemontux.org 2009-06-07 13:32:05 --- Changing VideoMemorySize doesn't seems to do anything behave differently, the output is still the same.
http://bugs.winehq.org/show_bug.cgi?id=14806
Jari Vetoniemi mailRoxas@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mailRoxas@gmail.com
--- Comment #12 from Jari Vetoniemi mailRoxas@gmail.com 2009-07-19 16:12:34 --- I can confirm, same repeated output here.
Wine 1.1.26 Nvidia 8600 GT
http://bugs.winehq.org/show_bug.cgi?id=14806
Warren Dumortier nwarrenfl@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nwarrenfl@gmail.com
--- Comment #13 from Warren Dumortier nwarrenfl@gmail.com 2009-11-28 09:01:27 --- Still present in Wine 1.1.33, i can see following output:
warren@kubuntu-desktop:~$ fixme:thread:SetThreadIdealProcessor (0x98): stub fixme:d3d9:D3DPERF_GetStatus (void) : stub fixme:win:EnumDisplayDevicesW ((null),0,0x33cd84,0x00000000), stub! fixme:d3d:debug_d3dformat Unrecognized 1112945234 (as fourcc: R2VB) WINED3DFORMAT! fixme:d3d:getFormatDescEntry Can't find format unrecognized(1112945234) in the format lookup table fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1aa530,0x1aa430): stub fixme:system:SystemParametersInfoW Unimplemented action: 94 (SPI_GETMOUSETRAILS) 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:system:SystemParametersInfoW Unimplemented action: 93 (SPI_SETMOUSETRAILS) fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface
Is there anything i can do to help developers?
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #14 from Warren Dumortier nwarrenfl@gmail.com 2009-12-27 14:15:15 --- This bug is fixed since Wine 1.1.36 (or maybe 1.1.34, not sure).
For people still having this problem, this is probably because the no-cd crack you used to get it running isn't working. As informative purposes, the no-cd crack present on razor-releases didn't seem to work, i tried another no-cd crack for version 1.0 and it worked without any problems.
Also, i think the original bug report is partly due to a not working crack, as the non-working crack on my side had the same behavior as reported here.
The xinput dll isn't needed anymore, however wmp9 is still needed to get it running.
This bug can probably be set as fixed?
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #15 from Warren Dumortier nwarrenfl@gmail.com 2009-12-27 14:16:24 --- (In reply to comment #14)
This bug is fixed since Wine 1.1.36 (or maybe 1.1.34, not sure).
For people still having this problem, this is probably because the no-cd crack you used to get it running isn't working. As informative purposes, the no-cd crack present on razor-releases didn't seem to work, i tried another no-cd crack for version 1.0 and it worked without any problems.
Also, i think the original bug report is partly due to a not working crack, as the non-working crack on my side had the same behavior as reported here.
The xinput dll isn't needed anymore, however wmp9 is still needed to get it running.
This bug can probably be set as fixed?
Sorry meant fixed since Wine 1.1.35.
http://bugs.winehq.org/show_bug.cgi?id=14806
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #16 from Dmitry Timoshkov dmitry@codeweavers.com 2009-12-27 23:37:14 --- Reported fixed.
http://bugs.winehq.org/show_bug.cgi?id=14806
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #17 from Jeff Zaroyko jeffz@jeffz.name 2010-01-09 04:52:46 --- Closing bugs fixed in 1.1.36.
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #18 from zanko@daemontux.org 2010-01-09 09:30:11 --- @Warren Dumortier: Is there anything special you did to make it work ? I still have the same problem with wine 1.1.36, a clean wineprefix, wmp9 and I tried different no-cd cracks.
http://bugs.winehq.org/show_bug.cgi?id=14806
--- Comment #19 from Warren Dumortier nwarrenfl@gmail.com 2010-01-09 10:08:10 --- I had to try several cracks before finding one which worked.
-
wine-bugs＠winehq.org