Jump to content
MrConway

Bug Reports

56 comments in this topic

Recommended Posts

[WG-EU]
WG Staff
1,864 posts
2,152 battles

Dear captains,

 

Please share all bugs encountered in the current update 0.6.15 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.

 

565152Sanstitre.png

Edited by MrConway
fixed version

Share this post


Link to post
Share on other sites
[BYOB]
Players
2,688 posts
9,853 battles

Issue was caused by mod incompatibility.

 

 

 

 

Edited by Aragathor
Problem solved.

Share this post


Link to post
Share on other sites
[CATS]
Players
13,610 posts
10,385 battles

1. Description

HSF/ARP commanders don't have their unique voiceovers in battle.

 
2. Reproduction steps

Enter battle with HSF Harekaze or ARP Ship

 
3. Result

Voiceovers correspond with each ship's base nation rather than the commander (Japan/Germany).

 
4. Expected result

HSF/ARP voiceovers to play.

 
5. Technical details
- Voiceover language is set to English (United Kingdom).

- Voiceover modification is set to National.

- I have HSF/ARP set to visible in the "things i (dont) want to see" menu.

 

 

 

  • Cool 2

Share this post


Link to post
Share on other sites
Players
16 posts
950 battles

Can someone help me please, i try to start up WoW but i cant get passed the log on screen  it just does not update to the new version.

Please check below. It has been like this all day 

image.thumb.png.936aeed5391ab5ba0509b3af09b0307d.png

Share this post


Link to post
Share on other sites
[BRI_Z]
Players
38 posts
5,070 battles

I will continue to post this after every update until it is fixed. I would really like some help or for this to be taken seriously as I love the game but can't bear playing it with this issue.

1. Description

  •  When playing in a division the game constantly crashes to desktop with a critical error. This has been happening for the best part of 6 months and it is completely turning me off the game. This issue has survived two fresh OS installs, endless different drivers and clean driver installs after using DDU and multiple windows updates and game patches. It is so unbelievably frustrating as I mostly play in a division. I always check the game logs after a crash and it doesn't show anything useful before the crashes. My PC is rock steady with all other games (even this one during solo play) apart from WOWS when in a division.

2. Reproduction steps

  •  Play a game in a division. It used to only happen when outside of matches, i.e. loading into battle, exiting battle, interacting with the port. Now it happens in game as well. It happens randomly and something I will get one crash a night and sometimes a crash every other game. I will include the crashes folder and you can see that tonight I had a crash and then as I loaded into the game it crashed again within a minute. I cannot emphasise how bad this issue is for the playability of the game.

3. Result

  •  Crash to desktop with critical error.

4. Expected result

 ......................
5. Technical details

  • Playing with the game in fullscreen windowed seemed to help for a while but now it crashes just as often after this patch.
  • As you can see from the python log, it shows nothing (that I can see) before crashing. This was the instance I mentioned earlier where I didn't even manage to load back into the game without a crash.

5a3c520ba002c_2017-12-2200_27_15-python.log-Notepad.thumb.png.a23640870ed95e01a0debd9e7ae2a009.png

 

Here is the zipped version of my crashes folder, it doesn't seem to capture every crash.

crashes.zip

Share this post


Link to post
Share on other sites
[BRI_Z]
Players
38 posts
5,070 battles

Further to my post last night I have since had a few crashes while playing solo.

 

I tried running many of the steps that I know WG support suggest and It has made no difference. I have also tried running in DX9 as well as running most of the fixes that have been suggested in the MANY threads on the forums. WG know this is an issue but they do nothing to fix it. This has been going on for months and no one has been able to fix it or find a workaround that actually works. I am incredibly frustrated having put a lot of effort and money into the game and I am unable to play it.

Share this post


Link to post
Share on other sites
[BRI_Z]
Players
38 posts
5,070 battles

After having no luck I resorted to doing a fresh install of the game. I played 3 games after the install and experienced a crash in all three.

 

I decided to run the WG Check application and it found damaged files (bearing in mind I had only installed the game 30 minutes prior). The python log is still no help, all seems fine until it shows "crashed", and the crashes folder may be useful to the developers but shows nothing intelligible to a normal user.

 

Spoiler

5a3d64549cf2a_2017-12-2219_57_02-WGCheck.thumb.png.2b265596a8be42fedf584128324845fa.png

 

Share this post


Link to post
Share on other sites
Beta Tester
3,671 posts
12,833 battles

#1 - Torpedo Bug

 

1. Description

  • When trying to fire torpedoes mouseclicks are ignored and torpedoes are not immediately launched
  • a few seconds later torpedoes are launched, but not in the direction they were aimed at and at which the target marker points, but in a different direction

 
2. Reproduction steps

  • Playing DDs and launching torps. Bug happens not each time when torps are fired, but randomly it seems

 
