Quote:
Originally Posted by Maximvs
<snip>
I am only concerned because your issues have gone from yourself and SvS to grouping all of us into this potential diaster for all players over the last several threads / posts - when most of us do not experience these issues (or not to the extremes you have) and cannot be called glitches - these are issues which you need to try and eliminate. I don't ACTUALLY believe Big D is trying to place intentional mistakes just to tourture you.
Now as for the REAL glitches of auto-repair and possible sailing forcefield... yes - these should fixed as soon as possible, and maybe even add options to lower graphic settings on ammo.
Your a good man and a great sailor, I'm only worried that your gonna need counciling and meds if you don't ease up a bit  |
OK, perhaps I did go over the top on those last few. Just because you and I had no lockups that one evening, does not mean they went away. The performance enhancements you pointed out made other parts of the game smoother, but seem to have nothing to do with the lockups I've been affected by, the most. With other players, I still get lockups; some people I sail with experience MUCH greater lockups than I do. For example, my best gunner (the one I'd always invite to boss battles) locks up consistently when thunder or fury is in use nearby. But she doesn't have little 15 second lockups like I sometimes do; she was gone for 30 to 60 seconds at a time; other times just disconnected. A couple other game-friends haven't been able to SvS at all. Just today, two more people got locked up on Andoso.
Now, as the days pass, I'm discovering more about the lockups. It is not
everyone's thunder and fury, but every time I get a lockup, it is from thunder or fury. (My observations of lag-from-grenades does not seem to be repeatable.) Approaching the same lag-storm boat a second time consistently locks up again when that boat fires thunder or fury. Well, sometimes a light sloop - other times four war frigates - but in both cases, repeatable. Not "random" or "intermittent."
I'll try to keep your kind words in mind, when I find myself getting frustrated by all this again. I'll try to remember that it is never easy to push software changes out, even if the change (turn off some minor feature that causes major disruption) itself is easy. I'll also try to not let some of the editing of my messages get to me - this is just a minor message board, just for a game, after all. But seeing my messages here be edited was very strange - that action itself was perhaps what goaded me over the top, here.
I would like to see these problems fixed. If they rework it, so that EVERYONE has auto-repair all the time, that would be cool. If they rework it, so that noone has auto-repair ever, that would be OK. If they rework it to hide the glitch and make the glitch require one more action to activate, that is not cool. If they do that (as someone said they did with the skeleton glitch,) I indeed, may need medication to curb my comments.
Quote:
Originally Posted by whiskey
My favorite method is to use the sloop, back up towards a rock, and throw lightning to draw opponent ships towards me. When they are in better range, I pull out the fury. If they close further, I draw out the explosives!
I have not seen the immobilization problem, either. Have you run a tracert to determine latency on your packets to Disney?
|
Didn't see anything of concern in my traceroute (nor my tracert) but won't put those results here, as I'm not clear on the privacy rules about IPs and city locations. I WILL post this though:
C:\>ping 204.2.148.53
Pinging 204.2.148.53 with 32 bytes of data:
Reply from 204.2.148.53: bytes=32 time=34ms TTL=122
Reply from 204.2.148.53: bytes=32 time=32ms TTL=122
Reply from 204.2.148.53: bytes=32 time=30ms TTL=122
Reply from 204.2.148.53: bytes=32 time=30ms TTL=122
Ping statistics for 204.2.148.53:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 34ms, Average = 31ms
C:\>
C:\>ping 198.105.196.91
Pinging 198.105.196.91 with 32 bytes of data:
Reply from 198.105.196.91: bytes=32 time=71ms TTL=239
Reply from 198.105.196.91: bytes=32 time=75ms TTL=239
Reply from 198.105.196.91: bytes=32 time=74ms TTL=239
Reply from 198.105.196.91: bytes=32 time=70ms TTL=239
Ping statistics for 198.105.196.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 75ms, Average = 72ms
I fortunate enough to ping the second one during a 15 second slowdown. The result was this:
C:\>ping 198.105.196.91
Pinging 198.105.196.91 with 32 bytes of data:
Reply from 198.105.196.91: bytes=32 time=70ms TTL=239
Reply from 198.105.196.91: bytes=32 time=70ms TTL=239
Reply from 198.105.196.91: bytes=32 time=77ms TTL=239
Reply from 198.105.196.91: bytes=32 time=72ms TTL=239
Ping statistics for 198.105.196.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 77ms, Average = 72ms
Which is to say, network round-trip time was FASTER during the slowdown. No network disconnection. I wasn't doing any major downloads at the time. Other times, I have done large internet downloads while playing, with no noticeable affect on game performance. When it is just the game, network utilization is 0.5 to 1.5 percent. With a simultaneous download it is 49.5%. Network traffic changes when my crew status changes, but not much for regular game vs. privateering.
Now, even though I'd like my ping times to be closer to 10ms, I really can't complain when they are under 100ms. I don't mean to be complaining about minor lag issues - I am seeing occasional major stops. About the light galleon - I find it hard to believe that shots consistently off my bow miss (if going backward,) while shots consistently three boat lengths behind, hit (if going forward.) I don't see that behavior with my light sloop! But that is a minor annoyance, so please forgive me for having mentioned it. The lockups are the problem that make it truly unpleasant, at times.
Quote:
Originally Posted by Tuefenhandel
<snip>
If it gets to be like a bad day on the golf course, then it might be time to read a book.
|
Aye, matey! Now that is some sound advice. Fair winds!