GeneralGonzo

The question has already been asked.

I think only the mod-developer or a person that speaks russian, can do this for us.

There are two separate smoke counter mods in the pack.

Which one do you have?

If you got the one by MasaruKondera, please read the description.

My Post from Sunday was about the other one (Alt Hud).

To let everyone know:

The smoke counter (Alt hud) works fine with my keybindings.

It seems like this mod doesn't depends on a specific keyboard layout.

And last but not least, thank you Aslain for including it to your modpack.

No he isn't using a triple monitor setup and you were right.

After he deactivated this setting, all HUD elements showed up again and were in the correct position.

Thanks a lot Quaksen

Hello everyone,

a friend if mine just installed the WoWS modpack and has the problem,

that the minimap and some other HUD/GUI elements (e.g. the compass) are not showing up.

We soon ended our play session and i forgot the to ask him for screenshots.

However i still got his log file.

He tried reinstalling the minimap with shipnames a second time, just to be sure, but the issue persists.

The client was running at the moment but he restartet the game afterwards.

Which mods are causing this behaviour and are incompatible to each other?

_Aslain_logs.zip

That sounds like the usual chat bug.

It's in the game since i started playing the WoWS open beta.

The problem occurs in all of the official chat-channels ingame.

A Community Coordinator once said, that WG wants it that way.

Every now and then the chat-history will be erased to save bandwidth etc.

IMHO WG thinks that this minor bug isn't worth to get fixed.

funfact: the chat used in WOT doesn't behave like this,

cause it's build on a different backend.

Aslain is right.  You need to activate a filter.

Yep, no fog didn't worked there.

And a third map.
 

Problem: fog remover doesn't work <> anti-glare

Starttime: 12.02.2017 23:31

Ship: Baltimore

Map: Hotspot

Screenshots

python.log

_Aslain_logs.zip

Edit:

Sorry didn't expected #06 that fast. o.O

Will check it out.

thx again

Problem: fog remover <> anti-glare

Starttime: 12.02.2017 21:02

Ship: Belfast

Map: Northern Lights (North Winter)

Screenshots

_Aslain_logs.zip

python.log

Just saw that you already fixed the issue with the update #4.

That was super fast.

ty Aslain

I haven't encountered the bug since 0.6.0

Will let you know, when it happens again.

- Update -

Looks like the fog remover is working with most of the maps.

So far, i only had the issue on "Fault Line".

I think we just have to wait for a newer version of the mod.

Is it just me or is the fog remover didn't working?

I can provide logs, screenshots and/or replays if necessary.
 

I will test it, when (if) i start playing again.

Thanks for the reply.

I'm taking a break from WoWS anyway, so i think i can wait it out.

The reason is the RPF commander skill

What were they thinking, when they implemented this ****?!
Now the static gameplay will be even more static.

Hail to the mighty camper god  -.-

Is there any chance of getting a fully customizable smoke duration counter?

I binded nearly all consumables to completely different keys.

So for me, neither the qwerty nor the qwertz version works.

Or does anybody know how i can do this myself and which file

do i have to edit for this?

You opened this thread because you needed help.

Then you type in the shoutbox, that the problem is solved?  o.O

That's a strange method to letting us know.

- Update -

After another 20-30 battles i had the same bug again.

I can't reproduce it with a replay, cause i tab out of it and kill the game via the task manager.

After restarting the client, the game loads into the running battle.

The replay in the game directory starts at that point.

The issue occured after the second start of the client (after i switched to the other detection mod).

I had the same problem with the "old"-mod from blueman.

Most of the time it happens when i start the second or third match.

But then i can play the game for hours.

Next day the same procedure again.

The PC was shut down during the night.

Hope this helps to find the problem.

Sadly i can only attach the python log file, cause the aslain-zip clearly isn't in the main directory of WoWS.

Found them. It was so obvious  o.O

python.log

_Aslain_logs.zip

this forum section is english-only!

try to install the modpack with disabled antivirus software.

and you have a look at this page http://aslain.com/index.php?/topic/3270-how-to-report-a-bug-or-issue/

i had the same problem of being stuck in the loading screen.

so i switched to another detection mod.

blue man detection mod -> black citadel v4

now after ~20 battles i think the issue is gone.

at least it didn't showed up again.

which mod were you using cobrazax?