0.6.12 Bug Reports

[Ph3lan]

Captains,

 

Please share all bugs encountered in Public Test 0.6.12 below, using the following template:

 

1. Description

Clear and substantial description containing all necessary details.
Example: the cruiser Aoba: scout is inoperable.

 
2. Reproduction steps

A sequence of the player's actions which triggered the bug.
Example: 1. Select the cruiser Aoba 2. Enter the battle (Training or Random Battle). 3. Try to launch the scout.

 
3. Result

In-game experience resulting from the bug.
Example: When you press the scout activation button, you can hear the sound, but nothing actually happens. The aircraft stands still on the catapult.

 
4. Expected result

In-game experience which should have occurred if no bug is present.
Example: The scout has to be launched by the catapult.

 
5. Technical details
Example: Bug time: about 19:30 (UTC).Replay (attempt at 01:00), python.log, DxDiag.
 

If you encounter this error, please zip your ~\crashes\ folder, upload it to any online file storage and add the link to your report.

 

 

Cheers 

[Arto_McBoaty]

Had the game UI disappear after ending a Transylvania mission

[rnat]

1. Description

Sometimes Clan tag is not shown in Divison, which makes it impossible to launch clan battles.

Can be remedied by the affected player changing his status to "ready" (possible having to switch to "not ready" first)

 
2. Reproduction steps

Happens often but randomly.

Get in a division for clan battles and try to start match

 
3. Result

Can not start battle without (re-) selecting ship (on top of needing ship anyway ofc)

 
4. Expected result

Clan tag being shown and battle being able to start nomally.

 

 
5. Technical details
unknown

[eliastion]

1. Description

The firing-in-smoke concealment much worse than expected based on announcements as well as available in-game values.

 
2. Reproduction steps

1. Select Akizuki (possibly other smoke-capable ships as well)

2. Set a smoke screen and keep firing your main guns from within

 
3. Result

Detectability of the ship much higher than it should be (9,4 km on Akizuki)

4. Expected result

Detectability while in smoke and firing main guns should be equal to the "detectability by sea when firing main guns in smoke" value appropriate for the ship (here 2,4 km)

 
5. Technical details

Notice the values displayed thx to H key pressed (expected concealment after firing 2,4 km, the actual concealment after firing: 9,4 km), the circles on the minimap and the smoke circles clearly indicating that the ship remains within the active smoke screen.

[Jessa_Doom]

Hi WG & All

In the new public test we are testing the new Helloween scenario 

 

I've played the new Helloween battle and find it very awesome it look very gothic and steampunk'ish and outstanding more like this please.

 

Sorry to say i've have had an issue in the Jackal BB i've had the ship come to a stop when i've not touched the speed control and either way when firing HE shells i suddenly notice i'm firing AP shells and vice a versa without touching any buttons.

 

Also at the end when the Rasputin appears we hardly damage the ship and a minute or two later the battle ends and with all our ships firing at it very little damage is done and shortly after it showsthere's time to destroy the Rasputin as the game ends maybe some changes to both the rasputin that we have to destroy it before the ship we are escorting can enter the portal not the ship entering before destruction and a little change to the over armored Rasputin.        

Sorry no replays as i don't know if PTS has this option and dose not show in replays in main game.

[300ConfirmedKills]

1. Description

UI is inoperable after returning from a battle

 
2. Reproduction steps

Finish a battle. Return to the port screen. Attempt to use the UI elements do not respond to clicking. The only exception is the ability to select text entry areas, but no messages can be sent.

 
3. Result

UI elements do not respond to clicking. The only exception is the ability to select text entry areas, but no messages can be sent.

 
4. Expected result

UI can be used normally.

 
5. Technical details

No relevant details known.

[Admiral_Chunder]

Copy/pasted from Elastion's post. Smoke detection bug with Kiev on PTS.

 

1. Description

The firing-in-smoke concealment much worse than expected based on announcements as well as available in-game values.

 
2. Reproduction steps

1. Select Kiev (possibly other smoke-capable ships as well)

2. Set a smoke screen and keep firing your main guns from within

 
3. Result

