HockeyPhool

On screenshot it's medium panel #2, switch it to #1

Aslain, I'm not sure I understand.  I chose 'medium #1' when I installed the modpack, but WoT is displaying 'medium #2'.  For some reason, the modpack is creating a corrupt '_Aslain_logs.zip' file (I cannot open it with any ZIP utility).  I'm attaching _Aslain_Installer_CompList.log which shows my selection.  I'm also attaching the 'playersPanel.xc' config file, which also shows that the start mode should be 'medium', not 'medium2'.  Yet the screenshot I attached (taken in-game) clearly shows 'medium #2'.

For what it's worth: I have selected this same medium panel start mode for a long time.  Yesterday I uninstalled WoT and reinstalled it to clear up some video driver issues, then I reinstalled 4.5.23_99 (on top of the old res_mods folder, which I preserved).  I always choose a clean install, but I do not clear the WoT cache.

I can try reinstalling the modpack again to confirm the behavior.

HockeyPhool

_Aslains_Installer_CompList.log

playersPanel.xc

In 4.5.23_99, the player panel 'medium #1' is displaying tank names instead of player names (as shown in the preview in the installer).

I'm attaching my _Aslain_logs.zip.  For some reason I cannot upload my python.log.

_Aslain_logs.zip

MegaCrun, please read "How to report a bug or issue" (pinned at the top of this forum).  If you don't describe the problem accurately *and* include the requested logs, there's no possible way for Aslain or anyone else to diagnose the problem.

Kind regards,

HockeyPhool

Andrea, I don't believe the capture bar is capable of indicating *which* base is being captured in Domination mode.  Is this something that you know was working in a previous version?  I don't play any of the Domination mode games, so I haven't seen any problem like this.

the capture bar is not telling me wich cap is being captured but only that there is one enemy in the circle.

Hello Bodalex,

Thank you for including log files with your bug report.  I examined the 'python.log' file to see if there was any clue about your hangar issue, but I think all the messages were logged after you emptied your 'res_mods' folder.  I also looked at the Aslains log files but I did not see anything obviously wrong.

Have you tried installing the latest version of the modpack to see if the behavior is different?  I would suggest that you do that, and if the bug still occurs then submit new logs before you remove your 'res_mods' folder.  That will ensure that Aslain has the best available information to look at when he returns from vacation.

Regards,

Scott (HockeyPhool)

(First, excuse me for possible mistakes, english is not my first langage. Thanks).

 

Hello

 

When I install Aslain's Modpack it cause a bug in the garage (as you can see on the screenshot).

I tried to uninstall and install again but i didn't success. I have to empty my res_mods folder to play.

 

Hope you can help me

Bodalex

Hello andrea,

Please read the topic How to report a bug or issue.  Aslain probably cannot diagnose the problem unless you attach your _Aslain_logs.zip and python.log files (found in your WoT directory.

When you describe the problem you're seeing, it would help if you would state what version of the modpack you installed, and what relevant mods you selected (such as the crosshairs, in this case).

Kind regards,

HockeyPhool

The multi-lined carousel also has some extra filters (the tank filter icon, IIRC).  That filter has a 'hide Domination tanks' option.  Make sure that isn't selected.

Ah I see.

But there is a checkbox in carousel - don't you have any idea? It seems it is the same as for Domination mode.

Install engine sounds after unpacking gun sounds. Should work.

Yeah, I guess that would be a good plan.  :-)  I'm reinstalling WoT clean right now, though.  

I prefer Kriegstreiber's sound mods, any way.  I'll wait until they're ready for 9.8.

Thanks!

Update: I installed the latest GnomeFather's gun sounds 'res_mods' folder.  I didn't get stuck at the battle loading screen, but following his directions has the side-effect of deleting the engine sounds as well.  

Thanks for the info, altobe!  Trying it out right now.

The problem lies with Gnomefather guns. There is a hotfix that he released that will fix this issue. I'll attach a link to his blog.

 

http://gnomefather.blogspot.no/2015/05/hr-gun-sound-mod-1963.html

 

Go to this link and read the post. It explains that you install the latest gnome release (aslains installer), then delete the bad files and apply the fix. Its explained there. This works as I tried it.

 

Otherwise you just cant use gnome guns till aslain fixes it in the installer.

update: I reinstalled 4.4.1_98 and selected MeltyMap's crosshair mod.  I started another battle and encountered the same issue.  FWIW both battles were in my Centurion Mk 7/1.

I'm attaching updated logs, in case they are helpful.

_Aslain_logs.zip

python.log

I found this while installing 4.4.1_98:

Attaching _Aslains_logs.zip

_Aslain_logs.zip

I just reported this problem as well: http://aslain.com/index.php?/topic/2567-stuck-at-battle-loading/

I just reported this problem as well: http://aslain.com/index.php?/topic/2567-stuck-at-battle-loading/

I have modpack v4.4.1 installed.  I played 4 or 5 battles without issues, but on my last battle my client remained stuck at the battle loading screen.  At the point where I should have seen the countdown timer screen, I could see the OTM's for my allies, and they would move around the battle loading screen as I moved my mouse:

Once the battle started I could hear the sounds of the battle, and see tanks in the roster go dark as they were destroyed. I could see the spotting indicator on screen.  When my own tank took hits I could see the damage panel being updated as well.

I'm attaching _Aslains_logs.zip, python.log, and xvm.log.  I could not see anything in they python.log that points to a particular mod, however.  I will try selecting a different crosshair mod (currently using J1mb0's with Sword of Damocles SPG crosshairs).

_Aslain_logs.zip

python.log

xvm.log

FWIW I'm not having any issues with 4.3.8.  I'll upload my _Aslain_logs.zip in case any of you having problems want to compare configs.

_Aslain_logs.zip

I can confirm this bug.  I use the 'vanilla radial menu with reload on "C" key':

_Aslain_logs.zip

python.log

RadialMenu.xml

It would help if you indicated *which* radial menu mod you selected, and if you attached your logs (_Aslains_logs.zip, python.log).

same for me.

Did radial menu change the format? I tried using my old config, and my commands don't work any more. I tried to edit the new config (added <text> entry), but it doesn't get displayed either.

+1 for the clear descriptions!

Using a certain mod that cant be mentioned makes this error occur nearly every battle. Using the legal auto aim+ in combination with custom crosshairs also produces the error in varying forms every few battles.

 

In tanks it happens one of three ways for me:

BTW: if you use AutoEquip it's a good idea to save a master copy of your AutoEquip.xml configuration file.  I have a master copy in a different directory, and I use WinMerge to copy differences into the mod's config file.  

Aslain, that seems like a debug message and not necessarily an error.

I really wish I could see the source code! :-)

I always see this error, but why it shows up, no clue.... maybe some other mod is causing it but you barely selected any mods to be installed... 

 

NOTICE: [NOTE] (scripts/client/Avatar.py, 1074): [iNIT_STEPS] Avatar.vehicle_onLeaveWorld

Will do.  Thanks!

Aslain, you did add it in 4.3.2_97.  I do not install any mods outside of your modpack.

EDIT: I realize now I meant *locastan's* sessions stats, not YasenKrasen.  My apologies

This sounds like another issue of the problem reported in the 'perspective locked' and 'turret and sniper freeze' topics.  Aslain - perhaps you could lock those two topics and redirect people to 'perspective locked' topic?

No worries, Aslain.  I will try without 'big hotkey numbers' and only 'letter shell icons'.  It's not a big deal, considering the other nasty bugs we're chasing