HockeyPhool

i was playing a match yesterday and another player mentioned the same problem. I asked if he was running a SafeShot mod, but he said he had uninstalled one and it was still happening. I have no idea if he was using a mod pack.

Darn. I was hoping that would be the common thread. All my testing points to that mod, but without knowing exactly how to trigger the bug I can't test with precision.

See attached screencap. This was after at least 5 battles. _Aslain_logs.zip python.log

Gumby, I haven't had any CTD's with this version of Aslain's. I'm using P_Mod and J1mB0's, FWIW.

xKapi, do you have BalCalc mod enabled?

I have enabled the 'big hotkey numbers' and 'letter shell icons' mods. When I hover over the hotkeys, I don't see the info popups any more. Instead, very small black boxes pop up. You might be able to see them in the attached screenshot, but it's very dark against a dark background. You can see my cursor is hovering over the "AP" shell icon, and the popup is just above and to the right. You can see what it should look like in 'Capture2.jpg', which I just took without either of those mods enabled. _Aslain_logs.zip python.log

Aslain, I reproduced the problem once more after enabled BalCalc mod (plus session stats, but those weren't available in 4.3.1). When it occurs, it seems as if the camera remains in one location but follows your tank. So if you keep driving you eventually drive away from the camera. You can no longer turn your turret, and auto-aim only seems to work on targets within the camera's field of view. I don't think I can correlate a specific event with the occurrence of this bug, however. I did find these errors in python.log right after the bug occurred. (I ALT-TAB'd to the desktop and opened python.log): INFO: ============================= INFO: 2015-04-26 17:14:37: [ERROR] ./res_mods/mods//xfw/python\xfw\events.pyc ERROR: Traceback (most recent call last): ERROR: File "mods/xfw/python/xfw/events.py", line 54, in __event_handler ERROR: File "scripts/client/game.py", line 489, in handleKeyEvent ERROR: File "scripts/client/AvatarInputHandler/__init__.py", line 298, in handleKeyEvent ERROR: File "scripts/client/AvatarInputHandler/control_modes.py", line 1400, in handleKeyEvent ERROR: AssertionError INFO: ============================= ERROR: TypeError: Personality handleKeyEvent retval must be set to a bool INFO: ============================= INFO: 2015-04-26 17:14:37: [ERROR] ./res_mods/mods//xfw/python\xfw\events.pyc ERROR: Traceback (most recent call last): ERROR: File "mods/xfw/python/xfw/events.py", line 54, in __event_handler ERROR: File "scripts/client/game.py", line 489, in handleKeyEvent ERROR: File "scripts/client/AvatarInputHandler/__init__.py", line 298, in handleKeyEvent ERROR: File "scripts/client/AvatarInputHandler/control_modes.py", line 1400, in handleKeyEvent ERROR: AssertionError If you want, I can point you to my latest replay where the bug occurred in my Matilda IV. I will upload my python.log. Meanwhile, I'm going to disable BalCalc and see if the problem still occurs. If I had access to the Python source code I might be able to diagnose the problem. Any idea how I might get that code? python.log

Aslain, I played a few more games with the current install and still haven't reproduced it. I recall that I disabled BalCalc mod and I'm wondering if that could be the culprit. I'm going to enable it and see what happens.

Reinstalled with AutoAim Indication + enabled, played a half-dozen battles without seeing this issue again. Will play more in a while.

Aslain, I installed v4.3.2_97. The only difference was enabling Battle Assistant. Three or four battles, no issue. I'm now going to re-enable AutoAim Indication + and retest. I'll also see if I can verify mosetsuki's comment about the problem happening after a tank is destroyed. Attaching update logs. _Aslain_logs.zip python.log