3. Result

  • Torpedo launch was wasted and the target was not sunk. Sometimes resulting in my DD getting sunk instead and a lost battle

 
4. Expected result

  • Torpedoes are supposed to be launched in the direction that they are aimed at and hopefully sink the target.

 
5. Technical details

  • Several times during different battles since the last update; not more than once per battle though (If I remember correctly)

 

#2 - Result screen not displayed properly

 

1. Description

  • when I enter a new battle immediately after getting sunk (= not waiting until the battle is over) and the first battle ends before the new battle does, the result screen for the new battle is not shown when it ends
  • Both result screens can only be seen through the message tab 

2. Reproduction steps

  • Play a battle. Get sunk. Leave battle. Enter new battle. Play this battle to the end.

 
3. Result

  • The battle ends and after ashort pause the game goes directly to the harbour screen

4. Expected result

  • Result screen for the battle that just ended is supposed to be shown

 
5. Technical details

  • several times during play since the last update; each time when a new battle was entered before a previous battle had ended
  • Cool 1

Share this post


Link to post
Share on other sites
[FAITH]
Players
426 posts
14,825 battles

I have the same bug as @Deckeru_Maiku so borrowing his bug report. This bug is GAME BREAKING I must add, it happens very often and gets one killed more then once. Im very disappointed in WG with this patch, it crashes, have game breaking bugs, its like taking 2 steps backward in development.

 

#1 - Torpedo Bug

 

1. Description

  • When trying to fire torpedoes mouseclicks are ignored and torpedoes are not  launched
  • 10-15 seconds later they can be launched and they can go in another direction then where you aimed.

 
2. Reproduction steps

  • Playing Mogami, Ibuki, Zao (any ship with torps probably works) and launching torps. Bug happens not each time when torps are fired, but randomly it seems. My first game today and yesterday it happened, it have happened many times today, now I rage quieted because my Zao just refuses to fire torps.

 
3. Result

  • Torpedo launch was wasted and the target was not sunk. One often die or take heavy damge from targets that would have been sunk before they could react.

 
4. Expected result

  • Torpedoes are supposed to be launched in the direction that they are aimed at and hopefully sink the target.

 
5. Technical details

  • Several times during different battles since the last update.

 

Share this post


Link to post
Share on other sites
[HEROS]
Players
3 posts
5,548 battles

Game and entire computer freeze in startup while attempting to load the game. Several times over. 
Works after running "check and repair-tool" but back to freezing next time I start the game. 

 

Can't take a screenshot of it since the everything freezes.

Hope you can fix it

Share this post


Link to post
Share on other sites
Players
2 posts
3,324 battles

Confirming torpedo bug, same as Deckeru_Maiku and G3Virus.

 #Torpedo bug

 

1. Description.

 

- When trying to launch torpedoes, mouseclicks are ignored and torpedoes do not fire.

- If you try 10—15 seconds later, it is possible to launch them.

 

2. Reproduction steps.

 

- I can reliably reproduce this with ARP Takao. Start the game, wait for the torpedoes to be ready, try to launch.

 

3. Result.

 

- Torpedoes are not launched. Since you have to expose your side in order to launch them, this leaves you in a vulnerable position while you are pumping the mouse button, hoping that the damn things will fire.

 

4. Expected result.

 

- Torpedoes, once ready, should be launched upon a mouse click.

 

5. The issue does not occur every time, but for me it happens at least several times per game.

Share this post


Link to post
Share on other sites
Players
2 posts
6,620 battles

Crash on loading screen

 

1. Description:

 

-Game crashed several times on the loading screen before the battle.

 

2.Reproduction steps:

 

-Seem to happen every time almost every time I try to load in a battle.

 

3.Result:

 

-Game freezes on loading screen & gives one of the followin crashreport, & it can't be terminated in the task manager.

 

4.Expected Result:

 

-The battle loading in properly.

 

5. Details:

 

-The problem appears since 6.15 , even full re-install didn't help.

-The bug completly prevents me from playing the game properly & if its not get fixed in 5 days from patch it prevent me from doing Aftvent mission too.

 

Crash report:

 

Application E:/World_of_Warships/WorldOfWarships.exe crashed 12.22.2017 at 11:19:03

Message:
The BigWorld Client has encountered an unhandled exception and must close (EXCEPTION_ACCESS_VIOLATION : 0xC0000005 @ 0x018ACB09) (Read @ 0x00000006)
Current thread #3884 native trace:
(0) : WorldOfWarships.exe!0x018ACB09
(0) : WorldOfWarships.exe!0x017992A0
(0) : WorldOfWarships.exe!0x01799BB1
(0) : WorldOfWarships.exe!0x0178EEE7
(0) : WorldOfWarships.exe!0x0178F3FF
(0) : WorldOfWarships.exe!0x010813FF
(0) : WorldOfWarships.exe!0x01329C54
(0) : WorldOfWarships.exe!0x01329C21
(0) : WorldOfWarships.exe!0x01329BE0
(0) : WorldOfWarships.exe!0x0132210B
(0) : ucrtbase.DLL!0x67B2E87F
(0) : KERNEL32.DLL!0x75F27C04

