Nor.DuFFman

Happy to do it! Tanks for the modpack! 💚

Ok, I have now played for 1 month (15.11.2023 - 15.12.2023) without crashing. ~ 400 battles. It would seem like "Hitmarker" maybe was the culprit. Im adding back some mods now: Show the garage clock Show advanced info on the carousel Accurate Damage Indicator Disable Gun shake effect after shot Scope Shadow Remover Custom Damage Indicators Object 279 Personal Mission auto-reset Marks of Excellence calculator lebwa Sixth sense animated icon 10s bulb Fog Remover: fog & sun-glare Garage icons, class colored icons + golden colored premium tanks by aslain Garage Mastery Unanonymizer on battle results Crew Auto-return Oldskool Equipment & skill icons: Marked ammo icons Will update after some playtime or if game crashes again 😉

Crash 22:51 Steel Hunter - Huragan Removing Hit Marker Aslains_WoT_Logs.zip

I still have hitmarker mod enabled, but I have been playing 182 random battles without crash since I removed the "Modpack button" on 30.10.2023 For me in the past the crashes have been random though, so 3 days is in my opinion not enough to verify anything yet.

Ok, I will do that next time i crash

crash: 15:39 - 30.10.2023 Fjords, standard battle - WZ 132A Removing: Modpack button in the garage Aslains_WoT_Logs.zip

Yeah, I downloaded the latest when I reinstalled, as I always do. I only get notified about new modpack update when I start the game, so if I've my game has been launched for some time without restarting, I wouldnt know if there was an update to the modpack. I'm one of those guys who has to have my computer idle in the background because I can't sleep without the computer fan noise, therefore I dont restart my game all that often either. Sure

Crash. 00:02 - 30.10.2023 Studzianki - Standard battle - WZ 132A Removing Marks of Excellence Calculator (MoE) - lebwa Aslains_WoT_Logs.zip

At this point I'm starting to wonder if its just a game problem and not any mods causing it, seeing I am almost down to vanilla. But at least we will find out!

Crash time: 01:11 27.10.2023 Outpost - standard battle - SU 130 PM Removing: Crew Auto-return: OldSkool Sixth Sense (NON-XVM) - static icon : the all seing eye v1 Aslains_WoT_Logs.zip

I will do that next time I reinstall. I just recently (1-2 weeks ago) added Player Panels pro by CHAMPI as a replacement for unselecting "Show HP bars" from XVM section [PANELS & WINDOWS (IN-BATTLE)] as CHAMPI's mod was listed under the [NON-XVM MODS BRANCH]. The WoT vanilla healtbars (picture 1) doesn't give you the HP numbers (picture 2) as far as I know, just a green bar wich shows you somewhat how much HP a tank have, but without the actual numbers making it an actual handicap to play without a mod that does show this. The Crew auto return I also switched from the "Crew Auto-return (XVM)" to "Crew Auto-return: OldSkool" some weeks ago. I reinstalled yesterday with less selections, so I will play untill I crash again, then I will remove more. So we can hopefully pinpoint where the problem is.

M46 Patton, Abbey - Standard battle. freeze at approx 03:25 Reinstalling with fewer options selected Aslains_WoT_Logs.zip

Just had another crash. Now without any xvm selected options. Amx 1390, Abbey - Standard battle. freeze at approx 15:35 Reinstalling modpack again with even fewer selections now. Aslains_WoT_Logs.zip

I have removed alot of options from the modpack, but I still got a freeze today. Obj. 430 II, Karelia, standard battle. Crash at approx. 02:08 cet I think I only had 1 selected xvm option for the garage at this point. Im reinstalling now and unchecking everything from xvm options. Aslains_WoT_Logs.zip

Hi again 😃 Standard battle - Redshire - Kpz 07 P(E) I noticed it first happening: 23:10 So I had a match where whenever I enter sniper view my tank start aiming at a specific point, causing the turret to turn away from where I am actually aiming. I only use shift to enter sniper view, and have disabled "scroll to sniper view". This made it impossible to do anything except trying to shoot people without using sniper-view. I took a video recording of it. Any ideas what could cause this? Aslains_WoT_Logs.zip

