dirtyrat_1
-
Posts
6 -
Joined
-
Last visited
Posts posted by dirtyrat_1
-
-
I think I found the issue. It seems to be in the WoT itself, rather then in XVM.
In post https://koreanrandom.com/forum/topic/15280-pjorion-%D1%80%D0%B5%D0%B4%D0%B0%D0%BA%D1%82%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%BA%D0%BE%D0%BC%D0%BF%D0%B8%D0%BB%D1%8F%D1%86%D0%B8%D1%8F-%D0%B4%D0%B5%D0%BA%D0%BE%D0%BC%D0%BF%D0%B8%D0%BB%D1%8F%D1%86%D0%B8%D1%8F-%D0%BE%D0%B1%D1%84/ there is 0.9.18.0_410_Decompile_WOT.zip which contains res\packages\scripts\client\AvatarInputHandler\DynamicCameras\ArcadeCamera.py and that contains the following function:
def __calcRelativeDist(self): if self.__aimingSystem is not None: distRange = self.__cfg['distRange'] curDist = self.__aimingSystem.distanceFromFocus return (curDist - distRange[0]) / (distRange[1] - distRange[0]) else: return
When distRange[0] and distRange[1] are the same, it causes a division by zero, and thats probably why the game gets stuck at battle loading screen.
Would it be possible to supply a fixed function somehow using XVM?
-
Average removes the difference in number of alive vehicles, which IMHO plays a role too.
-
-
I would like to have one single camera distance in arcade at 12m, and 3 zooms in sniper 3x, 9x, 27x.
Sniper config works fine.
But the arcade is giving me difficulties:
"arcade": {
"startDist": 12,
"scrollSensitivity": 100,"distRange": [12, 12], // with same values in min and max, entering a battle gets stuck at loading screen
"distRange": [11.99, 12], // entering battle works again, but I get two virtually same distances in arcade mode
},
Any suggestions?
(I have XVM 6.6.4)
-
An approximate time frame of the updated win chance? Days, weeks, months...?
Camera distance and zoom config
in XVM: English Support and Discussions
Posted
You fall back to the default 2 and 25 as min and max, in case they are equal.
While that avoids the division by zero, it defeats the purpose why I would like them to be the same actually (to have exactly one arcade distance, that switches straight to sniper on mouse wheel forward).
I would prefer something like returning 0 from __calcRelativeDist() when min and max are equal, or something like that, that permits achieving my configuration goal.