Jump to content
Forum Shutdown 28/7/2023 Read more... ×
Sign in to follow this  
FaceFisted

This game is seriously testing my nerves :D

37 comments in this topic

Recommended Posts

Beta Tester
868 posts
5,081 battles

I just wanted to share one frustratingly "funny" story that happened recently. 

 

You know that players are not so great recently and that average skill in games is sinking like a Titanic. Well, I had one of those games with the team that was just like that. They were lemmings, cowards, bad at shooting and it felt that I was the only one who knew what he was doing. We were of course losing badly until I saw a gap in enemy lines and chose to use it to slide through and cap their base.

 

I finally got there and counter started ticking. They weren't close so I thought - finally something good is happening in this match. Then I saw that someone has spotted their DD coming to decap their base. "No problem", I thought, "I have stalinium HE shells loaded, he will be swimming with fishes soon". He started to emerge behind rock, counter showed 10s more until cap, my team is completely broken and everyone is border hugging at the opposite side of map...

 

...I aimed with a grin on my face...

 

...clicked left mouse button..

 

...and...

 

...and this happened...

 

 

JOTtdsA.png

 

 

 

G5vOeFP.png

 

  • Cool 2

Share this post


Link to post
Share on other sites
Players
1,064 posts
4,944 battles

The worst part, adding insult to injury, is that you even have to aknowledge it by clicking "OK"!!!

The dev who conceived the error message never played the game, or he would have written a big bright red "Foxtrot Uniform Charlie Kilo" instead of that silly "OK".

  • Cool 3

Share this post


Link to post
Share on other sites
[SCRUB]
Players, Players, Sailing Hamster
3,462 posts
5,363 battles

The worst part, adding insult to injury, is that you even have to aknowledge it by clicking "OK"!!!

The dev who conceived the error message never played the game, or he would have written a big bright red "Foxtrot Uniform Charlie Kilo" instead of that silly "OK".

 

I don't think this error message was designed by anybody in particular. Error msgs are generated based on the error ID by the OS upon the collapse of an application...

Share this post


Link to post
Share on other sites
Beta Tester
1,046 posts
20,419 battles

Sorry mate, the result of that game was set before it started, you were meant to loose, opposing the system leads to desperate measures such as the one that happened there with you. 

 

  • Cool 2

Share this post


Link to post
Share on other sites
[1378]
Players
460 posts
3,784 battles

I recently found that the focus of Windows 10 changes from WoWs to the desktop, basically doing a forced Alt-Tab. Not as bad as a crash, granted, but if it happens in something like that you will lose out on that shot and, well, lose.

Share this post


Link to post
Share on other sites
[DECOM]
Beta Tester
193 posts
7,926 battles

I recently found that the focus of Windows 10 changes from WoWs to the desktop, basically doing a forced Alt-Tab. Not as bad as a crash, granted, but if it happens in something like that you will lose out on that shot and, well, lose.

 

​I get that quite often. Only thing that really seems to help is to not have any other windows open while playing.

Share this post


Link to post
Share on other sites
Beta Tester
868 posts
5,081 battles

The worst part, adding insult to injury, is that you even have to aknowledge it by clicking "OK"!!!

 

lol yes :D

 

TcW7dq0.png

 

That game was definitely meant to be lost. :)

  • Cool 2

Share this post


Link to post
Share on other sites
Alpha Tester
5,609 posts
5,569 battles

Windows 10 have some issues with memory that are probably highlighted by WoWs game architecture. It never crashed for me on Win 8, and on 10 i've got two crash in one battle few times already. Having minimal possible amount of crap running in the background help though. God forbid from runing WoWs and Firefox.

Share this post


Link to post
Share on other sites
Beta Tester
868 posts
5,081 battles

I am playing on 8.1 64-bit and it crashes constantly. Mods or no mods, with apps in background or without.

 

Problem is in WOWS and it started to happen since 0.5.3

 

I have i5@3.2MHz, nVidia GTX 760 2GB, SSD, 8GB Ram, Creative X-Fi extreme music. Quite decent PC and WOWS used to work great until that patch.

Edited by FaceFisted
  • Cool 1

Share this post


Link to post
Share on other sites
Alpha Tester
2,543 posts
16,031 battles

Can I share in the feels?

 

 I was playing with a buddy some light hearted matches on lower tiers. It was during that 3x weekend and for once I decided to actually pay atention to my ships' first victories modifiers and went all out: Kraken, confederate and even Papa Papa flag, which I've never ever touched. Decided to bring out my best premiums to make the most out of the flags.

 

