You are here

The forum

Problems with World of Tanks

Won't allow me to play

New topic
Reply
Author Replies
Jump to the page: 1 - 2
mchubbuc Wednesday 10 April 2013 at 2:16
mchubbucAnonymous
okay thanks, I will uninstall WoT and then try to reinstall it and follow all instructions. Thanks so much for all your help!!
Ronin DUSETTE Wednesday 10 April 2013 at 2:25
Ronin DUSETTE
For sure. I hope it works out. Let us know if it doesnt, and if not, we will get a bug report open.
Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
Eightfold_Path Monday 29 April 2013 at 0:27
Eightfold_PathAnonymous
Hi, I use a Mac and just tried playing today. I too am able to get into the game and use the garage, but actual battles crash at random, usually within a couple minutes.

I Don't quite understand what you are saying with this: "It does say it right in the script" and "try the install script again, making sure to follow all messages exactly"

When I used PoM it just sorta did everything automatically (was kind of amazed how many separate programs it was installing) Using the + Install a Program feature, it just went from one download screen to the next until I had the WoT installer, once WoT installer was done, then I was playing the game (sort of)

I'm curious how to interrupt the WoT install process, then finish with PoM. As I said, first time user, this is all new to me.

Edited by Eightfold_Path
Ronin DUSETTE Monday 29 April 2013 at 2:17
Ronin DUSETTE

I Don't quite understand what you are saying with this: "It does say it right in the script" and "try the install script again, making sure to follow all messages exactly"

Quote

I mean that there are very specific instructions in the script, so if a window pops up during install, it needs to be read carefully.

Using the + Install a Program feature, it just went from one download screen to the next until I had the WoT installer, once WoT installer was done, then I was playing the game (sort of)

Quote


If that is exactly what happened, then you did not follow the exact instructions, because it says not to launch WoT and to close the patcher BEFORE it finishes, so that the install can finish.

This is copied directly from the script

'Attention: After installation is complete, the patcher will load. Please close the patcher before logging in or finish updating to complete the installation. After this, you can run "$TITLE" when setup is done'

Quote


Basically, just cancel and close the WoT patcher/updater so that it just goes away. Then, the POM installer will finish out and create a shortcut, and it should be good. Then you can start it, and do the initial update and patch download.
Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
Eightfold_Path Monday 29 April 2013 at 7:28
Eightfold_PathAnonymous
I don't remember seeing that but I will give it another try tomorrow. Ty for response.
Eightfold_Path Monday 29 April 2013 at 10:58
Eightfold_PathAnonymous
I tried again, this time aborting the installer and allowing PoM to finish. It seems even worse now, lol...

I can only think of 3 reasons...

1. The installer has a part at the VERY start that was too brief for me to avoid, a 1.9 MB update. It was over before I knew it, couldn't cancel it. Maybe if I disable internet when it gets to this point that part will fail and I'll have a chance, but that may derail the whole process.
2. The shortcut on my desktop was the old shortcut from the first time I installed it and was not replaced by the new one, or was ineffective for some reason.
3. My machine really is just too old to be playing this (getting frames of 7-8 fps)
Ronin DUSETTE Monday 29 April 2013 at 17:25
Ronin DUSETTE
You would need to delete the virtual drive (In the Configure window) that originally held the game, then try reinstalling it. lol. Hopefully that will work.
Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
Eightfold_Path Monday 29 April 2013 at 18:24
Eightfold_PathAnonymous
The script asks you to do that each time, and I have. But the shortcut doesnt delete as part of that process. I'll try one more time, but really, idk why I bother. ven if i get it working the game is gonna be too choppy to enjoy lol...I just played at a friends house and really liked it, probably just time to get a new system
Ronin DUSETTE Monday 29 April 2013 at 18:48
Ronin DUSETTE
Possibly. An upgrad usually fixes things like that.

That notwithstanding, the shortcut can be deleted manually, and then try the install from a fresh start.

I have had it running on Linux fine, but thats on my gaming system. So far, WoT keeps giving people issues in Mac, though.
Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
Precious84 Friday 10 May 2013 at 20:47
Precious84Anonymous
I did install today as the instructions said, and the game is starting (loading), but before beeing in the garage crashing, when the laoding line is almost up to 100 %

this is the debug code: whats wrong with my mac/the game? Please help!

SRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevationType, ...) semi-stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockExclusive (0x15a900): stub

