I updated today to WarPack 8.7.
The Problem is, when i open the WarPack-Launcher and press "Start World of Tanks", the Launcher Quits and World of Tanks starts.
There is no Option-Panel as usual, the complete Task gets lost in the Task-Manager.
Anyone had the same Effect or a solution?
I see the same thing, but WP seems to be working. How to enable/disable certain options is beyond me at the moment. If I figure it out, I'll let you know.
OK. Here's the scoop. (A readme would have been nice)
There's now a nifty "WARPACK" button in the WoT Garage screen, just under the "MENU" button.
Click on that to open the Warpack options window.
did you do anything special with your settings ?
Цитата: f15achief от 15.08.2013 01:32:15
OK. Here's the scoop. (A readme would have been nice)
There's now a nifty "WARPACK" button in the WoT Garage screen, just under the "MENU" button.
Click on that to open the Warpack options window.
Nope, there is no WarPack-Button under my Menu-Button.
Even there are no messages that the WarPack is loaded or something else! :-\
I need the Download-Link to the Old-Version which runs perfect!
(http://pics.kz/i2/ae/f1/aef16816813ddb4f3ca75ef436f1d289.png)
Цитата: kpradd от 16.08.2013 06:04:32
(http://pics.kz/i2/ae/f1/aef16816813ddb4f3ca75ef436f1d289.png)
This Button is missing at my garage, with 0.8.5.8 it was working perfect!
Цитата: Agarwaen от 16.08.2013 08:52:37
Цитата: kpradd от 16.08.2013 06:04:32
(http://pics.kz/i2/ae/f1/aef16816813ddb4f3ca75ef436f1d289.png)
This Button is missing at my garage, with 0.8.5.8 it was working perfect!
Try an allocation of world of tanks on CPU1 in Task Manager,in processes...
I can set the allocation to CPU1 only if World of Tanks is already running, at that Point the WarPack-Task already closed itself.
Is there any chance to get a Error-Protocol to see why it close itself?
Цитата: Agarwaen от 17.08.2013 11:43:51
I can set the allocation to CPU1 only if World of Tanks is already running, at that Point the WarPack-Task already closed itself.
Is there any chance to get a Error-Protocol to see why it close itself?
Expect, we try to solve the problem