System info:
    OS Name: Windows 8.1 or later
    OS Version: 6.6
    OS Architecture: x86_64


Memory info:
    Virtual memory: 1589640Kb/4194176Kb (38%)
    Working set (process physical memory): 1146904Kb/4194176Kb (27%)
    Commit charge (working set + process page file usage): 1207812Kb/4194176Kb (28%)
    Global physical memory: 2738728Kb/8293548Kb (33%)
    Global commitable memory (physical + pagefile): 3145932Kb/9604268Kb (33%)

 

 

 

 

 

 

 

Share this post


Link to post
Share on other sites
Players
33 posts
10,384 battles
On 20/12/2017 at 7:59 PM, MrConway said:

Dear captains,

 

Please share all bugs encountered in the current update 0.6.14 below, using the following template:

 

First: 0.6.15 Feedbak thread link this topic for bug report, yet it is for 0.6.14

On 22/12/2017 at 9:39 PM, Deckeru_Maiku said:

#1 - Torpedo Bug

 

1. Description

  • When trying to fire torpedoes mouseclicks are ignored and torpedoes are not immediately launched
  • a few seconds later torpedoes are launched, but not in the direction they were aimed at and at which the target marker points, but in a different direction

 
2. Reproduction steps

  • Playing DDs and launching torps. Bug happens not each time when torps are fired, but randomly it seems

 
3. Result

  • Torpedo launch was wasted and the target was not sunk. Sometimes resulting in my DD getting sunk instead and a lost battle

 
4. Expected result

  • Torpedoes are supposed to be launched in the direction that they are aimed at and hopefully sink the target.

 
5. Technical details

  • Several times during different battles since the last update; not more than once per battle though (If I remember correctly)

Second: same here. When will be communicated that this bug makes torpedo boat (sometimes) unplayable during the whole game? Because loosing game after dealing no damage, getting reported, even team killing with no intention to do so, etc... seems rather important enough to warn people about this issue. For instance, within an annoucment on the General News front page (instead of new premium content), or within the game in a popup (like those daily after-battle adds to buy premium time because "we want to thank you by making you giving us money"). I'm sorry I can't give you a replay, as I had to re-install the game because of an unreleated issue (crash in the queue when a game is found, which BTW, is still a thing, see below in the spoiler), but I heard you manage to reproduce the bug (from Reddit). 

So, any news about that? When can we play DD again?

 

Bug report:

Spoiler

Application D:/WG/World_of_Warships_EU/WorldOfWarships.exe crashed 12.22.2017 at 21:58:32

