linaWOT

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.

Hey, just want to let you know that it seems like WG changed some things with 1.20 again as the atlas files created doesnt work any longer for me. The InGame UI is completly messed up. I'm using 066. Is there any new update or anything I have to do to make it work again?

Alright, yeah it is very likely that this is part of the same problem. I have seen this dot as well. Those full OTM for targets out of my viewport are even more annoying. For me at least.

WOT 1.20 / XVM 10.4.0_0007 (XVM installed only) I see OTM for vehicles that are not in my viewport since the latest release. It is kind of annoying. It might be related to the target markers for like "Attack Target" etc.. 2nd screenshot from a client without mods.

Hi, I want to report a problem that occurs while using XVM and Battle Assistant mod. I can't remember when it started, but it is like that for a while now. I use XVM to have the map segment + aiming point indicator on the minimap while playing SPG. The positions of those indicators don't match (sometimes more sometimes less) if I am using Battle Assistant mod at the same time. It seems to be related to the trajectory view while using BattleAssistant. The movement of the aim point on the map does not match up with the movement on the minimap if using this view. Switching back to the on top view the aim marker jumps to the rigth location on the minimap again. I have contacted the developers of this mod as well, but I am not sure where the problem is. It is possible that it requires efforts from both teams. Cu

Because of an issue some parts of XVM crashes and so will not be rendered as expected.

Pls see my last post about where you can check what is included in the patch. This update was nothing else than to reflect the new WoT version due to the mini-patch again, but without any other changes and fixes. It makes no sense to refer a new version and expect a fix for a problem which was not targeted at all. It's just a wrong expectation. However, I'm surprised that we haven't heard anything from Dev's so far. Not even a confirmation and that they are aware of this and might look into it at some point. But again, we all don't know their other duties and real-life situation.

Ofc it is still there, because the issue wasn't handled so far. You can check for the changes here: https://gitlab.com/xvm/xvm/-/commits/master Latest commit: https://gitlab.com/xvm/xvm/-/commit/8dba0d6c8be7205f49eeb46f5173d0ad2bc12c3b There was no change except a version number update.

I use Windows7 64bit as well. Still a good and stable OS. I will wait whether the devs find the problem and provide a fix. It seems like something that should be fixable since it worked before and still does randomly

From my experiene they normally do and respond quickly. But they might be on holidays or have other duties. So all we can do is wait till they can take care of those issues.

It might be a good idea to start a new thread over picking up an outdated thread. Also what could help are screenshots of what you are reporting here.

You should be more precisely about what does not work and about your observiations.Might be the case that you encounter the same problems as many others since the last micro patch. Btw. Its not called Win8, but WN8.