First match: Marblehead, lost horribly. Second Match, Marblehead again, did absolutely nothing and we won.

 

It's okay, I've never liked the Marblehead that much but I'm sure that with Yuubari it will be different. Silly me that I hadn't played with Yuubari since the end of AFT. Tier VI match, botton tier, Strait map, Fusos and New Mexicos EVERYWHERE, Clevelands too. I ended doing some miserable 25k damage mainly against BBs suffering and counting each second as my last one while dodging every shell on earth. We won. Miserable exp.

 

[edited]it, let's bring the jewel of the crown, Iwaki Alpha. Game was awesome, we wiped then, except that I was barely able to do damage. Miserable Exp again.

 

At that point I was convinced that those darned Papa Papa flags were cursed. While I was trying to cope with the frustration I brought out the big boy, Arkansas. As you may know the ship is extremely slow and if you pick the bad side of the battle you may end up doing nothing, and that, almost, exactly happened. Heading north in Solomon Islands I saw that the enemy in that flank was becoming completely wiped out. I said [edited] IT and decided to go directly through the middle perfectly knowing there were Minekaze and 2 CV in the enemy team. And as expected they went after me: dodged Minekazes torps, dodged the drops of both CVs in the strait, all with minimal damage. Luckily a cruiser went with me and we managed to take care of the Minekaze. FINALLY, I was at the other side with a lot of targets to shoot at and in a great position. Just as I was about to nuke a St. Louis who was happily showing its broadside at 7 km with my guns, the exact moment in which I clicked:

 

JOTtdsA.png

 

At that point it was 11 PM so I decided to close WoWs, close my laptop and cry myself to sleep vowing to never use those Papa Papa flags again.

  • Cool 1

Share this post


Link to post
Share on other sites
Beta Tester
4,249 posts
848 battles

I recently found that the focus of Windows 10 changes from WoWs to the desktop, basically doing a forced Alt-Tab. Not as bad as a crash, granted, but if it happens in something like that you will lose out on that shot and, well, lose.

 

To me, it happens that my PC asks if I want to upgrade to Windows 10 at the start of the game. Luckily, so far there has been no instance in which I was taking an important shot.

Fingers crossed... :hiding:

Edited by Historynerd

Share this post


Link to post
Share on other sites
[1378]
Players
460 posts
3,784 battles

Windows 10 have some issues with memory that are probably highlighted by WoWs game architecture. It never crashed for me on Win 8, and on 10 i've got two crash in one battle few times already. Having minimal possible amount of crap running in the background help though. God forbid from runing WoWs and Firefox.

 

Well, I almost always have Chrome open, and Steam. And it's ONLY WoWs that has this weird behaviour. WoT is fine. Different engine and architecture, probably, but still the same developer.:izmena:

Share this post


Link to post
Share on other sites
Beta Tester
868 posts
5,081 battles

Can I share in the feels?

 

 I was playing with a buddy some light hearted matches on lower tiers. It was during that 3x weekend and for once I decided to actually pay atention to my ships' first victories modifiers and went all out: Kraken, confederate and even Papa Papa flag, which I've never ever touched. Decided to bring out my best premiums to make the most out of the flags.

 

First match: Marblehead, lost horribly. Second Match, Marblehead again, did absolutely nothing and we won.

 

It's okay, I've never liked the Marblehead that much but I'm sure that with Yuubari it will be different. Silly me that I hadn't played with Yuubari since the end of AFT. Tier VI match, botton tier, Strait map, Fusos and New Mexicos EVERYWHERE, Clevelands too. I ended doing some miserable 25k damage mainly against BBs suffering and counting each second as my last one while dodging every shell on earth. We won. Miserable exp.

 

[edited]it, let's bring the jewel of the crown, Iwaki Alpha. Game was awesome, we wiped then, except that I was barely able to do damage. Miserable Exp again.

 

At that point I was convinced that those darned Papa Papa flags were cursed. While I was trying to cope with the frustration I brought out the big boy, Arkansas. As you may know the ship is extremely slow and if you pick the bad side of the battle you may end up doing nothing, and that, almost, exactly happened. Heading north in Solomon Islands I saw that the enemy in that flank was becoming completely wiped out. I said [edited] IT and decided to go directly through the middle perfectly knowing there were Minekaze and 2 CV in the enemy team. And as expected they went after me: dodged Minekazes torps, dodged the drops of both CVs in the strait, all with minimal damage. Luckily a cruiser went with me and we managed to take care of the Minekaze. FINALLY, I was at the other side with a lot of targets to shoot at and in a great position. Just as I was about to nuke a St. Louis who was happily showing its broadside at 7 km with my guns, the exact moment in which I clicked:

 