Message:
The BigWorld Client has encountered an unhandled exception and must close (EXCEPTION_ACCESS_VIOLATION : 0xC0000005 @ 0x0070AD9B) (Write @ 0x00000000)
Current thread #2536 native trace:
(0) : WorldOfWarships.exe!0x0070AD9B
(0) : WorldOfWarships.exe!0x00DF1D79
(0) : WorldOfWarships.exe!0x0070A7C4
(0) : WorldOfWarships.exe!0x00DD18B9
(0) : WorldOfWarships.exe!0x00D897DB
(0) : WorldOfWarships.exe!0x00D886B8
(0) : WorldOfWarships.exe!0x00D89634
(0) : WorldOfWarships.exe!0x006DE5B4
(0) : WorldOfWarships.exe!0x00DC7280
(0) : WorldOfWarships.exe!0x00DCA2FF
(0) : WorldOfWarships.exe!0x00DEF9C4
(0) : WorldOfWarships.exe!0x0070A7C4
(0) : WorldOfWarships.exe!0x00DD18B9
(0) : WorldOfWarships.exe!0x00D8999A
(0) : WorldOfWarships.exe!0x00D88729
(0) : WorldOfWarships.exe!0x00D89634
(0) : WorldOfWarships.exe!0x006DE5B4
(0) : WorldOfWarships.exe!0x00DC7280
(0) : WorldOfWarships.exe!0x00DCA2FF
(0) : WorldOfWarships.exe!0x00DEF9C4
(0) : WorldOfWarships.exe!0x0070A7C4
(0) : WorldOfWarships.exe!0x00DD1554
(0) : WorldOfWarships.exe!0x00DCA500
(0) : WorldOfWarships.exe!0x00DEFD95
(0) : WorldOfWarships.exe!0x0070A7C4
(0) : WorldOfWarships.exe!0x00DD18B9
(0) : WorldOfWarships.exe!0x00D897DB
(0) : WorldOfWarships.exe!0x00D88729
(0) : WorldOfWarships.exe!0x00D89634
(0) : WorldOfWarships.exe!0x006DE5B4
(0) : WorldOfWarships.exe!0x00DC7280
(0) : WorldOfWarships.exe!0x00DCA2FF
(0) : WorldOfWarships.exe!0x00DEF9C4
(0) : WorldOfWarships.exe!0x0070A7C4
(0) : WorldOfWarships.exe!0x00DD18B9
(0) : WorldOfWarships.exe!0x00D897DB
(0) : WorldOfWarships.exe!0x00D88729
(0) : WorldOfWarships.exe!0x00D89634
(0) : WorldOfWarships.exe!0x006DE5B4
(0) : WorldOfWarships.exe!0x00DC7280
(0) : WorldOfWarships.exe!0x00DCA2FF
(0) : WorldOfWarships.exe!0x00DEF9C4
(0) : WorldOfWarships.exe!0x0070A7C4
(0) : WorldOfWarships.exe!0x00DD18B9
(0) : WorldOfWarships.exe!0x00D897DB
(0) : WorldOfWarships.exe!0x00D88729
(0) : WorldOfWarships.exe!0x00D89634
(0) : WorldOfWarships.exe!0x006DE5B4
(0) : WorldOfWarships.exe!0x00DC7280
(0) : WorldOfWarships.exe!0x00DCA2FF
(0) : WorldOfWarships.exe!0x00DEF9C4
(0) : WorldOfWarships.exe!0x0070A7C4
(0) : WorldOfWarships.exe!0x00DD18B9
(0) : WorldOfWarships.exe!0x00D897DB
(0) : WorldOfWarships.exe!0x00D9B428
(0) : WorldOfWarships.exe!0x00DF516B
(0) : WorldOfWarships.exe!0x00DF88B8
(0) : WorldOfWarships.exe!0x00DF8CD4
(0) : WorldOfWarships.exe!0x00C0F43F
(0) : WorldOfWarships.exe!0x005013FF
(0) : WorldOfWarships.exe!0x007A9C54
(0) : WorldOfWarships.exe!0x007A9C21
(0) : WorldOfWarships.exe!0x007A9BE0
(0) : WorldOfWarships.exe!0x007A210B
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

System info:
    OS Name: Windows 8.1 or later
    OS Version: 6.6 
    OS Architecture: x86_64


Memory info:
    Virtual memory: 2729476Kb/4194176Kb (66%)
    Working set (process physical memory): 1971188Kb/4194176Kb (46%)
    Commit charge (working set + process page file usage): 1689248Kb/4194176Kb (40%)
    Global physical memory: 4913380Kb/8285648Kb (59%)
    Global commitable memory (physical + pagefile): 6440792Kb/16674256Kb (39%)


System info:
COMPUTERNAME = CHRISTOPHE-UX
APPLICATION = "D:\WG\World_of_Warships_EU\WorldOfWarships.exe" 
4 PROCESSOR(S) = 0 - 6 3d04
DISPLAYDEVICE 0 = \\.\DISPLAY1, Intel(R) HD Graphics 5500, PCI\VEN_8086&DEV_1616&SUBSYS_183D1043&REV_09
DISPLAYDEVICE 1 = \\.\DISPLAY2, Intel(R) HD Graphics 5500, PCI\VEN_8086&DEV_1616&SUBSYS_183D1043&REV_09
DISPLAYDEVICE 2 = \\.\DISPLAY3, Intel(R) HD Graphics 5500, PCI\VEN_8086&DEV_1616&SUBSYS_183D1043&REV_09


Extended info:
Current thread #2536 native trace:
(0) : WorldOfWarships.exe!0x0079262D
(0) : WorldOfWarships.exe!0x00791BE6
(0) : WorldOfWarships.exe!0x0079199A
(0) : WorldOfWarships.exe!0x00791A80
(0) : KERNELBASE.dll!0x76F5F6E5


Frozen threads:
Thread #4300 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x007A9BB4
(0) : WorldOfWarships.exe!0x0079DA15
(0) : WorldOfWarships.exe!0x009F5A1D
(0) : WorldOfWarships.exe!0x00A2F3DC
(0) : WorldOfWarships.exe!0x00799E19
(0) : WorldOfWarships.exe!0x00799E19
(0) : WorldOfWarships.exe!0x00A2A4CA
(0) : WorldOfWarships.exe!0x00A270BD
(0) : WorldOfWarships.exe!0x00A257C0
(0) : WorldOfWarships.exe!0x009F3F63
(0) : KERNEL32.DLL!0x76D67C04

