Jump to content

Ress

Modder
  • Content count

    88
  • Joined

  • Last visited

  • Days Won

    8

Ress last won the day on September 2

Ress had the most liked content!

Community Reputation

19 Good

About Ress

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Server
    EU
  • Location
    Croatia

Recent Profile Visitors

584 profile views
  1. @ZoeBallz sadly they are linked together (little side effect). Hmm...If you can't see last hit (tank) on damage log, maybe try installing final shot mod as alternative? (it sticks on screen forever and shows direction) Or simply re-enable showPostmortemTips.
  2. If you are using XVM there is option for it, but u have to manually edit config file (with notepad++). inside res_mods/configs/xvm/Aslain/battle.xc change"showPostmortemTips": true, to "showPostmortemTips": false, This should be added to modpack, since options for battle hints are included.
  3. Ress

    [1.1.0] XVM config parts (collection)

    Second on the list: miscellaneous stuff from my config (TeamHPPool, OTM, random stuff that someone might find useful...)  NOTE: Created and tested on 1920x1080, also with default XVM config in mind Quick install guide: 1) Copy .xc files and icons folder (if included) inside: res_mods/configs/xvm/<your config> folder 2) Add required formats: inside elements.xc and battleLabels.xc TeamHPPool (requires: only XVM, no extra py_macro) PerformancePanel (requires: mod_wn8_chance.py (by Tey - download link) & battleEfficiency.py (by Kotyarko_O - download link)
  4. In short, if you are on boot camp stage best to complete it without any mods. boot camp can me buggy, freezing, crashing...with many mods.
  5. Ress

    Battle Screen Ping and FPS

    xvm - yes, inside elements.xc add: "debugPanel": { "$delay": 100, "alpha": 0 } vanilla game - maybe...
  6. @irell Well i never had this issue, however i doubt it's xvm related this time around. Also using few mods you guys have installed. (also played 10 games today, after nano-patch) Only 2 mods that you and @nesquik have in common (and i don't use) are PMOD and No Fog + Max Far Plane. Maybe test it without them, until its confirm what's the issue?
  7. ...out of curiosity: 1) When this happens, do you have high ping or any lag indication? (did you add wot to firewall exception (launcher settings) 2) Did you try playing few games in safe mode? (just to verify that it might be mod related) 3) Did you update any drivers recently? (prior to issue maybe)
  8. Generate and attach logs.
  9. Ress

    Info Panel settings

    Well izeberg info panel is one of the mods that uses izeberg.modsettingsapi. The way settings for those mods are stored are different then poliroid.modslistapi mods for example. Usually when you install new mod that uses izeberg.modsettingsapi, it will reset setting to "default" for all mods that use it. There is no way to preserve settings (from config folder or some config file) like with some other mods. EDIT: I know, can be frustrating but you will get used to it. Also if you are to clear game cache, u will also reset izeberg.modsettingsapi settings (if i am not mistaken they are stored somewhere inside cache)
  10. -Well you have wot client v.1.1.0 #967 that's good. But for other logs you should have Aslains_WoT_Logs_Archiver.exe inside wot folder, run it, it will create Aslains_WoT_Logs.zip file inside Aslains_Modpack folder.Post that .zip file EDIT: If you managed to install/run Aslains Modpack, if not Archiever.exe should be created anyway, i believe. How to report a bug or issue
  11. In future i plan on using this topic to share some XVM config parts or pieces of my own config. First on the list: info panels NOTE: Created and tested on 1920x1080, also with default XVM config in mind Quick install guide: 1) Copy .xc files and icons folder (if included) inside: res_mods/configs/xvm/<your config> folder 2) Add required formats: inside @xvm.xc and battleLabels.xc 3) Download extra .py (if required) inside: res_mods/configs/xvm/py_macro folder Setup on .py panels are: display duration: 3 sec / enabled on: allies, enemy & destroyed ALT: show player / Numpad 7: toggle on/off V0 - Minimal Info Panel (by Ress) (requires: only XVM, no extra py_macro) V1,V2,V3 - izeberg Info Panels (originally by Shtys) (Requires: infoPanel.py & info_panel_data.py (by Kotyarko_O - download link) V4 - masheene Info Panel (originally by Kriegstreiber) (Requires: infoPanel.py & info_panel_data.py) V5,V6 - ekspoint Info Panels (Requires: infoPanel.py & info_panel_data.py)
  12. Ress

    Gun sounds error

    I guess you installed UT Announcer and old 0.9.13 gun sounds? Banks Loader can be tricky with too many sound mods (especially those that depend on audio_mods.xml) But banks loader improved recently, so should be easy enough to fix this popup. Anyway inside "...mods/1.1.0" you should now have two KK91_oldGunSounds_v1.1 files, if you started you game at least once. Original KK91_oldGunSounds_v1.1.wotmod and one created by banksloader as "compatible" KK91_oldGunSounds_v1.1_BanksLoader_ing.wotmod To avoid this popup you can: A) Safely delete original KK91_oldGunSounds_v1.1.wotmod inside "...mods/1.1.0" B) Delete both KK91_oldGunSounds_v1.1 and KK91_oldGunSounds_v1.1_BanksLoader_ing inside "...mods/1.1.0" BUT first extract wpn_old.bnk and wpn_old.xml from KK91_oldGunSounds_v1.1_BanksLoader_ing.wotmod (using 7zip, Winrar, Winzip...) and put them inside "...res_mods/1.1.0/audioww"
  13. Ress

    Wot stops With black screen

    On the subject of game freeze, i wanna share my "unrelated" experience so far since 1.1.0 launch. (win7_64) First of...no crashes in game/garage.( lucky me i guess) BUT i did noticed issues when closing game or closing replay with XVM installed (even latest 7.7.2-dev). ~70% of time game just freeze on exit, and if i alt-tab game close from taskbar but process still stays open in task manager. And i can't re-launch game or replay until manually closing process. (also python shows no errors...typical) Without XVM or any mods installed i can open and close game/replay without any freezes. I know it's not fully related to the topic, still... In conclusion it's still too early to say that patch v1.1.0 (without any nano patches) or current XVM are fully stable. Solution #1: IT'S ALWAYS XVM, for first week or 2 (after new patch)...if possible, play without XVM even if it's stable (non-dev) version. Still too early... Solution #2 (on the actual subject): Update your drivers, also if you got issue after new drivers then rollback to previous version (i had issues with AMD drivers with missing trees, rolled back and waited for next version, problem solved / having up2date drivers doesn't always work)
  14. Ress

    win chance

    Well its not official update, at least Tey didn't update it. I was using budyx69 version for few months. link Someone posted "working" version i tried it and appears to be working. (aside from wrong signs) https://koreanrandom.com/forum/topic/42018-team-wn8-командный-wn8/?page=7 Still that script needs some update. (or it will die same way as colored chat) EDIT: also i am not getting any python errors related to mod_wn8_chance.py atm, so idk about that log
×

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.