CptPrincess

Hi all, Recently went to collect a ship in a dock I'd not been to since the recent patch. Upon inspecting the "Equip" screen, I see that the vessel has two upgrades in two of the knowledge slots. My assumption is that these were equipped books before the update which were then changed to upgrades but left in-place on the equip screen. I'm not sure if the upgrades' effects are currently being applied and I am unable to move the upgrades manually into the upgrade slots. I can re-assign the slots to other, currently known, books. My main question, I suppose, is will the upgrades remain in the knowledges slot if I transport the vessel? Often, this causes the knowledges to be reset. Also - is this expected behavior? Is the intention that I get the use & benefit of the upgrades on this vessel/until I change the knowledge slots? Or an unexpected side-effect of the patch? Apologies if this has been addressed - I didn't see much about it skimming through the UI thread. Many thanks

Ah OK. I think I had a spare Trim By The Stern in a warehouse, too, which I can't find now so that would make sense Thank you

Did we lose some learnt book-knowledges with the patch? I seem to be missing the ability to equip some of the sailing skills, most notably Trim By The Stern and Winged Out Ballast but there may be others I'd not noticed. Can only use Staysails and Studding sails now (to do with sailing buffs). Not sure if this is expected? Many thanks

Hi, not sure if this is the right place to ask. If we create a character on the testbed server, do we have to use the same name/nationality as our main character to receive the Christian note or will the note be received on the main character regardless?

Hello again, @Ink. Sorry for the delay in my response, I've only just managed to get any decent time at my computer to look back at this. Tonight, I did finally get around to 1) Ensuring all Windows updates were complete and 2) Using CCleaner to scan and fix the registry. It found quite a few entries which it flagged as problems, which were all fixed successfully. Trying to run NA with MSI Afterburner active, though, presented the "Oops" box again.

@Ink, Hello! Finally some good news. In fact, 2 pieces: A fresh boot off the PC the following day allowed an install to complete without issue. I got back in on the new Windows account and had a play. Unfortunately a crash when docking in a port*, but recovered with a restart. I happened to be browsing other Support posts and stumbled across this incredibly similar sounding problem. I, too, run MSI Afterburner (though, it turns out, not in the new Windows account) - lo and behold, disabling it allowed NA to start up on the original account. So there we have it, MSI Afterburner incompatibility issue look to be the cause. Is this a know issue? It may be handy to sticky a note, or edit it into the common problems thread, in case it occurs for others too. The odd thing is that I've had it installed since before playing NA - is there something in a recent patch that might conflict? Is it something there may be a fix for in the future? I use MSI Afterburner to aid in fan control, it would be ideal to keep it on. *Finally, just a note about the crash to desktop when docking in port. I've noticed that I'm having fairly common crashes either exiting from battle or docking in port - are these common/expected, and should they be F11ed/reported here or does the in built crash reporter handle it? Thank you very much, @Ink, for staying with this. It's very reassuring to have received this level of support.

Hello again, @Ink I hope you're still seeing these messages, your recent silence was a little disappointing but at least I could play the NA - great work has been done in the recent updates :). When starting the game (in the new Windows account) today, it went through the update process as normal. After clicking "Play Game" to launch the client, though, I was again greeted with the "Oops" box. All other behaviour now seems to be as it was on the original Windows account. There may have been an update before the first time this happened - is this a clue to what may be happening? I would very much appreciate any help with this. I am hesitant to just go on creating Windows accounts if this happens with each update.....