Thread #5076 native trace:
(0) : ntdll.dll!0x775EC29C
(0) : ucrtbase.DLL!0x68B45A76
(0) : ucrtbase.DLL!0x68B4592F
(0) : ucrtbase.DLL!0x68B45B5D
(0) : ucrtbase.DLL!0x68B445DE
(0) : ucrtbase.DLL!0x68B43FF6
(0) : WorldOfWarships.exe!0x004669B4
(0) : MSVCP140.dll!0x68E456CA
(0) : MSVCP140.dll!0x68E63DA0
(0) : MSVCP140.dll!0x68E68296
(0) : WorldOfWarships.exe!0x00BAE4F5
(0) : WorldOfWarships.exe!0x00BAE315
(0) : WorldOfWarships.exe!0x004DB6DA
(0) : WorldOfWarships.exe!0x00BAE26D
(0) : WorldOfWarships.exe!0x00BAEF2E
(0) : WorldOfWarships.exe!0x00BAF161
(0) : WorldOfWarships.exe!0x007A210B
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #4280 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x007AA2DB
(0) : WorldOfWarships.exe!0x007AA189
(0) : WorldOfWarships.exe!0x007A210B
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #180 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x007A9C2A
(0) : WorldOfWarships.exe!0x007A9BE0
(0) : WorldOfWarships.exe!0x007A210B
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #5276 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x007A9C2A
(0) : WorldOfWarships.exe!0x007A9BE0
(0) : WorldOfWarships.exe!0x007A210B
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #364 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x003161C3
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #4564 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x003161C3
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #4052 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x003161C3
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #3100 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x003161C3
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #2164 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x003161C3
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #3660 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x003161C3
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #5192 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x003161C3
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #2224 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : nvwgf2um.dll!0x676AD951
(0) : nvwgf2um.dll!0x676ACB63
(0) : nvwgf2um.dll!0x67C08A75
(0) : nvwgf2um.dll!0x67F1D79E
(0) : nvwgf2um.dll!0x67F1D8C6
(0) : KERNEL32.DLL!0x76D67C04

Thread #4232 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : nvwgf2um.dll!0x67761E3A
(0) : nvwgf2um.dll!0x67761D60
(0) : nvwgf2um.dll!0x67F1D79E
(0) : nvwgf2um.dll!0x67F1D8C6
(0) : KERNEL32.DLL!0x76D67C04

Thread #6028 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : nvwgf2um.dll!0x67761E3A
(0) : nvwgf2um.dll!0x67761D60
(0) : nvwgf2um.dll!0x67F1D79E
(0) : nvwgf2um.dll!0x67F1D8C6
(0) : KERNEL32.DLL!0x76D67C04

Thread #4852 native trace:
(0) : ntdll.dll!0x775EC7EC
(0) : WorldOfWarships.exe!0x008E3CD4
(0) : KERNEL32.DLL!0x76D67C04

Thread #1052 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x0089B62C
(0) : KERNEL32.DLL!0x76D67C04

Thread #2036 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x00888C71
(0) : KERNEL32.DLL!0x76D67C04

Thread #5920 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x0089502A

Thread #3900 native trace:
(0) : ntdll.dll!0x775EC7EC
(0) : USER32.dll!0x7509D433
(0) : USER32.dll!0x7509D17F
(0) : gdiplus.dll!0x69A233AA
(0) : gdiplus.dll!0x69A2C215
(0) : KERNEL32.DLL!0x76D67C04

Thread #3444 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : nvwgf2um.dll!0x67761E3A
(0) : nvwgf2um.dll!0x67761D60
(0) : nvwgf2um.dll!0x67F1D79E
(0) : nvwgf2um.dll!0x67F1D8C6
(0) : KERNEL32.DLL!0x76D67C04

Thread #4872 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : nvwgf2um.dll!0x67761E3A
(0) : nvwgf2um.dll!0x67761D60
(0) : nvwgf2um.dll!0x67F1D79E
(0) : nvwgf2um.dll!0x67F1D8C6
(0) : KERNEL32.DLL!0x76D67C04

Thread #2108 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : dxgi.dll!0x6C17FEA4
(0) : KERNEL32.DLL!0x76D67C04

Thread #5612 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : dxgi.dll!0x6C17FEA4
(0) : KERNEL32.DLL!0x76D67C04

Thread #172 native trace:
(0) : ntdll.dll!0x775EC57C
(0) : KERNELBASE.dll!0x76EA104F
(0) : dxgi.dll!0x6C18CCB4
(0) : KERNEL32.DLL!0x76D67C04

Thread #2420 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : nvwgf2um.dll!0x67761E3A
(0) : nvwgf2um.dll!0x67761D60
(0) : nvwgf2um.dll!0x67F1D79E
(0) : nvwgf2um.dll!0x67F1D8C6
(0) : KERNEL32.DLL!0x76D67C04

