Spazza Posted March 2, 2017 Posted March 2, 2017 I keep getting a loadout error when trying to make changes to my ammo or consumables when using t34-85m . I get "Service Error T34-85M please try again later. I tried the vehicle in vanilla and it works fine....You have any ideas what mod might be affecting it??.....all other vehicles appear okay at this point many thanks Sane..... Quote
Spazza Posted March 2, 2017 Author Posted March 2, 2017 (edited) Just realised that this should have been in bugs and issues........silly me ....sorry fellas Shane Edited March 3, 2017 by Spazza Quote
Moderator Quaksen Posted March 2, 2017 Moderator Posted March 2, 2017 Moved to correct section Please attach logs, see my signature link for how to and which ones Quote
Spazza Posted March 3, 2017 Author Posted March 3, 2017 Attached as requested. The vehicle auto reloads after battle, but it wont allow me to make my own changes. THe error in screenshot was me trying to adjust ammo loadout Cheers..... _Aslain_logs.zip python.log Quote
Administrator Aslain Posted March 3, 2017 Administrator Posted March 3, 2017 Cannot reproduce, but I don't own this tank. I tried it on preview. Not sure why you have this error. Try without gun sounds maybe? Also try to play with amounts on tank service window. Quote
Spazza Posted March 4, 2017 Author Posted March 4, 2017 OK thanks mate...........I will give it a try. Thank you for taking the time to look at it... Cheers Quote
My_Gaming_TV Posted March 4, 2017 Posted March 4, 2017 @Spazza, might I suggest a couple ideas in case it's not repeatable with anyone else? 1. I would try running the game file checker tool built into the launcher in the settings on the launcher, it will check to make sure there is no problems with game files, to which I see in your python log some original game file issues, could be caused by a mod or possibly you just somehow have a corrupted file. Running that check will will find any corrupted files in the game and remove and replace them. If that doesn't work then I would suggest step 2 which would be to uninstall the game, mods and all, even make sure the WoT folder is completely removed from the system as it sometimes doesn't always get fully removed when you uninstall and also delete the game caches on the computer before reinstalling the game. If for any reason your computer will not let you remove the WoT folder if it's still there after you uninstall the game, just simply restart your pc and it should allow you to delete it along with all of it's contents. If you don't know where your game cache is it's in your c drive in the following path C:/users/(user name of person registered as admin..... usually top folder with your name on it)/AppData/Roaming/ on the very bottom or close to it is a folder named Wargaming.net, just right click and delete. After making sure the game folder and game cache folders are completely wiped from your computer just restart the computer then reinstall and reinstall the mods and try again. The errors I seen in the python log suggest a tooltip error that may be related to the error you are having and shouldn't take more than running the game checker to fix, but in the off chance the checker doesn't find or fix it option 2 is your best option, although a big pain in the butt. Hope you find what is causing the problem and can find a solution that will work for you to fix it Quote
Spazza Posted March 5, 2017 Author Posted March 5, 2017 16 hours ago, Davidinlv82 said: @Spazza, might I suggest a couple ideas in case it's not repeatable with anyone else? 1. I would try running the game file checker tool built into the launcher in the settings on the launcher, it will check to make sure there is no problems with game files, to which I see in your python log some original game file issues, could be caused by a mod or possibly you just somehow have a corrupted file. Running that check will will find any corrupted files in the game and remove and replace them. If that doesn't work then I would suggest step 2 which would be to uninstall the game, mods and all, even make sure the WoT folder is completely removed from the system as it sometimes doesn't always get fully removed when you uninstall and also delete the game caches on the computer before reinstalling the game. If for any reason your computer will not let you remove the WoT folder if it's still there after you uninstall the game, just simply restart your pc and it should allow you to delete it along with all of it's contents. If you don't know where your game cache is it's in your c drive in the following path C:/users/(user name of person registered as admin..... usually top folder with your name on it)/AppData/Roaming/ on the very bottom or close to it is a folder named Wargaming.net, just right click and delete. After making sure the game folder and game cache folders are completely wiped from your computer just restart the computer then reinstall and reinstall the mods and try again. The errors I seen in the python log suggest a tooltip error that may be related to the error you are having and shouldn't take more than running the game checker to fix, but in the off chance the checker doesn't find or fix it option 2 is your best option, although a big pain in the butt. Hope you find what is causing the problem and can find a solution that will work for you to fix it Thanks David for the heads up. I did what you said and low and behold....success!!!!...............All appears to be working now. Thanks to all for the time spent trying to help me with these issues. Best modpack and support on the net for WOT Cheers........Shane! Quote
My_Gaming_TV Posted March 5, 2017 Posted March 5, 2017 7 hours ago, Spazza said: Thanks David for the heads up. I did what you said and low and behold....success!!!!...............All appears to be working now. Thanks to all for the time spent trying to help me with these issues. Best modpack and support on the net for WOT Cheers........Shane! Glad I was able to help! Sometimes it's not a modpack related issue but a game issue instead. The python log can and will tell you the difference between a mod having an error and the game itself having the error, surprised that Aslain didn't catch those errors but then again it's not a mod related issue so...... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.