• Announcements

    • CHIMM

      RAT Chat Sunday 12/8 3pm server time!!!!   12/07/2019

      CRS is working overtime preparing and setting up the NEW SERVERS at the Portland colocation. This Sunday, December 8th, at 3:00 pm CST/9:00 pm GMT (Greenwich Mean Time). XOOM and the RATs are hosting a live chat discussing the move, and what services will be temporarily impacted in the process. Live chat link will be provided in discord channels when available. We look forward to chatting with you!
Sign in to follow this  
Followers 0
sascha

Micro-Freezes/Stutters

10 posts in this topic

Ran into this one for the first time since I restarted the game. Never happened during intermission, but tonight it did while flying LW.

I was in a pretty intense aerial battle over a town which was also heavily contested by ground troops. Game started doing micro-freezes. Usually lasted only a split second or so, but some were longer. I chased a Spit away from the town and over peaceful territory (no tracers, ground troops or other planes around here) and it would do it again, sometimes freezing up so long that when the Spit maneuvered, it "jumped" from my gunsight to my left/forward cockpit window.

Thought it might have been due to heavy server load, but I was playing with a squaddie with a similar ping and he didn't report any of this. My ping was rock solid at 140-143. And my PC should be more than up to the task (i5 Haswell 4670K @4.2GHZ, 8 GB of Corsair DDR3 memory, GF GTX660, Win 8.1).

