linaWOT

You can try the newest version 11.1.0.0015. There was a bug fix and it seems to work again as expected.

Hi, have noticed a bug with the floating damage values within the new version of WoT and XVM. The damage done by me is not shown in a different color (yellow/orange), like it is in vanilla wot client by default, anymore. But instead it is also red. Thats different to how it was before. This is also the case with the default settings of XVM. I could replace the color under damageText (markersAliveNormal.xc) from "null" to a specified color. but actually it keeps to show floating damage in the specified color for other damage as well, while the damage that destroys the enemy vehicle is shown in red (standard) again. bye

Thanks. Those settings work. There some settings told in that thread before, but they didnt change anything. I wounder what happen at WG site that those width and height had to be changed nowdays.

Just want to mention that I still struggle with this error I have posted and can't create battle atlas. Im using the version I was told to use (linked post). Also I checked the width (4096) and height (4600). What else do I have to do?

I guess you reffer to the version posted over there. Its actually the version I'm using and get this error. Maybe I miss the point what else is needed.

Hello, I see following error while generating new atlas files from WoT 1.22.0.2 using TIM 66.0.0.0 from 29th of may 2023 which seems still be the most actual version linked in this thread.

Todays micropatch needs an XVM update. Didnt expect WG to add so much to the game client for this event after the 1.21.1 update that it needs another XVM update.

Hello all, I have raised the issue on the wotinspector.com discord and talked to reven86 in the past few weeks. He was able to reproduce the issue and fixed it with the newest version 2.5.0. There was no connection between XVM and BA on this bug, but using XVM made the issue more visible. Without XVM it was hard to recognize. ;) So the thread can be closed as the issue is fixed by now.

Hello, I want to report a bug/problem that occurs while using XVM and Battle Assistant together. I can't really remember when it started, but it is like that for a while now. It is related to the map segment + aiming point indicator on the minimap while playing SPG and using the trajectory view. The positions of those indicators on the minimap don't match with the battlefield actions (sometimes more sometimes less). I understand that this is not a uniqiue bug related to XVM, but it feels like someone with the knowledge/skill would be required to take a look at this to get it sorted out. Thanks for your time.

Thank you. It is fixed. Those action markers on vehicles that are out of vieware gone. :)

Hey ktulho, thanks for responding. I have checked this again after your reply. The battleatlas.xml was available, but the .dds files were missing in the specific folder. I might be related to the error I got when creating the atlas files. Error: Error loading unmanaged library from path: C:\TIM-v006\FreeImage64.dll Module not found. The named dll is available in the folder. In addition I installed the Visual C++ Redist (2015,2017,2019 2022) as freeimage64.dll should be related to this based on Google, but with no success. However, I found a workaround. I copied the created png and renamed them to the dds files. This works. But maybe you can give an advise what to do to fix this error. :)

Thanks, created a bug report over there already.

http://wotreplays.eu/site/6505044#prokhorovka-aarushsakhuji-m53_m55 Time: 11:58 (help request from teammember AE Phase 1) Time: 9:10 (support request to fire on E100) Reproducable with different replays and default XVM config.

WOT 1.20 / XVM 10.4.0_0021 (XVM installed only) I see OTM for vehicles that are not in my field of view since the latest release. It is kind of annoying and it might be related to the target markers for like "Attack Target" etc as those OTM appear just in that particular case. 2nd screenshot is from a client without mods.

My specific problem with the OTM wasnt fixed with the latest update. Maybe I have to post it in the bug report section of the forum.