Jump to content
Korean Random

linaWOT

User
 View Profile  See their activity

  • Content Count

    55

  • Joined

  • Last visited

  • Days Won

    2

Posts posted by linaWOT

  6. Posted

    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. 

     

     

    • Upvote 1

  7. Posted · Edited by linaWOT

    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). 

     

     

    bug17ifmv.jpg

     

    bug2a4e0y.jpg

     

     

    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.

  9. Posted

    1 hour ago, ktulho said:

    @linaWOT Vielleicht haben sie vergessen, den BattleAtlas zu kopieren. XML ?

     

    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. :)

     

  15. Posted

    11 minutes ago, Aslain said:

    Must be broken XVM OTM markers, and related to that issue too: https://koreanrandom.com/forum/topic/81262-xvm-dot-around-otm-placement-to-request-fire/

     

     

    Still no word from xvm devs :/

     

     

    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. 

  17. Posted

    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

     

     

  19. Posted

    On 6/22/2022 at 6:54 AM, zoeballz said:

    WELL - New version of XVM still has the same bug but not happening as regularly in the last few days.

     

    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.

     

     

     

    • Upvote 2

  20. Posted

    37 minutes ago, zoeballz said:

    UPDATE - Now using XVM 9.2.1 (0002) - Bug is still there :(

    xvm.log 8.1 kB · 0 downloads python.log 127.9 kB · 0 downloads xvm.zip 298.43 kB · 0 downloads

     

    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. 

  22. Posted · Edited by linaWOT

    18 minutes ago, zoeballz said:

     

    It doesn't appear any devs have commented. Do they actually read these reports ? Someone told me they only read this forum occasionally ?

     

    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.

     

    • Upvote 2

  24. Posted

    17 hours ago, GeneralMills said:

    6th Sense only working for T29 Heavy, the in game team menu shows light bulb for T29 only, the other tanks the light bulb is present but with a line crossed through it as if it's disabled, as far as I know you can't disable this option for specific tanks

     

    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.

     

     

  25. Posted

     

    2 hours ago, pedjonix said: 
    
is there a solution that does not show statistics and win8???
    

 

     

    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.  

     

     

     

    • Upvote 1
×
×
  • Create New...