drsMarcellus

41 minutes ago, Aslain said:

In your logs I found some error from SpotMessanger mod, and this exception (exceptions are usually related to crashes):

2019-06-16 21:24:06.069: ERROR: [EXCEPTION] (scripts/client/account_helpers/CustomFilesCache.py, 519):
Traceback (most recent call last):
  File "scripts/client/account_helpers/CustomFilesCache.py", line 512, in __prepareCache
  File "scripts/common/Lib/shelve.py", line 239, in open
  File "scripts/common/Lib/shelve.py", line 223, in __init__
  File "scripts/common/Lib/anydbm.py", line 85, in open
  File "scripts/common/Lib/dumbdbm.py", line 250, in open
  File "scripts/common/Lib/dumbdbm.py", line 74, in __init__
  File "scripts/common/Lib/dumbdbm.py", line 86, in _update
  File "<string>", line 1
    'NB2HI4B2F4XXG5DBORUWGLTNN5SHQ5TNFZR
                                       ^
SyntaxError: EOL while scanning string literal

 

but got no clue where is this coming from (either some mod or game client itself)

It's a chatmod, at least I think it's the one in the attached pic.

I had the crash in Grand battle several times in the past weekend (3 times in total). It only occurs in Grand battle. Until recently XVM stats didn't work in Grand battle and there was no problem but since the last update from WOT it crashes on GB. From my point of view.......I was thinking maybe XVM can't handle the statistics from 60 players in one game and that will cause the crash, but I might just be wrong as well ;-)

I will try to play a Grand battle tonight, without XVM to see if the crash occurs again. That will be tonight since I am at work right now.

Aslains_WoT_Logs.zip

31 minutes ago, Ress said:

Already reported few times,
Battle Observer bug, don't use it (until it's fixed).

ps screenshot is nice addition, but posting logs is much better.

Okay, that is good to know. Where do I get the logfiles? (for the next time I report a bug)

Hi there,

The counter on top of the screen ingame is not counting the kills. As you can see on the image my team has 1 kill and the enemy has 2 kills.

If I run into other bugs or issues I let you know. Since my profession is test engineer I have an eye for that ;-)

1 minute ago, Aslain said:

Tank carousel scaling problem is known to me, it shall be fixed in upcoming XVM releases.

Nice to know Aslain, thnx. For now I adjusted the scaling from 0.8 to 1.0 and that fixed the problem.

3 hours ago, Darth_Clicker said:

In my case, the problem was caused by an old carousel.xc file in my Aslain's Custom Folder.  This xvm file changed in the latest version of xvm.  If you have custom settings for the carousel loading automatically from the Custom Folder during installation, you need to update that file with the new one in the current version of xvm.

 

Since you didn't provide any logs, I can't tell if the above situation applies to you or not....it is just what was true in my case.   

 

It is always best to include your logs whenever you post about a problem with the modpack.  See the link in my signature below if you need assistance.

I will take a look on that. Thanks for the tip regarding the logs.

The layout of the tankcarrousel seems to be fucked up. Info doesn't fit properly in the windows.

The info in the carousel is not projected correctly. Seems to be a problem with the layout.