Thread #4636 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x00798FCC
(0) : WorldOfWarships.exe!0x00798C6B
(0) : WorldOfWarships.exe!0x00797E10
(0) : WorldOfWarships.exe!0x007A210B
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #5528 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : WorldOfWarships.exe!0x004D8BA7
(0) : WorldOfWarships.exe!0x00B343D2
(0) : WorldOfWarships.exe!0x00B3504F
(0) : WorldOfWarships.exe!0x00B31853
(0) : WorldOfWarships.exe!0x00B31AC4
(0) : WorldOfWarships.exe!0x00B31EED
(0) : WorldOfWarships.exe!0x00B1CE77
(0) : WorldOfWarships.exe!0x00B1D6DF
(0) : WorldOfWarships.exe!0x00AFF62A
(0) : WorldOfWarships.exe!0x00B01E0F
(0) : WorldOfWarships.exe!0x00475865
(0) : WorldOfWarships.exe!0x00B2228B
(0) : WorldOfWarships.exe!0x00B227EE
(0) : WorldOfWarships.exe!0x00B1250A
(0) : WorldOfWarships.exe!0x00B1395A
(0) : WorldOfWarships.exe!0x00B16F31
(0) : WorldOfWarships.exe!0x00AEC8FF
(0) : WorldOfWarships.exe!0x00AECA64
(0) : WorldOfWarships.exe!0x00AED936
(0) : WorldOfWarships.exe!0x00AED7F4
(0) : WorldOfWarships.exe!0x00BF0F58
(0) : WorldOfWarships.exe!0x00BF11B1
(0) : WorldOfWarships.exe!0x00BD09B6
(0) : WorldOfWarships.exe!0x003E013B
(0) : WorldOfWarships.exe!0x00797E7B
(0) : WorldOfWarships.exe!0x007A210B
(0) : ucrtbase.DLL!0x68B5E87F
(0) : KERNEL32.DLL!0x76D67C04

Thread #2344 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : vivoxsdk.dll!0x69681AB3
(0) : vivoxsdk.dll!0x69690FF4
(0) : vivoxsdk.dll!0x6969317A
(0) : vivoxsdk.dll!0x69676B70
(0) : vivoxsdk.dll!0x69676A61
(0) : vivoxsdk.dll!0x6966F39B
(0) : vivoxsdk.dll!0x69687795
(0) : vivoxsdk.dll!0x69680C63

Thread #1840 native trace:
(0) : ntdll.dll!0x775EC27C
(0) : KERNELBASE.dll!0x76EA2C02
(0) : vivoxsdk.dll!0x69681AB3
(0) : vivoxsdk.dll!0x69690FF4
(0) : vivoxsdk.dll!0x6969317A
(0) : vivoxsdk.dll!0x6967707B
(0) : vivoxsdk.dll!0x6968694B
(0) : vivoxsdk.dll!0x6966BD40
(0) : vivoxsdk.dll!0x69676A61
(0) : vivoxsdk.dll!0x6966F39B
(0) : vivoxsdk.dll!0x69687795
(0) : vivoxsdk.dll!0x69680C63

Thread #4400 native trace:

Thread #1684 native trace:
(0) : ntdll.dll!0x775EDD2C
(0) : KERNEL32.DLL!0x76D67C04

Thread #4548 native trace:
(0) : ntdll.dll!0x775EC7EC
(0) : KERNEL32.DLL!0x76D67B89
(0) : XAudio2_8.dll!0x675C2AD0
(0) : XAudio2_8.dll!0x675C166D
(0) : XAudio2_8.dll!0x675C27AB
(0) : KERNEL32.DLL!0x76D67C04

 

Share this post


Link to post
Share on other sites
Beta Tester
3,671 posts
12,833 battles
On 22.12.2017 at 9:39 PM, Deckeru_Maiku said:

#1 - Torpedo Bug

 

1. Description

  • When trying to fire torpedoes mouseclicks are ignored and torpedoes are not immediately launched
  • a few seconds later torpedoes are launched, but not in the direction they were aimed at and at which the target marker points, but in a different direction

 
2. Reproduction steps

  • Playing DDs and launching torps. Bug happens not each time when torps are fired, but randomly it seems

 
3. Result

  • Torpedo launch was wasted and the target was not sunk. Sometimes resulting in my DD getting sunk instead and a lost battle

 
4. Expected result

  • Torpedoes are supposed to be launched in the direction that they are aimed at and hopefully sink the target.

 
5. Technical details

  • Several times during different battles since the last update; not more than once per battle though (If I remember correctly)

 

 

And as an addition: this now also happens with ship's guns...