Detectability of the ship much higher than it should be (looks to be exactly the same as non smoke detection range)

4. Expected result

Detectability while in smoke and firing main guns should be equal to the "detectability by sea when firing main guns in smoke" value appropriate for the ship.

 
5. Technical details

Nothing to add.

[TheCinC]

On 10/7/2017 at 0:25 AM, 300ConfirmedKills said:

1. Description

UI is inoperable after returning from a battle

 
2. Reproduction steps

Finish a battle. Return to the port screen. Attempt to use the UI elements do not respond to clicking. The only exception is the ability to select text entry areas, but no messages can be sent.

 
3. Result

UI elements do not respond to clicking. The only exception is the ability to select text entry areas, but no messages can be sent.

 
4. Expected result

UI can be used normally.

 
5. Technical details

No relevant details known.

 

Exact same problem.

Did a battle in Akizuki, exited early, selected Kagero, finished battle, return to port, no UI.

Clicking on the location where normally ships would be displayed, nothing happens, so can't select a different ship.

Same for clicking on the spot where "Battle" should be.

Only thing that seems to work is to press "Esc".

[Jessa_Doom]

Hi WG & All

 

A possible detection glitch/bug and have reported this before in main gameplay via a ticket months back then many players in battles were in chat about how were they getting spotted that quickly from start and it seems nothing was done.  

 

In most Random Battles no matter what ship i'm in i'm finding the just after start in being hit with continuous accurate fire from most of the enemy team and i'm not detected or there's a plane even no radar indications and being wiped out without seeing the enemy ships even if this type of fire was blind fire it's too accurate even for that this is not good at all.

 

Even if i fire back at where i see the fire coming from i could not get a hit let alone the same accurate hit rate of fire and even with all my team around me i'm still the one being hit it's like i'm the only ship there and most of the incoming fire is coming from ships that should not have the range it's getting damn annoying especially if my team don't hit in the same way.

 

Is the detection being abused by a cheat or is there a glitch/bug that i am detected but the indications are not showing.  

 

To add to this i did suggest that the start line be brought back closer to back of map nearer to the borders so those ships with the higher detection can at least get moving without getting incoming fire by unseen ships and also if a ship is behind an island with no other forms of being detected it should be undetected a case if you can see it you can't hit it and this is not what is happening in the game even that is a issue.     

[Zag32]

On ‎2017‎-‎10‎-‎06 at 10:19 AM, eliastion said:

1. Description

The firing-in-smoke concealment much worse than expected based on announcements as well as available in-game values.

 
2. Reproduction steps

1. Select Akizuki (possibly other smoke-capable ships as well)

2. Set a smoke screen and keep firing your main guns from within

 
3. Result

Detectability of the ship much higher than it should be (9,4 km on Akizuki)

4. Expected result

Detectability while in smoke and firing main guns should be equal to the "detectability by sea when firing main guns in smoke" value appropriate for the ship (here 2,4 km)

 
5. Technical details

Notice the values displayed thx to H key pressed (expected concealment after firing 2,4 km, the actual concealment after firing: 9,4 km), the circles on the minimap and the smoke circles clearly indicating that the ship remains within the active smoke screen.

 

 

Concealment bug confirmed. Just played Akizuki, was sitting in smoke while the nearest ship was 6km away. Still was spotted. BTW with concealment mechanic changes it would be nice if WG gave us free perk reset, or at least bonus price for captain retraining.

[Admiral_H_Nelson]

On 06/10/2017 at 9:19 AM, eliastion said:

1. Description

The firing-in-smoke concealment much worse than expected based on announcements as well as available in-game values.

 
2. Reproduction steps

1. Select Akizuki (possibly other smoke-capable ships as well)

2. Set a smoke screen and keep firing your main guns from within

 
3. Result

Detectability of the ship much higher than it should be (9,4 km on Akizuki)

4. Expected result

Detectability while in smoke and firing main guns should be equal to the "detectability by sea when firing main guns in smoke" value appropriate for the ship (here 2,4 km)

 
5. Technical details

