MG_Billy_Mitchell

@Aslain: It just happened again in the last battle I played, 2:05 AM EDT. I can confirm it's not related to Overwolf, because it was not running at the time. The freeze also doesn't have anything to do with leaving the battle early, at least on my machine. In several battles that have frozen, I died but am sure I stayed until the battle was over. This is one of them. Aslains_WoT_Logs.zip

This is exactly the problem I have sometimes. For me, it is intermittent and unpredictable. Sometimes I might go a week or two with no problem, sometimes 2 or 3 days in a row. Usually only once or twice a day when it happens. No pattern that I can determine, and I've uploaded my logs to Aslain on several occasions with no luck identifying the problem.

I'm going to run 45-60 days without Overwolf. If I get a similar crash during that time, that should rule out Overwolf.

@Aslain: Just froze in return to garage in Road to Berlin mode. Free cam not working, but the garage motion (for example, troops marching) is still visible. My second battle in that mode today, after 4 or 5 in random mode with no problem. I just did a clean install of 1.9.0.2 #02 earlier tonight. So any errors in the log happened within the last hour or so. Aslains_WoT_Logs.zip

I see these other people saying "I played 15 battles and no problem, so it must be fixed", or "No freeze in 200 battles so it's good now". That doesn't work for me, because the freezes are so infrequent. I'll won't Overwork for the rest of May. Let's see what happens.

I've been playing Frontline since it came out, and I've never had the freeze problem after a Frontline battle before -- even when I was having the problem in Random battles. And I've always played with mods in Frontline. I'm at Level 9 right now, haven't had the problem in this iteration, or this month's phase until today. It just happened now, in my first Frontline battle of the day. I've attached the log. As far as I'm concerned, the reason this needs a serious debugging effort is that it's intermittent. Why is it that I can go for two weeks without it happening? And when it does, it's just once. After closing out the game by End Task and restarting, it doesn't happen again. There must be some kind of trigger for it. Aslains_WoT_Logs.zip

That bug's been there forever. Just right click as soon as you spawn and you're good to go.

Yesterday's freeze occurred at 11:28, based on the time that the replay file was created. I had another freeze again today. It was only the ninth battle after I updated to #09, so hopefully this log is clearner. Today's freeze occurred at 20:08. In addition to the log archive, I'm also attaching both replays. I could remove Hangman, but I have a hunch that's not it. I wonder if it might have something to do with YasenKrasen session stats, because the session stats aren't updated properly (battle count and win count don't reflect the battle that freezes) after I use Task Manager to close WoT and restart the game. In today's freeze, I left the previous battle (in the TVP VTU) early because I died fast; I didn't have any problem returning to the garage. So I started the battle that froze in the Panther, and I didn't get either the Panther results OR the TVP results in my session stats when I restarted the game. Do you see anything wrong with YasenKrasen? Aslains_WoT_Logs.zip 20200322_1119_ussr-R27_SU-14_35_steppes.wotreplay 20200323_2000_germany-G03_PzV_Panther_38_mannerheim_line.wotreplay

@Aslain, it just happened again today -- so it's not the ping spam mod. (But I like Champi's better, so that switch was good.) Here's the log and screenshot. It was just my second battle of the day. One other thing I noticed: I can toggle the chat open and closed with the Enter key, but I can't toggle the minimap on and off with "M". Probably doesn't matter, but if you happen to know what the sequence of shutting down the battle window and returning to the garage is, maybe that could help. I can't help but wonder if this is connected to something related to one of the mods for battle results, experience, or missions (because those all change at the end of every battle). Anyway, curious if you can find anything else. Aslains_WoT_Logs.zip

That's interesting. It's never happened to me more than once in a day. I finally got mad enough to start logging the crashes a month ago. Once it happened two days in a row, but then it didn't happen again until 10 days later.

OK, thanks, I'll give that a shot. Two questions: Do you know if there are any other ping spam blockers? Did you happen to notice any other errors?