fixme:thread:ReleaseSRWLockExclusive (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockExclusive (0x15a900): stub

fixme:thread:ReleaseSRWLockExclusive (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockExclusive (0x15a900): stub

fixme:thread:ReleaseSRWLockExclusive (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockExclusive (0x15a900): stub

fixme:thread:ReleaseSRWLockExclusive (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockExclusive (0x15a900): stub

fixme:thread:ReleaseSRWLockExclusive (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockExclusive (0x15a900): stub

fixme:thread:ReleaseSRWLockExclusive (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x5de6cfe4): stub

fixme:thread:ReleaseSRWLockShared (0x5de6cfe4): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockExclusive (0x15a900): stub

fixme:thread:ReleaseSRWLockExclusive (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x15a900): stub

fixme:thread:ReleaseSRWLockShared (0x15a900): stub

fixme:thread:AcquireSRWLockExclusive (0x15a900): stub

fixme:thread:ReleaseSRWLockExclusive (0x15a900): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockExclusive (0x5de6b680): stub

fixme:thread:ReleaseSRWLockExclusive (0x5de6b680): stub

fixme:thread:AcquireSRWLockShared (0x5de6b680): stub

fixme:thread:ReleaseSRWLockShared (0x5de6b680): stub

X Error of failed request:  BadWindow (invalid Window parameter)

  Major opcode of failed request:  10 (X_UnmapWindow)

  Resource id in failed request:  0x1000001

  Serial number of failed request:  204

  Current serial number in output stream:  205

fixme:advapi:UnregisterTraceGuids 0: stub

fixme:advapi:UnregisterTraceGuids 0: stub

[05/10/13 20:44:10] - Running wine-1.5.24 WorldOfTanks.exe (Working directory : /Users/Leene/Library/PlayOnMac/wineprefix/WorldOfTanks/drive_c/Games/World_of_Tanks)

X Error of failed request:  BadWindow (invalid Window parameter)

  Major opcode of failed request:  10 (X_UnmapWindow)

  Resource id in failed request:  0x1000001

  Serial number of failed request:  359

  Current serial number in output stream:  360

[05/10/13 20:45:02] - Running wine-1.5.24 WorldOfTanks.exe (Working directory : /Users/Leene/Library/PlayOnMac/wineprefix/WorldOfTanks/drive_c/Games/World_of_Tanks)

fixme:ntdll:NtConnectPort (0x5b0c1170,L"\\\\ThemeApiPort",0x33f98c,0x0,0x0,0x0,0x33f99c,0x33f998),stub!

fixme:win:EnumDisplayDevicesW ((null),0,0x118ab48,0x00000000), stub!

fixme:win:EnumDisplayDevicesW ((null),1,0x118ab48,0x00000000), stub!

fixme:win:EnumDisplayDevicesW ((null),0,0x33e9c4,0x00000000), stub!

fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot

fixme:toolhelp:Heap32ListFirst : stub

fixme:win:EnumDisplayDevicesW ((null),0,0x33e2a4,0x00000000), stub!

fixme:win:EnumDisplayDevicesW ((null),0,0x33e064,0x00000000), stub!

fixme:dxgi:dxgi_output_GetDesc iface 0x177b78, desc 0x33e640 stub!

fixme:ole:CoInitializeSecurity (0x0,-1,0x0,0x0,0,3,0x0,0,0x0) - stub!

fixme:wbemprox:client_security_SetBlanket 0x44221fac, 0x17f288, 10, 0, (null), 3, 3, 0x0, 0x00000000

fixme:wbemprox:client_security_Release 0x44221fac

fixme:win:EnumDisplayDevicesW ((null),0,0x33d584,0x00000000), stub!

fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported.

Please configure the application to use double buffering (1 back buffer) if possible.

fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.

fixme:d3d9:d3d9_device_CheckDeviceState iface 0x177b78, dst_window 0x0 stub!

fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0xfd3f65c): stub

fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

fixme:win:EnumDisplayDevicesW ((null),0,0x33e51c,0x00000000), stub!

fixme:win:EnumDisplayDevicesW ((null),0,0x339fb4,0x00000000), stub!

fixme:win:EnumDisplayDevicesW (L"\\\\\\\\.\\\\DISPLAY1",0,0x33a2fc,0x00000000), stub!

fixme:win:EnumDisplayDevicesW (L"\\\\\\\\.\\\\DISPLAY1",1,0x33a2fc,0x00000000), stub!

fixme:win:EnumDisplayDevicesW ((null),1,0x339fb4,0x00000000), stub!

fixme:d3d:state_zenable Z buffer disabled, but ARB_depth_clamp isn't supported.

fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

fixme:win:EnumDisplayDevicesW ((null),0,0x33ed34,0x00000000), stub!

fixme:win:EnumDisplayDevicesW ((null),0,0x33eaf4,0x00000000), stub!

fixme:dxgi:dxgi_output_GetDesc iface 0x13b38268, desc 0x33f0cc stub!

fixme:ole:CoInitializeSecurity (0x0,-1,0x0,0x0,0,3,0x0,0,0x0) - stub!

fixme:wbemprox:client_security_SetBlanket 0x44221fac, 0x13b38268, 10, 0, (null), 3, 3, 0x0, 0x00000000

fixme:wbemprox:client_security_Release 0x44221fac
Ronin DUSETTE Friday 10 May 2013 at 21:58
Ronin DUSETTE
We need your whole debug output. Also, we need your computer specs for your system. Linux version, arch, graphics card, installed driver for graphics card, etc.

Please refer to the stickies in top of the forums on how to properly post information regarding this.

From the looks of it, Ill say right now, that it looks like you dont have your graphics drivers installed.

Please post more information on your system and the proper debug output (you can get this by following the instructions at the top of this forum).
Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
chainmailchan Sunday 16 June 2013 at 17:11
chainmailchanAnonymous
registered just to say thank you to DJYoshaBYD. :D on my way to a smooth install!
Ronin DUSETTE Sunday 16 June 2013 at 20:29
Ronin DUSETTE
Excellent
Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
You are here: Index > PlayOnLinux > Problems with World of Tanks

This site allows content generated by members, and we promptly remove any content that infringes copyright according to our Terms of Service. To report copyright infringement, please send a notice to dmca-notice@playonlinux.com