Does anyone know this behaviour and have some suggestions? Are there any settings in the options I should fiddle with? Should I consider re-installing the game on my SSD (it's currently installed on one of my HDDs)?

Thanks for your input.

Sascha

Edited by sascha

Share this post


Link to post
Share on other sites

Hm.. can't seem to edit my initial post.

Just did a bit of checking with combat stats and the WW2-log.txt file and this should be the net-log for the mission in question. It happened on the one before that as well, but on this one the stutters were most pronounced.

[Wed Apr 16 00:39:58.330 2014] Netcode2:66.28.224.144 Session Statistics:

Actual bytes per second sent 1168

Actual bytes per second received 2592

Message bytes per second sent 737

Message bytes per second resent 103

Message bytes per second queued 737

Message bytes per second processed 2059

Message bytes per second ignored 10

Total bytes sent 930973

Total bytes received 5010837

Total message bytes sent 594073

Total message bytes resent 103

Total message bytes queued 594073

Total message bytes received 4644853

Total message bytes ignored 10

Messages in send buffer, by priority 0,0,0,0

Bytes in send buffer, by priority 0,0,0,0

Messages in resend buffer 2

Bytes in resend buffer 144

Current packetloss 0%

Average packetloss 0%

Elapsed connection time in seconds 870

[Wed Apr 16 00:39:58.330 2014] spe

[Wed Apr 16 00:39:58.330 2014] t:17 sending pEx with result: 27

[Wed Apr 16 00:39:58.697 2014] t:17 closing code:30014

[Wed Apr 16 00:39:58.697 2014] t:17 got ENOTCONN:10057

[Wed Apr 16 00:39:58.697 2014] t:17 closing code:30122

[Wed Apr 16 00:39:58.897 2014] pmr

[Wed Apr 16 00:39:59.148 2014] t:18 closing code:30122

[Wed Apr 16 00:39:59.148 2014] spe

[Wed Apr 16 00:39:59.148 2014] pEx/no cell

[Wed Apr 16 00:40:54.760 2014] tciRx ro:2 ip:0.0.0.144

[Wed Apr 16 00:40:54.831 2014] t:3 sNot

[Wed Apr 16 00:40:54.831 2014] rvj

[Wed Apr 16 00:40:55.125 2014] tciNoCnx

[Wed Apr 16 00:40:55.297 2014] Netcode2:66.28.224.144 Opening 66.28.224.144...

[Wed Apr 16 00:40:55.297 2014] t:19 on:1 h:1109188752 p:27015 aCell

[Wed Apr 16 00:40:55.297 2014] ! cell active

[Wed Apr 16 00:40:55.297 2014] redired

[Wed Apr 16 00:40:55.724 2014] Netcode2:66.28.224.144 Opened

[Wed Apr 16 00:40:55.976 2014] Netcode2:66.28.224.144 Established

[Wed Apr 16 00:54:06.474 2014] Netcode2:66.28.224.144 Disconnecting

[Wed Apr 16 00:54:06.474 2014] Netcode2:66.28.224.144 Max bps: 0.00 in, 0.00 out

[Wed Apr 16 00:54:06.474 2014] Netcode2:66.28.224.144 Session Statistics:

Actual bytes per second sent 1056

Actual bytes per second received 1168

Message bytes per second sent 737

Message bytes per second resent 103

Message bytes per second queued 737

Message bytes per second processed 756

Message bytes per second ignored 10

Total bytes sent 856397

Total bytes received 2576501

Total message bytes sent 548441

Total message bytes resent 103

Total message bytes queued 548441

Total message bytes received 2240152

Total message bytes ignored 10

Messages in send buffer, by priority 0,0,0,0

Bytes in send buffer, by priority 0,0,0,0

Messages in resend buffer 1

Bytes in resend buffer 72

Current packetloss 0%

Average packetloss 0%

Elapsed connection time in seconds 791

[Wed Apr 16 00:54:06.685 2014] spe

[Wed Apr 16 00:54:06.685 2014] t:19 sending pEx with result: 23

[Wed Apr 16 00:54:06.829 2014] t:19 closing code:30014

[Wed Apr 16 00:54:06.829 2014] t:19 got ENOTCONN:10057

[Wed Apr 16 00:54:06.829 2014] t:19 closing code:30122

[Wed Apr 16 00:54:07.038 2014] pmr

[Wed Apr 16 00:54:07.289 2014] t:20 closing code:30122

[Wed Apr 16 00:54:07.289 2014] spe

[Wed Apr 16 00:54:07.289 2014] pEx/no cell

[Wed Apr 16 00:54:11.623 2014] t:3 pAcc

No idea what most of this stuff means, but packetloss doesn't seem to be an issue. Maybe one of you guys can interpret this stuff?

S.

Share this post


Link to post
Share on other sites

same thing is happening to me, I reinstalled the game 3-4 times and even did the 4g patch and it is still doing it, it was running fine during campaign 99 and the intermission, now I am getting micro freeze's about 3 -5 sec freezes. any ideas guys?

Share this post


Link to post
Share on other sites

Still no answer? Hmmm..

Just tried this again with XCAS and while my game was smooth as silk, his wasn't. And he did a full OS-and game-reinstall and only had TS up in the background.

I also saw a friendly Stuka doing some crazy warping (while Xcas' plane looked completely smooth to me), but the player said everything was smooth on his end. On my FE he went from my 1oc to my 3oc (basically warping backwards onto my right wingtip), then warped back forward about 300-500m to my 12/1.

Oh and BTW: The only time I experienced anything like it on the ground was in one mission in a IIIF on monday. But on that one I was multi-crewing with a squaddie, so I blame that.

I also checked my system resources and found that my PC isn't even breaking a sweat running the game. Total CPU and RAM usage were both well below 50% whenever I checked.

Come on CRS.. would be nice to get a comment on this one. I'll happily provide logs, system info, video-clips, whatever u need to narrow this thing down.

S.

Edited by sascha

Share this post


Link to post
Share on other sites

ok sacha I fixed mine and EVERYTHNG running smooth as bug in a rug,when I did my updates after reinstall of os, it updated my vid drivers to the newest drivers they just put out, I uninstalle them and found olders driver from a year ago, and installed them and it fixed it, you might want to roll your back and give it a shot.

Share this post


Link to post
Share on other sites

Thx Cas! Have yet to try all that, since I'm currently at the folks' house (Easter and all that) with only my laptop to access the web.

I'll see if I run into this again and if I do, I guess I'll just try rolling back the driver.

S.

Share this post


Link to post
Share on other sites

I'm getting this too

I have latest NVidia drivers (335.25 - for windows 7/8 64-bit)

micro stuttering sucks - no others games I have do it

Share this post


Link to post
Share on other sites

http://www.guru3d.com/files_details/display_driver_uninstaller_download.html

Try this, clean out nvidia drivers completely, if you haven't done so with this and reinstall - if still happening use older driver - after cleaning new drivers with tool again of course

Not all the latest nvidia drivers are peachy, some in the past have actually burned up cards even tho they were WHQL

Share this post


Link to post
Share on other sites

Thanks gsc.

Alas, I had to do exactly that a few weeks ago already and not on account of WW2ONL: GF Experience hung up on me during driver update and messed it up completley. Had to clean all things related to NVidia and do a fresh re-install. So I guess my driver *should* be "clean".

I usually never, ever use GF Experience to update drivers (it never really works in my, err, experience.. neither on my desktop nor on my laptop which are both Win 8.1) but instead I use the old-fashioned way of downloading and installing manually. Just this once I didn't think before I clicked - don't ask me why.. :)

S.

Edited by sascha

Share this post


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

  • Recently Browsing   0 members

    No registered users viewing this page.