Notice the values displayed thx to H key pressed (expected concealment after firing 2,4 km, the actual concealment after firing: 9,4 km), the circles on the minimap and the smoke circles clearly indicating that the ship remains within the active smoke screen.

I had the exact same problem with Akizuki in three battles today.

 

FFS wargaming. a MAJOR change to the game and you still manage to screw it up this badly!

Don't you do ANY testing before throwing the code onto Public Test?

[Mike_Chaffin]

 After playing the Transylvania whatnot the UI seemed to crap out.

 

Logging back out and in, same....

[Silver_Leviathan]

Round 2... and this simply bug, no resolve!

Is a trivial error writing of a variable, they wrote 9 instead of 2, understandably human error, but easily correctable if someone was reading the report!

 

There are so many other active bugs, but considering that many bugs reported in the previous patches have not even been considered, I wonder what is the public test, (just to see the stats and logs of the various servers)? Why do I waste time reporting bugs? We have to write reports in the Russian forum for her to read from the WG programmers?

 

 

On 6/10/2017 at 10:19 AM, eliastion said:

1. Description

The firing-in-smoke concealment much worse than expected based on announcements as well as available in-game values.

 
2. Reproduction steps

1. Select Akizuki (possibly other smoke-capable ships as well)

2. Set a smoke screen and keep firing your main guns from within

 
3. Result

Detectability of the ship much higher than it should be (9,4 km on Akizuki)

4. Expected result

Detectability while in smoke and firing main guns should be equal to the "detectability by sea when firing main guns in smoke" value appropriate for the ship (here 2,4 km)

 
5. Technical details

Notice the values displayed thx to H key pressed (expected concealment after firing 2,4 km, the actual concealment after firing: 9,4 km), the circles on the minimap and the smoke circles clearly indicating that the ship remains within the active smoke screen.

 

[Spunyarn]

1. Description

Halloween Commander name not displayed correctly when Halloween Camouflages hidden.

 
2. Reproduction steps

After getting the permanent camouflage for the Saint Louis from a Halloween Container I checked that switching the display of this off worked to make the Saint Louis look normal rather than like an Igor.

 
3. Result

Ship changed appearance correctly but when I selected one of the Halloween special-ships there was a strange name with lots of numbers, no portrait, and the rank was displayed as Aquafarmer. Switching the display of Halloween camouflages back on fixed the problem.

 
4. Expected result

A normal looking name and rank and a portrait.

 

====

 

1. Description

Halloween 2017 port not displayed correctly after scenario

 
2. Reproduction steps

Played the 2017 scenario and when I died I exited back to port.

 
3. Result

Port was not displayed correctly. Most of it was missing. I could see trees floating in mid-air. Switching to another port and switching back corrected the problem

 
4. Expected result

To be able to see the port normally.

 

EDIT: Might have been after claiming the pumpkin container as that was when the error just occurred for me, rather than after the scenario. Player name was also missing for dropdown list on port screen and when I went into "Profile". 

[Live85]

On 7/10/2017 at 0:25 AM, 300ConfirmedKills said:

1. Description

UI is inoperable after returning from a battle

 
2. Reproduction steps

Finish a battle. Return to the port screen. Attempt to use the UI elements do not respond to clicking. The only exception is the ability to select text entry areas, but no messages can be sent.

 
3. Result

UI elements do not respond to clicking. The only exception is the ability to select text entry areas, but no messages can be sent.

 
4. Expected result

UI can be used normally.

 
5. Technical details

No relevant details known.

 

Confirmed. Had to close and restart the client two times because of this.

[rnat]

Textures missing from Event-port and player name not displayed after doing halloween-scenario.

Spoiler

 

Switching ports and back fixes texture problem but name is still not displayed.

[eliastion]

The problem described here

 

Still not resolved in playtest Round 2.

[Admiral_H_Nelson]

4 hours ago, eliastion said:

The problem described here

 

Still not resolved in playtest Round 2.

+1

 

The changes to detection mechanics wrt smoke are the most significant in patch 0.6.12.

 

