artifact4727 0 Posted December 25, 2014 It (see topic) happens only randomly when opening vehicle stats tab. Game becomes unresponsive can be killed only in task manager. It doesn't happen without xvm, Quote Share this post Link to post Short link Share on other sites
13 3,395 #238526 Posted December 25, 2014 How to describe your problem correctly and get help faster Quote Share this post Link to post Short link Share on other sites
Qu1ckJ 7 #238802 Posted December 26, 2014 i have exactly the same problem as artifact4727.i use the latest xvm version 5.5.0 Quote Share this post Link to post Short link Share on other sites
Uti-Puti 344 #238810 Posted December 26, 2014 @WOT_Avenger, I think your problem is not in the XVM. Delete other mods and test again)) Quote Share this post Link to post Short link Share on other sites
Qu1ckJ 7 #239326 Posted December 26, 2014 i delete all the mods but the problem still exist. If i delete the xvm freezing stops. Quote Share this post Link to post Short link Share on other sites
artifact4727 0 #239780 Posted December 28, 2014 now with the final I don't get that error too often anymore but it still persits, the logs are taken right after a freeze xvm.log python.log configs.zip Quote Share this post Link to post Short link Share on other sites
sirmax 5,499 #239783 Posted December 28, 2014 You have this lines in the python.log: [ERROR] (scripts/client/account_helpers/AccountValidator.py, 73): Couldn't get vehicle using compact descriptor: (59921,) Try to clear game cache - remove %USERPROFILE%\AppData\Roaming\Wargaming.net\ Quote Share this post Link to post Short link Share on other sites
Qu1ckJ 7 #239977 Posted December 28, 2014 (edited) the only solution for me to play without freezes is to uncheck Players stat (awards) in xvm website Edited December 28, 2014 by WOT_Avenger Quote Share this post Link to post Short link Share on other sites
artifact4727 0 #240077 Posted December 29, 2014 unfortunately the error remains (59921,) and the freeze remain @WOT_Avenger thx I try that out python.log Quote Share this post Link to post Short link Share on other sites
13 3,395 #240168 Posted December 29, 2014 Please try nightly build #3606+. If problem persist, please Right click on the Computer icon on your Desktop and choose Properties option. In the System window click on Advanced system settings in the left pane. In the System Properties window select Advanced tab and click on Environment Variables. In the Environment Variables window you will find two sections: User variables and System variables. Click "New...". Then, in the New User Variable dialog window type the XPM_DEVELOPMENT in "Variable name" field and 1 in "Variable value" field. Click OK button. Attach new logs after the freeze. Quote Share this post Link to post Short link Share on other sites
Qu1ckJ 7 #240620 Posted December 30, 2014 Please try nightly build #3606+. If problem persist, please Right click on the Computer icon on your Desktop and choose Properties option. In the System window click on Advanced system settings in the left pane. In the System Properties window select Advanced tab and click on Environment Variables. In the Environment Variables window you will find two sections: User variables and System variables. Click "New...". Then, in the New User Variable dialog window type the XPM_DEVELOPMENT in "Variable name" field and 1 in "Variable value" field. Click OK button. Attach new logs after the freeze. no issues since yesterday with nightly build 3612. keep up the good work guys. Quote Share this post Link to post Short link Share on other sites
artifact4727 0 #240774 Posted December 31, 2014 i ve been playing all day long with 3612 and i didn't have a single freeze, didn't need to set XPM_DEVELOPMENT variable Quote Share this post Link to post Short link Share on other sites