JOTtdsA.png

 

At that point it was 11 PM so I decided to close WoWs, close my laptop and cry myself to sleep vowing to never use those Papa Papa flags again.

 

we should start a support group for those who have experienced these crashes :)

Share this post


Link to post
Share on other sites
Alpha Tester
5,609 posts
5,569 battles

 

Well, I almost always have Chrome open, and Steam. And it's ONLY WoWs that has this weird behaviour. WoT is fine. Different engine and architecture, probably, but still the same developer.:izmena:

 

Yes, nothing else is crashing, only WoWs. And guess what game as the only one had micro lags and stuttering all the time? Yep, WoWs. Done absolutely everything, still some battles are utterly unplayable because the crap lags for a second every 3 seconds.
  • Cool 1

Share this post


Link to post
Share on other sites
Players
13,176 posts
13,617 battles

Windows 10 have some issues with memory that are probably highlighted by WoWs game architecture. It never crashed for me on Win 8, and on 10 i've got two crash in one battle few times already. Having minimal possible amount of crap running in the background help though. God forbid from runing WoWs and Firefox.

 

W10 used to notoriously BSOD few times a day, mostly when playing WoWs, which had tendency to crash every so often. All stress tests were fine, other games were fine, only Sheeps were working as intended. Rolled back to W7 and game (and OS) is rock stable.

Share this post


Link to post
Share on other sites
[SCRUB]
Quality Poster
7,146 posts
31,598 battles

Hi all,

 

Darn... :(

 

Do you have some MODs installed?

 

If yes - which ones (please post a list)...

 

BTW, I have found out that certain MODs must use "Reduce GUI Refresh Rate" in order to avoid WoWs game crashing ("Navigator" for example)!

 

 

Leo "Apollo11"

Share this post


Link to post
Share on other sites
Beta Tester
3,552 posts
8,863 battles

I don't think this error message was designed by anybody in particular. Error msgs are generated based on the error ID by the OS upon the collapse of an application...

Yep, that's MS there helping users with their lovely informative error messages.

Then again after Windows 7 they've been shafting PC constantly into arse...

With all the cramming of toyphone garbage into PC and intention of making PC remote payment terminal for their continuous updating Windows and Store.

 

That 0xC0000005 error can be caused by awfully many things.

 

Yes, nothing else is crashing, only WoWs. And guess what game as the only one had micro lags and stuttering all the time? Yep, WoWs. Done absolutely everything, still some battles are utterly unplayable because the crap lags for a second every 3 seconds.

Any DPC latency issues?

http://www.resplendence.com/latencymon

 

Share this post


Link to post
Share on other sites
Players
585 posts
13,149 battles

Using windows 7 in gaming pc no problems at all so far with WoWs. I have win 10 installed on laptop and I don't like it. I ll keep win 7 for very long I guess. I dont see any reason to get windows 10 unless you want all your privacy handed over to microsoft. 

  • Cool 2

Share this post


Link to post
Share on other sites
Beta Tester
868 posts
5,081 battles

Using windows 7 in gaming pc no problems at all so far with WoWs. I have win 10 installed on laptop and I don't like it. I ll keep win 7 for very long I guess. I dont see any reason to get windows 10 unless you want all your privacy handed over to microsoft. 

 

This is the reason why I uninstalled W10 and reinstalled win8.1. On a long run, I see Linux as only viable option and when that time comes, WG better port their games for that platform ;)

Share this post


Link to post
Share on other sites
Players
585 posts
13,149 battles

 

This is the reason why I uninstalled W10 and reinstalled win8.1. On a long run, I see Linux as only viable option and when that time comes, WG better port their games for that platform ;)

 

Linux will be the savior of mankind operating systems considered. I wish I knew how to use it probably will give it a try soon too. There must be a topic here explaining how to run WoWs on linux.

 

As an average user you don't control Win10, Win10 controls you...

 

 

Share this post


Link to post
Share on other sites
Players
340 posts
134 battles

That 0xC0000005 error can be caused by awfully many things.

 

The "@ 0x00D3B438" is typically a crash location in the code though. WG should be able to look that up and determine exactly where the code is crashing and probably why.

 

I'd be surprised if it wasn't fixed in the next patch, assuming that it crashes for Russians too.

 

Share this post


Link to post
Share on other sites
Players
119 posts
155 battles

Now that's just funny. I expected the story to end something like, 10 torpedoes from a direction you didn't know about from a second Destroyer and then go " Clever Girl:popcorn:

 

Share this post


Link to post
Share on other sites
Sign in to follow this  

×