Noticed it a couple times yesterday and today... guns don't react immediately on mouseclick, but couple seconds later they shoot at a different direction than I was aiming at... no lag shown, framerate as usual...

 

EDIT:

 

A possible solution seems to be to not lock turrets and launchers to a certain direction. Those failed launches and shots seem to be going in the direction to which either the guns (in case of torp launcher fails...) or the torp launcher (in case of gun shot fails...) are locked at.

 

Played a couple games today without locking turrets/launchers and the bug didnt happen.

Share this post


Link to post
Share on other sites
Players
2 posts
3,324 battles

EDIT: I did more testing and added more details after reading Deckeru_Maiku's post

 

#Torpedo bug 2

 

1. Description

 

- Torpedoes fire in the opposite direction in which they are fired. I encountered this several times with the Gearing and I also did an additional test with Shinonome. You aim in the direction in which you want to fire the torps, mousclick, and torps fire but from the other side of the ship, going in the completely opposite direction.

 

- This bug often happens in combination with Torpedo bug 1, which is already described above. As per Deckeru_Maiku's post, this issue appears to be related to the Lock Guns on Bearing feature. Additional tests show that the torpedoes would often fire in the direction in which you have locked your guns.

 

 
2. Reproduction steps

 

- Start a game with a destroyer.

- Lock your guns on one side of the ship.

- Aim at something on the other side of the ship and fire torpedoes.

- If the bug triggers you will see the torps sail in the direction in which your guns are locked and not in the direction in which you aimed them.

 
3. Result

 

This is incredibly frustrating as not only do your torps completely miss the target, they may very well sink one of the ships on your team if you are not careful. You have to watch out not only for friendly ships at the side at which you are firing, but also at the opposite side.

 
4. Expected result

 

- Torpedoes should fire towards the white marker that you use to aim them.

 
5. Technical details

 

- The bug doesn't manifest in every game, but i encountered it 3-4 times with the Gearing and 1 time with the ARP Takao. Also used a Shinonome to do additional testing and I encountered the bug with that ship as well.

 

I have to point out that Torpedo bugs 1 and 2 are GAME-BREAKING bugs. Especially for destroyer ships, as many of them are highly dependable on their torps. I already got killed twice due to these bugs.

 

 

  • Cool 1

Share this post


Link to post
Share on other sites
[FAITH]
Players
426 posts
14,825 battles

They need to fix the torpedo bug fast.

 

Played two games in my Kamikaze R and I cant even aim the torps strait. First I missed a Cruiser because the torps launched to much forward compared to where I aimed.

Next game I sent 6 torps down between two islands in a channel, or well I tried but the game instead launched them strait in to the island WAY OFF, I mean its not bad aiming its like 20 degrees of where I aimed.

 

Game is unplayable in a DD right now and Cruiser relying on torps like IJN are just awful to.

 

Second rage quit for me, the game is just unplayable with torps.

Share this post


Link to post
Share on other sites
[HEROS]
Players
3 posts
5,548 battles
On 2017-12-23 at 8:30 AM, Sn0rkS said:

Game and entire computer freeze in startup while attempting to load the game. Several times over. 
Works after running "check and repair-tool" but back to freezing next time I start the game. 

 

Can't take a screenshot of it since the everything freezes.

Hope you can fix it

Problem still exists. Have to Chech and repair every time before startup and most of the times it doesn't work anyway. 

 

Time of latest occurance:

2017-12-25 at 13:59

Share this post


Link to post
Share on other sites
[FAITH]
Players
426 posts
14,825 battles

1. Description

  • Launching torps shows torps being drooped in the water and the tubes reload timer restarting but there are no torps in the water after the initial splashes.
  • I launched all 3x2 torps from my Kamikaze R and saw the splashes but no torps in the water and the cooldown counter restarted so the tubes where empty.

 
2. Reproduction steps

  • Launching torps and it can randomly happen, cant find a pattern.

 
3. Result

  • Well no torps in the water means I cant hit the target and I still have to wait until new once are loaded.

 
4. Expected result

  • I expect the torps to actually be in the water after launching them and just not vanish magically.

 
5. Technical details

  • Random event?

Share this post


Link to post
Share on other sites
Players
83 posts
25,578 battles

Happened to me several times.

1 - After the end of a battle in which I have finished in the first place by experience I receive a pop-up message with a proposal for a prize (for example, a discount for premium time)

2 - By pressing the button in the message I am transferred to the site

3 - Opens my login window

4 - After logging in, he writes that the "promotion" has expired. But what was the "promotion" ... not a word.

Share this post


Link to post
Share on other sites
[CSF]
Players
467 posts
4,605 battles

Ship: Midway

Bug: Torpedo planes flied off to the stratosphere (even higher than the camera is)

 

