Vesanius

Got a download issue with the latest v.1.19.1.0_04 modpack. Everything else downloads just fine but "Aslains_GoldPremiumTanks_TIM_1.19.1.0b.7z" gives a "File not found (404)" error. Everything until version #03 has always worked just fine.

"xfw/crashfix: adapted to WoT 1.18" an hour ago so apparently it was an XVM issue which should be hopefully fixed on the newest version.

You need to renew your XVM activation on the XVM website again. It's only active for 14 days and you need to renew it after that. If you have never had it working then you need to go the XVM website, login and activate it.

Oh sorry about that. I must have missed it.

The custom health bars on top of the tanks. Vehicle markers / OTM to be specific. So not the health bars a lone but the whole OTM fails to load. I have tried a few options and none of them works.

Here. Aslains_WoT_Logs.zip

So far the game has crashed every time I have went back to the garage.

Here's the logs. The game also keeps crashing after leaving a match each time. Aslains_WoT_Logs.zip

The health bar mod fails to load since the update. I have tried a few different styles and it just keeps the stock health bars from the vanilla game.

I don't know if it's an issue with your setting or on the XVM end but I'm posting it here anyway. I have dynamic view range enabled so I have Red (max rendering distance), yellow (445m max view range), turquoise (dynamic view range) and navy blue (view range while moving) visible. If my tanks view range goes over the maximum of 445m without binos it will show the blue circle outside of the maximum of 445m while the dynamic view range stays at 445m. I don't recall ever having this issue before until yesterday and it's really bothering me whether it's an issue with the settings or a bug. As far as I can remember the blue circle used to stay at 445m if your view range exceeded that and it overlapped with the dynamic view range circle and was hiding it. The issue seems to not be there with binos ans the dynamic view range always caps at 445m so it's only an issue with the navy blue "on move" indicator. Not the best explanation but hopefully you got the hang of it.