http://bugs.winehq.org/show_bug.cgi?id=32789
Bug #: 32789 Summary: World of Tanks: crash in "sniper mode" Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: n296869@rtrtr.com Classification: Unclassified
Created attachment 43300 --> http://bugs.winehq.org/attachment.cgi?id=43300 stdout & stderr from game launch to crash (without install)
Wine version: wine-1.5.22-36-g99c1b55 WoT version: v.0.8.3 #364 (EU Version) NVIDIA closed source driver version: 313.18
Installer can be downloaded from: http://dl.wargaming.net/wot/eu/files/WoT_internet_install_eu.exe
WoT crashes when in game mode, and completly zoomed into "sniper mode" (right shift key or mousewheel until zoom is at maximum level)
WoT was installed with same version of wine using:
# winecfg (to create .wine directory) -> Pressed "ok" without changes # winetricks d3dx9 d3dx9_43 vcrun2008 msxml3 wininet ie7 # wine WoT_internet_install_eu.exe
Closed launcher. Then game was started using: # cd ~/.wine/drive_c/Games/World_of_Tanks # wine WorldOfTanks.exe
login, start battle using normal tank (no artillery), switch to sniper zoom level, move around a bit or fire -> crash
http://bugs.winehq.org/show_bug.cgi?id=32789
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #43300|log |log.txt filename| | Attachment #43300|application/octet-stream |text/plain mime type| |
--- Comment #1 from Austin English austinenglish@gmail.com 2013-01-22 20:14:05 CST --- Comment on attachment 43300 --> http://bugs.winehq.org/attachment.cgi?id=43300 stdout & stderr from game launch to crash (without install)
Please use .txt in the future.
http://bugs.winehq.org/show_bug.cgi?id=32789
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com Version|unspecified |1.5.22
--- Comment #2 from Dan Kegel dank@kegel.com 2013-01-22 22:00:01 CST --- The log has a few shader compiler errors early on:
fixme:d3dcompiler:D3DCompile data 0x12625dd8, data_size 1427, filename "memory", defines 0xd955b98, include 0x32f028, entrypoint (null), target "__fx_2_0__", sflags 0x20000, eflags 0, shader 0xd960310, error_messages 0x32f244 stub! err:d3dcompiler:wpp_lookup_mem Parent include file missing
so although you did 'winetricks d3dx9', you're still using builting d3dcompiler.
Then towards the end, it says:
err:d3d:resource_init Out of adapter memory fixme:d3d_texture:texture_init Failed to create surface 0x1711c018, hr 0x8876017c wine: Unhandled page fault on read access to 0x00000008 at address 0x7dee6e77 (thread 002d), starting debugger... Backtrace: =>0 0x7dee6e77 in d3d9 (+0x16e77) (0x0822e7a0) 1 0x00660d6d in worldoftanks (+0x260d6c) (0x1e9db990)
What does lspci | grep -i vga say?
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #3 from whatbug n296869@rtrtr.com 2013-01-23 15:56:28 CST --- it says "01:00.0 VGA compatible controller: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1)"
Could it be my card is too weak? I'm also running this game on a dual head setup.
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #4 from Dan Kegel dank@kegel.com 2013-01-23 16:00:39 CST --- What model is your graphics card? How much RAM does it have?
http://worldoftanks.com/game/guide/en/general/frequently_asked_questions#a2 makes it sound like 256MB might let you scrape by, but it might not really be quite enough.
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #5 from whatbug n296869@rtrtr.com 2013-01-23 16:15:43 CST --- # lspci -v -s 01:00.0 01:00.0 VGA compatible controller: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) (prog-if 00 [VGA controller]) Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fd000000 (32-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at fa000000 (64-bit, non-prefetchable) [size=32M] I/O ports at 9c00 [size=128] [virtual] Expansion ROM at fe780000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nvidia Kernel modules: nvidia
yeah, it's 256M but, as said, i'm running a dual head X server, so this might be the problem. Anyway I wouldn't expect it to crash that miserably :) I think that's the reason for the crash, so this bug could be closed unless there are tricks to save GPU memory that I could try.
thank you very much for the help
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #6 from whatbug n296869@rtrtr.com 2013-01-23 16:34:29 CST --- # lspci -v -s 01:00.0 01:00.0 VGA compatible controller: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) (prog-if 00 [VGA controller]) Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fd000000 (32-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at fa000000 (64-bit, non-prefetchable) [size=32M] I/O ports at 9c00 [size=128] [virtual] Expansion ROM at fe780000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nvidia Kernel modules: nvidia
yeah, it's 256M but, as said, i'm running a dual head X server, so this might be the problem. Anyway I wouldn't expect it to crash that miserably :) I think that's the reason for the crash, so this bug could be closed unless there are tricks to save GPU memory that I could try.
thank you very much for the help
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #7 from whatbug n296869@rtrtr.com 2013-01-23 16:35:36 CST --- i turned down all graphic settings and the crash now doesn't occur that often but still occurs. I also found these: https://support.worldoftanks.com/index.php?/Knowledgebase/Article/View/32
Are there ways to adapt those suggestions to wine?
http://bugs.winehq.org/show_bug.cgi?id=32789
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #8 from Dan Kegel dank@kegel.com 2013-01-23 16:40:55 CST --- That page refers to a memory leak, and turning on 3GB addressing. You could try marking the app as needing large address space. See e.g. http://www.techpowerup.com/forums/showthread.php?t=112556
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #9 from Rico kgbricola@web.de 2013-01-24 03:00:04 CST --- Well err:d3d:resource_init Out of adapter memory sounds like there is not enough video memory. And indeed, the minimum graphics memory for the game is 256MB.
You may have more luck by setting VideoMemorySize to a bigger value (see http://wiki.winehq.org/UsefulRegistryKeys). I'm not sure how much video ram is detected by wine, but it looks like it is 128MB (a WINEDEBUG=+d3d log should show it.
I think these have nothing to do with the suggestions for the 3GB switch!
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #10 from Henri Verbeet hverbeet@gmail.com 2013-01-24 03:57:04 CST --- (In reply to comment #9)
You may have more luck by setting VideoMemorySize to a bigger value (see http://wiki.winehq.org/UsefulRegistryKeys). I'm not sure how much video ram is detected by wine, but it looks like it is 128MB (a WINEDEBUG=+d3d log should show it.
Yeah, just bump VideoMemorySize. WoT uses d3d9ex, and I suspect it has "virtualized" video memory like d3d10 and GL, instead of the scheme d3d9 and earlier use where resource allocation just fails once VRAM is full. The way resets work in d3d9ex is a pretty big hint in that direction.
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #11 from Dan Kegel dank@kegel.com 2013-01-24 06:16:48 CST --- Is it really ok to bump VideoMemorySize higher than the physical video memory size on the card?
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #12 from Henri Verbeet hverbeet@gmail.com 2013-01-24 06:19:10 CST --- It is here.
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #13 from Dan Kegel dank@kegel.com 2013-01-24 06:36:09 CST --- That sounds like a tidbit that belongs in the wiki (possibly in http://wiki.winehq.org/UsefulRegistryKeys ).
http://bugs.winehq.org/show_bug.cgi?id=32789
--- Comment #14 from whatbug n296869@rtrtr.com 2013-01-24 15:47:47 CST --- That seems to fix it completly. Thanks a lot!
http://bugs.winehq.org/show_bug.cgi?id=32789
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Austin English austinenglish@gmail.com 2013-01-30 16:03:58 CST --- Closing.
-
wine-bugs＠winehq.org