Description: I was playing on the Haven map, attacking enemy Montana which was close to the hill on F4. I issued manual attack command for them and when they locked into the attack, they flew over the mountain and into space. I know that planes do change altitude (take two brothers map as an example) but this was way way more than usual - as I said, they were so high that they did not even show up on the camera, while they were up, they were still taking damage from AA and dropped their torps eventually (with serious amount of delay, something like 6 seconds), also the sound effects sounded like the planes were right next to the camera.

 

Reproduction seps: 

Not really sure, maybe bunch of testing in a training room?

 

 

Result:

TBs were still under attack, suffering losses mid drop, the BB passed the drop unharmed.

 

Expected result:

TBs not flying off the screen and dropping consistently.

 

Share this post


Link to post
Share on other sites
[BABBY]
Players
241 posts
5,841 battles

OPERATION NARAI

 

I dont know if this was intended but there seems to be a glitch in the objectives. When one of the enemy transports runs away and some of your transports are sunk (so there is not enough troops to fulfill the primary objective) it is impossible to achieve victory by wiping the attacking force. After killing the last attacking ship you are forced to wait till the timer runs out only to face an inevitable defeat. If this was intended then it is IMO a design flaw that leads to a frustrating experience.

 

1. Description

 Operation Narai impossible to win by eliminating the attacking force if at least 1 transport ship escaped
2. Reproduction steps

 1 transport ship escapes, not enough troops to complete primary objective
3. Result

impossible to achieve victory via secondary objective, stuck in game till mission time ends
4. Expected result

If this was intended, mission should fail as soon as it is not completeable (an enemy transport escaped, not enough troops) without the need to wait until timer ends

If this is NOT intended, there should be a possibility to win if all REMAINING enemy ships are killed, excluding the escaped transports

Share this post


Link to post
Share on other sites
[BGNAV]
Players
741 posts
13,827 battles

1. Description

Discount( -15%) from "New Year!" event for Tier8 ships is not stacking with clan discount of -10%

2. Reproduction steps

Go to TechTree pick Tier8 ship check the price....

3. Result

example Amagi Tier8 BB standard price 10 900 000 credits, current price 9 265 000 credits

4. Expected result

Go to techtree pick Tier8 ship and get it for  standard price -25%(-15% "New Year!" and -10% from clan bonuses)

example Amagi T8 standard price 10 900 000 credits, current price to be 8 175 000 credits

5. Technical details

Time:26.12.2017 17:09:12(CET)

shot-17_12.26_18.09_12-0501.thumb.jpg.e4114f0fc38e67a90ed8d09998154e28.jpg

Share this post


Link to post
Share on other sites
[GBONM]
Players
15 posts
11,511 battles
On ‎24‎.‎12‎.‎2017 at 11:00 PM, Flint213 said:

EDIT: I did more testing and added more details after reading Deckeru_Maiku's post

 

#Torpedo bug 2

 

1. Description

 

- Torpedoes fire in the opposite direction in which they are fired. I encountered this several times with the Gearing and I also did an additional test with Shinonome. You aim in the direction in which you want to fire the torps, mousclick, and torps fire but from the other side of the ship, going in the completely opposite direction.

 

- This bug often happens in combination with Torpedo bug 1, which is already described above. As per Deckeru_Maiku's post, this issue appears to be related to the Lock Guns on Bearing feature. Additional tests show that the torpedoes would often fire in the direction in which you have locked your guns.

 

 
2. Reproduction steps

 

- Start a game with a destroyer.

- Lock your guns on one side of the ship.

- Aim at something on the other side of the ship and fire torpedoes.

- If the bug triggers you will see the torps sail in the direction in which your guns are locked and not in the direction in which you aimed them.

 
3. Result

 

This is incredibly frustrating as not only do your torps completely miss the target, they may very well sink one of the ships on your team if you are not careful. You have to watch out not only for friendly ships at the side at which you are firing, but also at the opposite side.

 
4. Expected result

 

- Torpedoes should fire towards the white marker that you use to aim them.

 
5. Technical details

 

- The bug doesn't manifest in every game, but i encountered it 3-4 times with the Gearing and 1 time with the ARP Takao. Also used a Shinonome to do additional testing and I encountered the bug with that ship as well.

 

I have to point out that Torpedo bugs 1 and 2 are GAME-BREAKING bugs. Especially for destroyer ships, as many of them are highly dependable on their torps. I already got killed twice due to these bugs.

 

 

same here, toped my team in ranked instead of cap area

Share this post


Link to post
Share on other sites
[CATS]
Players
13,610 posts
10,385 battles

1. Description

Getting logged out after battle ends before you get to battle results

 
2. Reproduction steps

Play a battle, end a battle

 
3. Result

Sometimes you get logged out from the game, forcing you to miss the battle results and reload the game

 
4. Expected result

Seeing the battle result screen

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×