Hi again. I just had this happen in a Frontline battle. But it was totally different here. So what happened, I was playing my GSOR 1010 FB, did some dmg, and then I died. Nothing off so far. I got the tank selection and map to choose a new spawning location. I switched to my Bourrasque and shot a couple mags. No problems here, BUT then I shot 1 shot and went for a reload (with 1 still in the mag). The reload indicator dissapeared, and it didnt seem like it was reloading, so I then tried to override reload with 2-button (premium ammo), didnt seem to work. I waited for about 20 seconds and the two gray "bullets" turned green indicating it had reloaded. But I was now unable to shoot. I tried pressing "C" for a new reload, but it did nothing. I then pressed "1" to force reload to regular ammo. The 2 green bullets turned gray, but no reload indicator showed. I tried to spot since I was unable to shoot. Died. Did NOT get the tank selection menu with map to choose a new location. Since i couldnt choose a new tank i just had to wait looking at my dead tank. Weirdly enough when aiming around me, the turret turned on my dead tank, and I could even autoaim at enemies while dead. After maybe a minute I automaticly respawned in the same zone with another tank, the CS 52 LIS. The 2 bullets from the bourrasque was still here, so It now confirmed the hud was bugged from the previous tank. (all the modules in left corner was all red even though I just spawned). I was still unable to shoot, BUT i was able to use my Frontline consumables (inspire and artillery strike). So i went spotting and died. No respawn screen. spawned automaticly with GSOR 1010 FB again, same problem. cant shoot. die. No respawn screen. spawn with Bourrasque. cant shoot. die. Match ends and now the victory screen gets locked and is overlaying in the garage just like it usually happens in random battles (Like in the pictures above in this thread). So yeah. A weird experience, but maybe it could shed some light on the problem? Attaching logs. Edit: reinstalled modpack without "accurate damage indicators" and "xvm sight" Aslains_WoT_Logs.zip

Another crash. Berlin, standard battle, obj 430 II crash time: 21:37 Aslains_WoT_Logs.zip

Another crash. with battle hits viewer disabled, but with "colored scale (better blue)" re-enabled. Lakeville - ST-I (standard battle) Time of crash: 00:51 Aslains_WoT_Logs.zip

Yeah, I'm not playing on the best computer either. That could possibly be part of it. Also im on 4 monitors and watching youtube/twitch and browsing chrome while playing (normally when dead and platoonmate still alive) so that could possibly also be affecting it. Although other people having this exact same thing happening could suggest there is something in the modpack that causes the crash. I could potentially play without the modpack for a while to check if it happens in vanilla, but I hate playing without your OTM (vehicle colored by class, both in battle and garage) among other mods. I disabled the "battle hits viewer" now. So I'll see if that changes anything.

Ok thanks I'm gonna try that, and I'll keep you updated 😃

Had another crash today just now. crash time 18:20 random battle, fishermans bay, charioteer Aslains_WoT_Logs.zip

I just updated to version "Aslains_WoT_Modpack_Installer_v.1.21.1.0_14" I turned off the "colored scale (xvm with better blue)" to see if that stops my game from crashing, but now the floating damage numbers are back to being wrong again. I would much rather have wrong colors on damage numbers than the game crashing all the time. (even though platoonmate and my own damage numbers are hard to differentiate) Attaching pictures of the damage numbers: 1: teammate shooting enemy 2: platoonmate shooting enemy 3: me shooting enemy I dont need to see other players stats (XVM) as i play with anonymizer anyways, but I do want my game to look like it does with the selected mods that I have. Is there a way to fix the floating damage numbers color without selecting the "colored scale (xvm with better blue)"?

Hi Aslain, Tank played: CS-52 LIS Game mode: Standard - Fishermans Bay Last Crash Time: 03:05 cest Mod version: Aslains_WoT_Modpack_Installer_v.1.21.1.0_13 My game crashes/freezes after the battle has completed. Just after the "Victory/Defeat/Draw" and then the game loads back to garage but the ingame HUD remains and is overlaying the garage. Attaching 2 pictures from a match just a couple matches before this one where i managed to get some screenshots. This has been happening at random (sometimes every 5 battles, sometimes every 50 battles.) I have to close the game and restart it to continue to play. I found another post in the forum about the same exact problem (https://aslain.com/index.php?/topic/23185-random-crash-freeze-at-end-of-game/#comment-112996). But the solution you provided here did not work as far as I know. I've had this problem for a couple of months in every last version of the modpack, so I decided to try to uncheck different stuff from the mod-installer options. 3 days ago I got another problem after removing some mods where the floating damage numbers had the wrong colour. Teammate, platoonmate and enemy floating damage numbers were correct, but my floating damage numbers were yellow (and hard to read) instead of purple. I searched this forum and found another guy with this problem (https://aslain.com/index.php?/topic/14576-floating-damage-text-colour/#comment-74168) where you told him to select colored scale (xvm with better blue). During these 3 last days i did not crash at all at the end of the game (not sure if this was random luck or because i removed some mod option), but today i reinstalled the modpack and selected "6 colors Team XVM with better blue". My floating damage colour then became the correct purple, but now the game has started crashing again at the end of the battle. It has crashed twice in this session. The crashes has been occuring with different tanks. I have not played the steel hunter event that is going right now. Aslains_WoT_Logs.zip

Yes, but i still think the best option for the mod is to show the: From Base - To Max (like I mentioned before) For T34: 11.87s - 14.4s Then there would be no question about it being legal, and it would be 100% fair

Okay =) Ill trust you on that topic then! Edit: Only problem here is if it says on the modcreators page that the mod does not include equipment calculation (but it does), and WG believes it without testing it. And then we are left with a false positive?. :/