WHY ON EARTH DID YOU START ROUND 2 OF PUBLIC TEST BEFORE IT WAS FIXED!

 

Anyone who has worked in a professional Software Testing Team (as I have) will be laughing at Wargaming for this shoddy effort.

 

You only need one game  - ONE FRIGGING GAME - to discover this bug. How on earth did it ever make it through internal "testing"?

[Yankmyplank]

Ship Z52 laid smoke and remained still, hydro activated and undetected, fired torpedoes and was immediately spotted, closest ship was 9km.

[Spunyarn]

1. Description

Trees floating in mid-air in second Halloween Scenario.

 
2. Reproduction steps

Playing the scenario and being inside the filth.

 
3. Result

Saw trees floating in mid-air but even when I ran aground I could not see the island those were on, which made it harder to judge where the coast was since my only reference was the minimap.

I think there are also buildings on that island and that those were not visible.

 
4. Expected result

To be able to see the island in the same way as can see enemy ships within the filth; fairly clearly if both of you are within it and more as a silhouette if you are outside it and they are within it. 

[peachpest]

On ‎05‎/‎10‎/‎2017 at 7:39 PM, Ph3lan said:

 

If you encounter this error, please zip your ~\crashes\ folder, upload it to any online file storage and add the link to your report.

 

 

 

Ok so while this is not strictly related to the PTS I want to say:

 

On the Live server In the 13 days of this month already I have had this exact crash 17 times already and since the 3/8/17 (3rd August) iv had this crash 47 times ...yes read that again 47 times......this is beyond a joke and I have no idea how to go about fixing it on my end.

 

my crash files:

https://www.dropbox.com/s/fez9ptirghvg3fe/crashes.7z?dl=0

[omfalos]

Hello,

 

Got this bug during new Halloween scenario:

 

1. Description

Rasputin spawned under an island at F2 and jumped up and down and was loosing health very fast.

 
2. Reproduction steps

It happend only once during my play.

 
3. Result

He was out of the game faster.

 
4. Expected result

Rasputin should be above water and able to be fired upon.

 
5. Technical details
22:06 12.10.2017

[Jessa_Doom]

Hi WG

Shortly after start of the Halloween advent 2 i'm in the Battleship and after the first wave of enemy ships i got a bug that and hardly getting a hit all the main guns and torpedoes tubes on the ship would not fire it was like they all became incapacitated and at the rectal there was a timer that was saying repair 12+ seconds but stayed at 12 as the time above the 12 seconds got to 12 it reset to 13-15 seconds and even my repair and shield would not work either and for nearly a minute i had no main fire and as a result nearing enemy just slaughtered me and shortly after that the first tower was attacked by one ship destroying the tower and barely a shot hit it nor did the filth.

 

If it takes one salvo from an enemy ship to destroy a tower and we have to save at least two then we have no chance of winning that secondary task and like the first halloween part i'm yet to get 5 stars or to know if anyone have got to 5 stars i'm sure it can be done if the teams were any way good but not every team is that good or do what is asked of them like one battle i played one DD shopped maybe went AFK and a BB sailed far away from battle without firing a shot that player was a coward thinking by doing that we win NOT!.

 

Below a suggestion of slight improvements.

 

Maybe if there were 10 in the team and 4 towers that give out a little less power each to make up for the fourth tower also if all the enemy ships came from the portal or in the filth and not spawn behind the first tower or in the middle of the map we might stand a chance.         

[JohnPaulJones1954]

1. Description

The screen locked up after battle before going to results.

 

2. Reproduction steps

Finished Random Battle and screen locks up

 
3. Result

Nothing happens

 
4. Expected result

The game should continue into Battle Results

 
5. Technical details
 Bug time: about 04:00 (UTC).  I had to go to task manager end program.  Will notify if happens again!

[ShuggieHamster]

people having problems claiming their rewards for testing done on the PT server. this is now the 3rd update that this has been happening.

 

see here for a thread on reddit where people are voicing problems. Tickets have been raised before but nothing has been done/people fobbed off with - you got your rewards, the server says so .... but rewards dont seem to be appearing at client side.