That's an excellent resource, thanks.

I ought to have said "it's not likely we'll do it soon"

Check out this article for a couple simple examples of scenarios that will break (in spectacular and difficult to diagnose ways) when given a memory address past the 2GB barrier. We can't release a build with this flag enabled before we ensure that we haven't done anything stupid, and that our 3rd party libraries haven't done anything stupid.

This evening, Flying Lab Software staff issued a series of permanent bans as a result of gold selling activities by players of Pirates of the Burning Sea. Additionally, 24 hour bans were issued on multiple accounts found to have participated in the transfer of this illicit gold.

Please understand that we will investigate all reports of illicit transactions and we will following up with the appropriate disciplinary actions, which could include confiscation of the resources in question, and ultimately banning accounts that sell or buy these illicit resources.

In the future, if you are approached by someone seeking to sell you gold, you are asked to file a support ticket by typing /support in game, or by visiting our support site at http://support.flyinglab.com/

Customers are encouraged to share as much information as possible, including the character’s name, the server where this occurred, the time of the incident and any links they may have shared with you during the solicitation.

Flying Lab Software has developed a host of resources to help us identify these illegal activities as they occur, and we will take swift and decisive action to protect and preserve the economic features of our game.

Best,
Aether

We will be applying an emergency serverside upgrade this morning (Sat, 1/19) at 4am. Estimated downtime is 2-3 hours.

We apologize for the inconvenience and the short notice.

Ok, here's what I've got:

For XP, 163.25 seems to be the best bet.

For Vista, 162.50 works for any 8800 card other than the GT, which can't use it. The best answer we have right now is to run in windowed mode, while we continue to work on the problem. Unfortunately, we need Nvidia's help with this to see what changed with their driver, and they're not in on the weekend, so it'll be Monday before we get any movement on this.

As noted before, we'll be posting a build to testbed with the crash to desktop fixes and the losing textures (turning to white) sometime tomorrow.

Please see this thread.

Re: /LARGEADDRESSAWARE

Thanks for pointing this out. I've filed a suggestion that we enable this flag.

However, I must admit it's not likely we'll do it. Enabling large address awareness requires being sure that we (and possibly any 3rd party libraries we use) don't do pointer arithmetic that might overflow a 32-bit register. It's not likely that we do, but we'd have to audit the entire codebase to be sure. Even with large address awareness, 32-bit Windows still restricts us to 2GB. (3 in extremely rare cases where an advanced user has reconfigured the OS) We're much more inclined to focus our efforts on reducing our memory footprint than on enabling a larger one.

Yep. In patch v1.1, coming shortly after launch, these rare spawns will appear twice as often as they do now.

submit it please

You're absolutely right. The second fight in that mission is too hard, and it's because the xebecs are too powerful for that mission. We do view it as a problem, and we'll get it fixed as soon as we can.

Warham, you're exactly right about the 169 comment. Heidi sent me the recommended drivers, but we're doing a little testing right now to make sure that we're certain they work. I'll update this message with the info and the links once I get it.