Hi again, @Ink. Unfortunately not had the time to jump into NA as much these past couple of weeks. Quick update, though (but not much new to report): I tried copying across the NA registry entries of the working User to my original Windows user but no luck there (I didn't expect much, but thought it worth a shot). Running NA from the new Windows User still works; it's had a couple crashes to desktop but nothing permanent. This is still the only way I can get into the game - it is running the same antivirus etc running as my usual account. It may seem silly to keep battling with this as NA in the new Windows account works ok but it is a pain to have to have the second account, and to not be able to use NA from my main user, so I'm likely to keep seeing if I can find anything. The fact the client launches ok when started through the NA .exe makes it feel like it could be a steam issue - tho I would've hoped the steam reinstall would have caught that... Do you know what steps Steam goes through to launch the NA client?

Tried as you suggested, running with all antivirus etc. disabled and still got the Oops box. Am finding NA is still running stable in the new Windows user account - not sure if this is any clue?

Any more ideas, @Ink?

@Ink Apologies, Captain, for the long delay - I've not had chance to get to my computer after last weekend. I had been hoping to avoid reinstalling Steam fearing it'd be a lot of work to sort everything else in the library again. I took the leap this afternoon, though, and the reinstallation seems to have gone OK. The issue with NA, however, still persists - An "Oops" box on startup. I haven't tried the install I made in the other User Account again, yet, but am assuming it still works there. E: Just to clarify, I reinstalled Steam while NA was uninstalled, then reinstalled NA fresh and still can't make it on :(.

Hi again, and another quick update. I've been tinkering through this weekend trying to get back into NA. I'm still not 100% what the issue is, hopefully you guys can still help me there, but fortunately I seem have found a workaround this afternoon. After I had no luck with the registries (they were not recreated when NA launched thru Steam) I decided to see if starting the .exe would generate them. This created some but it didn't look like as many as there were before, and starting through Steam still caused the crash. I have noticed, though, that some of the crash logs contain incorrect information - saying I have 8126Gb (yes, Gb) of addressable space - this is certainly not the case - so I'm not sure if that's an indication of what may be wrong? Anyway, I was out of ideas so gave up until this afternoon. I was still feeling that it's a registry issue, and I'd noticed thatl the keys are all created in the Current User registry section, so I decided to create a new Windows user account and try installing and running NA with that. Low and behold, I was into the client, logged into the server, and sailing without a hitch. Very happy with that. I didn't have the time to switch back to my usual account to see if NA was working there and, if not, I'd like to continue trouble shooting to see if I can. @Ink I hope it's ok, I have a couple of questions. 1) Has any of this given any clue as to what may be wrong, or how to solve it? 2) Would seeing the collection of crash logs shed any light? 3) Is copying the registry entries from the working User account to my original account likely to get NA starting? And finally, Are you able to tell me where the log generator queries for system resources so I can find out where it's getting the incorrect value? Thanks again for your help

H agaiin @Ink, Took your advice and removed the registry entry for NA. Interestingly, lots of the values seemed to just say "Invalid DWORD (32Bit) Value". When restarting NA, however, the same behavior as before is given. Also, no new registry entries have been created in place of the ones I removed, even when reinstalling and restarting NA, Is this expected? Or should it have created new registry entries? I have a copy of the entries prior to deletion, if that would be of any use in going forwards?

@Ink any more thoughts? Still not able to get into the client when launching through Steam. Am at work but eager to give anything a try again this evening Edit: And how do we properly tag people in posts?

Hiya, back home for the night and a quick update. So, I tried uninstalling NA and removing all files left behind from the location (copied them elsewhere) and then reinstalling it - same result, generation of the "Oops" box on launch of the bug reporter and of the client. For whatever reason, I then tried launching the client from the exe directly. This launched the client and got me to the Server Select screen and I was excited. Unfortunately, selecting a server to load in to briefly showed a "Steam start required" sort of message in red and then quit the client, (I assume) tried to start the client the Steam way and produced the "Oops" box again. So I took your advice, removed NA and reinstalled it to a new drive and, in fact, a new Steam library. No luck there either, when starting through Steam both the client and the crash reporter give me the "Oops" box. When started through browsing explorer to the location and launching the .exe files directly, both applications start and seem to behave as expected until the point they request to be started through Steam. Perhaps a registry entry somewhere needs resetting - is there anything set by NA explicitly? Any help greatly appreciated I have copies of all logs if they'd help - just let me know where to send them.