|
|
|
|
|||||||
| Fixed Geek Squad Rescued These Threads |
|
Login or Register now to see less ads. |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Disney always tells you it's latency if they have no clue what else might be causing it - they do the same on TT. Their customer support is lacking.
Regarding problems - the only one I've really seen since the update is loading screens sometimes take longer than usual and I've had the gun freeze bug a few times. I'm thankful it's not been worse. All I can suggest is asking others here what helps, sending bug reports so they realize that there really is a problem and playing on quieter areas. |
|
#2
|
||||
|
||||
|
We have two men down in our guild right now. Since the update, the game play has been so terrible for one that he can't even play. Crashes whenever he sails, TP screens load and never stop, and crazy lag - all of this keeping him off the game. For the other one, he crashes when a ship ports, or he can't board the ship at all because it never loads, and when he does sail the game is beyond laggy. Neither one can TP really.
Both of them were playing perfectly fine up until the update. So I find it hard to believe that the problems are specific to just their computers. There has to be more to it. I know that people were having similar issues, so I'm just curious to see if anyone has found any helpful fixes to this over the past few days. They updated their graphics drivers, which helped a bit. Now one of them can play the game, so long as he pretty much stays in the same spot to fight. But once he starts moving, the lag comes in. The other one won't even bother signing on right now. It's been a bit since I first posted this thread, so I wanted to check back and see if anything new has come up. I appreciate the help. Thanks. |
|
#3
|
|||
|
|||
|
I got word of the new changes in Pirates and logged to my trial pirate a couple of days ago to check them out. Experienced a lot of lag and crashes; it was really discouraging.
One thing I did notice was that the game seemed to now be using port 1935 TCP while running. I don't recall it doing that before. I was too disgusted at the time with seeing some of the same old bugs in the game to care about playing with port triggering to see if it helped, so I didn't bother. Maybe some of you guys that play on wireless routers or behind hardware firewalls might want to take a look at that and see if it might be something that makes a difference. |
|
#4
|
||||
|
||||
|
Thanks for the quick response on that one. That's a possible solution that I haven't heard before. I'm going to pass that along right now.
|
| Thread Tools | |
| Display Modes | |
|
|