Jump to content
Korean Random

^CHAMPi^

User
  • Content Count

    28
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by ^CHAMPi^

  1. Thanks for you feedback. It's nice to see that it works now. Let me know if it breaks again.
  2. The reason is a broken camera hook. It seems that the number of arguments are different between wg and lesta client. I'll try to fix it Based on the fact that the penetration power of an ap/apcr projectile is not only losing over distance. It's also affected by a random value. It's +/- 25% of the base penetration power. The mod can't know this value, but it can calculated the remaining piercing power over distance and can subtract 25% of this value. When this value is still greater as the enemy tank armor, it will for sure penetrate the armor. At least if you hit exactly the point where you're aiming at (dispersion factor). Penetration example: The default alpha pen for the Object 268 V4 is 293mm. This value will decrease over distance -25% = 219mm +25%= 367mm The RNG roles a value for your shot penetration between 219mm (-25% lowest) and 367mm (+25% highest) as its also shown in the tooltip Return to your main questions: RNG stands for Random Number Generator, that calculates the value. I can add russian language if someone will help to translate it.
  3. I updated the mod, but was unable to test it by myself. So feel free to give it a try: https://wot.champi.de//mods/champi.littlehelpercollection_1.59.004_1.21.1.0.zip If it still doesn't work, please post me the latest logfile.
  4. If the settings GUI is missing, an error must have occurred during initialization. If you can send me your python.log file I can check what's going on there.
  5. It's developed for the WG version. I don't know if it works with lesta's version. You can give it a try.
  6. Hi, @spotter: The extended tooltip for equipment usage stuff still works. It's not limited inside the flash part. Feel free to contact me at any time and i will send you the needed code changes. I also included this feature in my Little Helper Collection mod - https://wgmods.net/4457/ example: For the artySplash: It still works too in all cam modes. I ported spoter's artySplash a long time ago. You can give it a try here: https://wot.champi.de//mods/champi.artyimpactradius_0.99.006_1.21.1.0.zip Equipment Tooltip colored
  7. @spoter : FYI: GUIFlash was updated. https://github.com/CH4MPi/GUIFlash/releases/tag/v0.6.0
  8. It works from a browser by using "Save link as..." but not if you try to directly open it and even not if you try to download it with python
  9. Hi, short info: since at least 2 days the link https://static.modxvm.com/wn8-data-exp/csv/wn8exp.csv returns a csv file without data, excepts the header columns (tank_id,dmg,frg,spo,def,win,battles,type,tier,tag). The JSON link works fine. Can you guys please take a look on it.
  10. GUIFlash was updated. See link for download & changelog https://github.com/CH4MPi/GUIFlash/releases
  11. In the case of the issue the following happens: Every other mod that hooks into the ArcadeCamera create method and is executed before the XVM hook of Arcade camera and returns all parameters of the original method (as it always should be for every mod hook!) will cause this issue. The XVM hook is called with one more parameter as it expect and then it happens: TypeError: _ArcadeCamera_create() takes at most 4 arguments (5 given) orignal ArcadeCamera def create(self, onChangeControlMode=None, postmortemMode=False, smartPointCalculator=True): XVM hook of ArcadeCamera: (xvm-master\src\xpm\xvm_battle\camera.py) def _ArcadeCamera_create(base, self, onChangeControlMode = None, postmortemMode = False): Please fix this issue because there are other mods out there that also using that hook to change cam stuff. Even if you don't need the smartPointCalculator parameter for your method you need to expect it in your hook or XVM will break the hook chain. Of course you also need to change the call to the base method at the end of your method from: base(self, onChangeControlMode, postmortemMode) to base(self, onChangeControlMode, postmortemMode, smartPointCalculator) btw: Please stop to recommend to install xvm alone. No one will do this
  12. @StranikS_Scan:I need to change this during the compilation process. Before I overwrite the configuration each time the options are changed ... is it possible to specify the path to the configuration file for pjorion from the command line? @goofy67: That could work, i will check it out. Thanks
  13. Is it possible to control the options 'Bytecode->Protect->Lock attributes review and double import' & 'Exec only in WoT' from command line with arguments?
  14. You can try this as alternate MoE mod ttps://wgmods.net/4322/ Expected Vehicle Values: It shows marks on gun values and also inbattle WN8, expected damage for every tank and a lot more. The 1.10.1 update is currently in review by WG but you can get it from my developer page: https://wot.champi.de/
  15. @ЧАЙНИК try updating the gambiter GUIFlash library - gambiter GUIFlash Source
  16. Никакой специальной функции, это просто для информации. Он просто показывает сопротивление местности транспортного средства. Example
  17. Это было бы здорово. Но это должно быть во всплывающей подсказке треков
  18. I thought nobody ever noticed. Even WG accepted it that way. Done
  19. @ Spoterhow about to include both values? (990ms and 792 tracer speed)? spoter forgot to jump out of the for loop after data was added once
  20. If you guys don't need the display of the MoE value in the hangar you can try this version: Expected Vehicle Values - you can get it here: https://wot.champi.de/ and here: https://wgmods.net/4322/ i can display much more as just MoE. Shows expected vehicle damage, marks of excellence percentage, inbattle WN8 and post battle WN8 (at battle result window), spot-/track and block damage and many more infos in real time during the battle. Highly customizable @spoter: we all miss you - come back
  21. https://wot.champi.de/ название было сокращено до Tooltip Pro, но оно делает то же самое.
  22. Thank you! As you maybe already saw there's a fixed version of the MoE mod and the needed mods_gui by Oldskool around. So you can use this version and don't have to wait any longer.
  23. @yepev : sure, why not? the source code belongs to spoter. i would only update it for the latest wot client version. but i need the full source (this also include the flash source and in the best case with mods_gui, which normally only spoter can give me). I already sent him a message, maybe he answer me.
×
×
  • Create New...