Henry d'Esterre Darby

I had a very similar problem with the cable provider's internet router. On wireless, it dropped all packets every 1:45 for 15 seconds. Extremely annoying, and replacing it with another unit didn't help. A third party wireless router fixed the issue. Always check your network with the above and/or a program called PingPlotter - you might be surprised where the problem is. Very glad you got the issue identified and could work around it sir!

It works just fine to buy back your outpost slot from any other port (or at least it did before the recent patch, I haven't tried it since).

Only for client based games. See my response above - every gamer should be aware of both models of game server - client pushes facts/locations/etc, and client receives facts/locations/etc. In the latter, which is how Naval Action is designed, a single client's latency by definition can not affect the actions of the other players around it, unless there is some sort of check/response system in place that requires the client respond to the server's assertions - and I'm not sure I would see the point in doing that. Effectively, the server plays the game, moves the ships, etc. all by itself given their last state. The clients just issue requests (please fire the cannon now, please apply left rudder) and the server is the one that makes the final decision on whether or not to do it based on business rules.

Let's back up the truck for a moment here. "When I play with people from Australia everything is jumpy and they ruin the game." That's not how this works. The server is not in Australia, and the physics, locations, etc. are not being transmitted from the client side, they're on the server side. This means if you're near the East Coast or European Server, and someone else is in your match from Australia, they do not affect latency or anything else in game one bit due to a bad ping. The only people that might have a complaint about latency not working right are the Australian/SEA area players themselves. Should their ping be bad, they might suffer from all of the ships in the match having delayed actions, not being where the client expects them, etc. Their ping does not affect your game, in any way shape or form (other than perhaps giving you a slight benefit in that you can "see" and "react" before they can. Let's review - the server receives your instruction to fire. The server itself is tracking everything, waves, ship health, where things are aiming, ship speed, location, etc, so it runs the fire routine, handles the flight of the balls, applies damage to the ships that intersect those balls, starts the reload process on your guns, then sends all of that information to the various connected clients. At no point is a client "pushing" location or state, etc. to the server - that's how people commonly cheat in online games. Since the client isn't pushing anything, at worst, a bad ping on an SEA player will result in that player's requests to "do something", like fire, turn, etc. being delayed reaching the server, but "reality" is real time on the server, and the only delays or issues are individually on the client machines themselves. So, if anything, an Australian might want a "local" server so they can be more competitive and not have to wait so long for their instructions to be executed (as well as seeing things that others are doing faster), but those nearby the existing servers don't have anything whatsoever to fear from having a high latency player in their match.

Awesome! Thanks for sharing that information Dom.

Great Dom, did you have a link to that information?

That may be correct in the real world, but in the game, the order is currently Ensign -> Midshipman -> Jr. Lieutenant. Admin has stated that those ranks will be changing in the near future so they weren't going to correct it right away.

I'm not entirely sure I'm a fan of this as written. However, maybe enhance the importance of Gunnery focus by only allowing both sides to reload when in Gunnery Focus. Leaving GF would mean the side most loaded would finish, then the side least loaded would finish after the first side is done. Disabling the decks on that side would prevent them from reloading (say, you wanted to do the more historical fire one side, then turn and fight the other side - you'd fire the first side, disable those decks, then switch to the other and fire normally. This change would increase the importance of Gunnery Focus, and decrease the ability to constantly S turn to fight both sides simultaneously. Ships with a completely full crew could potentially fight both sides I believe, at the cost of other activities.

Why would you penalize a premium ship owner with a week of no ship when a non-premium can go buy a new ship and keep going after losing their last durability? That doesn't make the first bit of sense.

It's possible the card was set too high to start with, it is damaged or failing, the case isn't handling heat very well, etc. etc. At least for now it's working. I'd agree that running a stress test would be a good idea so you can start saving for a new card if it's failing.

It's complicated, but there's a possibility they're on a global ban lost due to someone else's misbehavior.

I'm in career scenarios and still not getting points. No worries, it's fun either way.

Have him try a different email address. If that still doesn't work, he may be IP Banned, in which case, you could try to register for him and then hand him the account.

Prater has it right. Your graphics driver is the culprit - now the question is - what is crashing the graphics driver? That's beyond my ability to help with remotely unfortunately.

Yup! I re-ran the scenario last night and realized that I was too far ahead of schedule and effectively got too close to another train in front of me. Though now it's stopped awarding me career points for doing any scenario...not sure why.

Let's back it up - where can I find the graphics settings? They're not available from the Escape menu. Nevermind, found it. My problem blowing through the red was due to my not understanding that if you're going to be stopping at a platform on the main high-speed line, there are no speed reduction warnings - you're just expected to stop.

I'm still not a fan of this. The last time they had it (as I think was mentioned earlier in this thread), the testers thought that it made shooting too easy.

Seems like carronades also get knocked out more easily in OW, so I suspect there is something behind that.

No, they shouldn't. Being able to fly a flag for a particular group should require membership in that group. There's also a whole thread on false flags - it's a complete mess to do in the game. Please take a look at that thread and contribute any additional thoughts you may have. I think I completely killed the last attempt to get a player designed system for false flag operations simply with the level of complexity in the coding it would take to accomplish - http://forum.game-labs.net/index.php?/topic/1610-raising-different-national-flags-hiding-under-a-neutral-flag/page-4?p=95503#entry95503.

I bought the base package and played around with it last night. I'm a little disappointed in the performance on my laptop - the graphics are fairly ugly and yet I get stuttering when it loads an upcoming scenery area. I would have expected something marked as a "2015" product to be far more optimized and beautiful. I haven't found any way to customize the graphics, but when the steelwork on the trestles isn't even "hollow" and yet my framerate is bad, well, maybe I'm missing something. Past that, I learned that it's hard to watch your speed and the signals at the same time when doing 120 on the lines north of London.

hehe, no problem. The very presence of Constitution, Lynx, and soon, Rattlesnake all very much point to the existence of a fledgling United States at the time. I've learned more about that era of history in the past few months as I've begun to take such an interest in the game than I have in decades.

Does he have any other e-mail addresses he could use to try to create an account?

Yarev, Sea Trials 1 has been extremely stable for thousands of players. This leads me to believe that there is something local to your computer that is causing a problem - a hardware or driver conflict, malware, etc. Please let us know if trying a different driver version helps.

http://forum.game-labs.net/index.php?/topic/5315-long-maintenance-warning-open-world-servers/ This is an Alpha Test, the game hasn't been released yet. Open World is in a very early development stage and you can expect long outages. Once the next feature set and fixes are released, the OW servers will be back up for further testing. Once the game has reached a point where Game Labs is ready to enter Beta Test, I'm sure you'll see far longer up-times on the servers. For now, they have been kind enough to leave the original Sea Trials build up for folks to get their sailing fix. Keep an eye on the forums and they'll let you know when the next version of Open World is ready for testing and feedback. Thanks for your patience!

All new users must have their first post approved. It's a pain, but there is a problem with the forum software that has allowed spam bots to auto-register and start spamming the forums, so admin made that change.