Aslain, here's an update. i reinstalled v4.3.1_97. I disabled the following mods: AutoAim Indication + Battle Assistant BalCalc Mod Everything in 'Other Garage Mods' section (even though they *shouldn't* have any effect in battle) I wasn't using anything else in your list of suspects. Also, I reinstalled J1mB0's crosshairs (1 aim circle + J1mB0's SPG). I played 4 games in 3 different tanks without seeing this issue. I'll attach updated logs. I see there's a new version of the installer, so I'll download that and reinstall, adding only Battle Assistant (and nothing that's new in the installer). _Aslain_logs.zip python.log

Aslain, this just happened again and I don't have any crosshair mods installed. I'll start back at square one, disabling the mods you indicated. I'm attaching the latest logs. The problem occurs just after my teammates and I destroy the Pz. IV H downhill from my Leopard. At that point I can no longer turn the turret or change the camera view, although I can drive normally. I cannot switch to sniper view, nor can I CTRL-click to follow another tank in spectator mode. _Aslain_logs.zip python.log

This sounds like the issue reported in the 'Perspective Lock' topic.

Aslain, I removed all mods and reinstalled them one at a time. I only saw issues with J1mB0's and MeltyMaps crosshair mods (the only two custom crosshairs I tried). I did not see the issue with any of the other mods installed. I saw it with both Koshnaranek's and P_Mod zoom mods, but only with a custom crosshair. Also, now that I am not using any custom crosshair mods I no longer see this error in python.log: ERROR: File "scripts/client/VehicleAppearance.py", line 1165, in __onPeriodicTimer The evidence points strongly to something in the crosshair mods.

What do you mean by 'crashing'? An actual crash to desktop? If you believe the problem is tied to an auto-aim modification, have you tried reinstalling the modpack without enabling that mod to see if the problem is resolved? You should attach the '_Aslain_logs.zip' and 'python.log' files from your WoT directory. It will be nearly impossible for anyone to help without logs.

Also: I don't know if this is relevant but I'm seeing the following error many times in the python.log: ERROR: File "scripts/client/VehicleAppearance.py", line 1165, in __onPeriodicTimer

With J1mB0's crosshair mod installed, I eventually reproduced this problem. I don't think it's specific to J1mB0's since it also occurred when I had MeltyMap's crosshair mod installed. I just reinstalled without any crosshair mods and will keep playing to be sure I didn't miss the real cause. I don't know if the python.log will reveal what's going on but I'll attach the latest one anyway. _Aslain_logs.zip python.log

Update: I believe I've narrowed the problem down to crosshair mods. This problem happened to me with both J1mb0's and MeltyMap's crosshair mods. I've gone back through and installed mods one-by-one, and have a configuration with everything except crosshairs and it hasn't exhibited this problem. I'm going to go back and reinstall J1mb0's and see if the problem comes back. _Aslain_logs.zip

I've seen this as well. I've reinstalled without most of the XVM and in-battle modifications, and I'm slowly adding mods back to see if I can figure out what's causing the problem. I also noticed some black flickering during battle, often right before I'd lose control of the camera. the first time it happened, it occurred as I was zoomed in and I couldn't get out of sniper mode. I noticed that auto-aim was working, and it seemed that my client was actually aiming my gun at the designated target, even though it didn't appear that way to me. _Aslain_logs.zip python.log

I installed v4.3.1_97 today. The installer chose the default contour icon set I prefer (Aslain's modern with Arab tier numbers). However, it installed the 3D Modern with Arab tier icon set. The problem occurs with a clean install. I also tried deleting the DLC cache but it didn't help. Screenshot and install logs attached. _Aslain_logs.zip

Aslain, what do you consider to be 'fishy mods'? I just reinstalled without any of the "Garage Mods" enabled, so maybe that will resolve the issue. For what it's worth, I did not experience any more CTD's after I reported this problem yesterday.

After installing 4.2.48_96, my WoT client has crashed to the desktop twice. I looked at they python.log but I don't see anything that clearly indicates what's happening. I'm attaching _Aslains_log.zip and python.log. (I tried to file this just a moment ago but got a Service Unavailable error) _Aslain_logs.zip python.log

One thing that I've noticed in a few recent games is that SafeShot seems to be interrogating the commander's reticle and not the aimpoint of the gun. I had a match yesterday where I was auto-aimed at a target in arcade view, tried to shoot but saw the "Player you are blocking my target" message because the commander's reticle was aimed at an ally. If no one is developing the mod then I guess nothing can be done about it. I just have to be more careful about where I'm looking when auto-aimed.

Thanks for the update. You might want to mention that information in the change log (and the installer, preferably). I'm having trouble finding information on what the 'main mod' does. I guess I'll just disable it. EDIT: I just installed v4.1.15 and saw the note that Locastan's HD minimap main mod will disable XVM minimap. I would still suggest you add a note to the XVM minimap section stating "incompatible with Locastan's HD minimap main mod". As always, thanks for compiling a very useful set of mods!

The v4.1.14 installer is resetting all XVM minimap choices and using only defaults. I first noticed the minimap was not displaying my usual choices, so I reinstalled the modpack and made sure to set the ones I want. I noticed all of the minimap choices were unselected when I ran the installer: However, even after reinstalling and selecting my choices the minimap is set to all the defaults: _Aslain_logs.zip python.log