Aslain: I have notice an intermittent problem where the game will freeze after a battle is over, during the return to garage. I've kept a log over the past month to document when it happens and what the conditions are. It's happened with different tanks, on different maps, and usually after a victory (although one time after a loss). I'm attaching your log file, along with my spreadsheet and a screen cap of what the screen looks like when the game freezes. Although the screen background is the garage, the rest of the screen elements are still in battle. So, for example, if I hit the Enter key, I can open the chat dialog. This one in particular is really frustrating, because I fought an excellent battle: probably earned 1st class/#1 XP on team/#1 damage on team and I finished a personal mission. But because of this freeze, I didn't get to the battle results screen to collect my x3 bonus. When I restart the game, that won't be an option, and the battle results won't be available to me. I hope you can figure this one out. Thanks in advance for your help! Aslains_WoT_Logs.zip Crash Log.xlsx

New installer software? Looking forward to that. Any chance it will allow for changes in how to handle the selection tree?

hasta la vista, baby.

I don't use any mods for my consumables, and had no problem running Frontline last night with my normal mod installation.

Same here. Before returning to the garage, same gif.

Was that ranked battles? I'm having that problem too, but only in Ranked and not in Random.

I noticed both of these prior to the 9.22.0.1 minipatch, but I don't remember when exactly they started. It might have been prior to 9.22 also. Ekspoint Team WN8 does not appear, even though I have it selected in the install (with the WinChance option). Arty Log shows up for the first battle after mod pack install, but for any battle after that it does not appear correctly. Log zip and screenshots attached. Screenshot 98 shows Arty Log appearing correctly. Screenshots 99 and 100 show how it appears incorrectly. No Team WN8 on any of the screenshots. Aslains_WoT_Logs.zip

Has anyone else noticed that when you stay in a battle after you are killed, that the minimap tank labels don't work correctly? Once you switch your camera out of your own tank, the label for the next tank you switch into never changes. So when you switch again into another tank, the label is from the old tank you just left. This isn't a mod pack problem, obviously, it's the mod itself. Example screenshots attached. After my Badger got waxed, my camera went to the IS-7 (top of the team list). When I switched again, into the Maus, the minimap label is still "IS-7".

I can confirm this is still an issue (or an issue again). I finished the Death Star grind on Monday to get it as my first T10 tank just before the 9.21 upgrade. Last night I was running the FV 217 Badger and played my first Grand Battles -- a half dozen, on the Klondike map. Enemy side was mirrored in all of them. Random Battles were fine.

I don't think it's an installer error. The thing is, file permissions and owner status happen at the origin end, when you make the files available for download. I can't even look at those sed.exe files in my Windows, due to the permissions that are set on the file at its origin. As I pointed out in my screenshots, I can't even change the access because I do have the sufficient permissions. As you can see from the other messages in this thread, I'm not the only one who has experienced this problem. I think what you need to do is make sure that permissions on all the files available for download are set so that everyone has full access. Thanks for your attention to this. I had this problem in the past, but not for quite a while. Tried both of those multiple times. No dice. And even waited for the next update, thinking that a newer install might overwrite all the files. Nope.

I use McAfee LiveSafe, not malwarebytes. And no problem with any of the recent upgrades until this week.

In the last several updates, my install has not worked properly. I'm getting install errors due to a file named sed.exe which appears in 4 different directories. I cannot manually delete the file, because it is set up with permissions that require administrator access from the original author. I can't even see permissions for the file. During the install, if I select "Retry" I just get the same error message. In addition to the log zip file, I've attached a Word document with screenshots that show how I have tried to access the file with MY administrator access. Screenshot description: 1, 7, 8, 9 -- the files that are causing the install errors. 2 -- Error when trying to delete the file. 3 -- Error when trying to delete the file with my administrator access. 4, 5, 6 -- I can not even see the properties of the file with my own administrator access. Aslains_WoT_Logs.zip Aslain Install Problem.docx

Just updated to 9.19 today, straight to modpack 05. Same problem as everyone else. I noticed that the garage mod for research and stats does not update properly when the game hangs. That suggests to me the problem is either with that mod, or with something that happens before that mod is accessed. Also, when i force stop the game, either through Task Manager or by pressing Alt-F4, sometimes I can't reload the game because part of the game is still running. In those cases, the app is stopped in Task Manager, but there is still a background process running that has to be terminated separately. Aslains_WoT_Logs.zip

I haven't had any crashes since updating out of the #00 modpack. #02 and #04 were perfectly stable.