Unconfirmed Bug Consistent CTD when going to sea after visiting follower ship's deck

[MrMister]

Found a consistent CTD.

Attached are the save and my InternalSettings.h (modified a fair bit, including enabling big sea for Realism mode).

Steps to reproduce after loading the save:

1. Go to deck.
2. Go to follower ship's deck (an escortee from a tavern escort quest).
3. Go back to Seahorse's deck.
4. Go to Sea -> CTD.

Version 14 FINAL with latest hotfixes.


Visiting the escortee's deck is necessary to talk to the captain there and inform him I wanna change my colours when stopping by pirate settlement on Hispaniola (for a merchant transport quest), in case I stumble upon any of the french or spanish ships that sail around there. Guess I'll have to keep my colours and risk it.

 

[Sebrian]

Hey!

Is there an error log that you could provide ? it should be in the game's main directory, and if you could attach the compile file as well.

 

[MrMister]

I’ll go get it tomorrow, sure.

BTW, having tested some more while moored on a shore, I’m 90% confident that the problem is if you go from one ship’s deck directly to the other’s; if you do, then next time you either go ashore or to sea, the game will CTD.

I’ve had to moor, go asher, go to ship b, go ashore again, and go to ship a’s deck again, in order to tell the other captain and continue playing without crashing.

 

[MrMister]

Here are the compile and system logs; no error.log is generated.

Steps:

1. Moor.
2. Fast travel to other ship's deck.
3. Fast travel to shore -> CTD.


My original discovery was that Mooring, fast traveling to other ship's deck, then fast traveling back to mine, then going to sea CTDs too.
In contrast, fast traveling to shore, then to other ship's deck, then to shore again, then to my ship's deck, then going to Sea, works.

The problem is that, I repeat, fast traveling from one ship's deck DIRECTLY to the other's will CTD on the first future transition that is not a ship's deck (including going to Sea).

Included is a save ready to moor on a beach, for ease of testing.

 

[Sebrian]

Thank you!

Seems like you are not running the latest version of the game, because your save is incompatible with my game, so i couldn't load it and test...

Have you downloaded it here ?

Mod Release - Build 14 Gamma Version [Last update: 27th April 2022]

My original discovery was that Mooring, fast traveling to other ship's deck, then fast traveling back to mine, then going to sea CTDs too.
In contrast, fast traveling to shore, then to other ship's deck, then to shore again, then to my ship's deck, then going to Sea, works.

1. Go to deck.
2. Go to follower ship's deck (an escortee from a tavern escort quest).
3. Go back to Seahorse's deck.
4. Go to Sea -> CTD.

Unfortunately i could not replicate any of your CTD's, it works just fine for me, i have copied your internalsettings so it's not that either.

 

[Grey Roger]

I think I've seen a report of something similar before, and it's certainly not been fixed in any update. If I remember correctly, you need to be in port, go to the companion's cabin, then either fast-travel back to port or go back to your own ship first. Reloads aren't properly set up on companion ship decks, which causes the crash.

Alternatively, remember to tell the escort captain that you intend to use false flags when you first accept the mission, then you don't need to go to his cabin at all.

 

[MrMister]

I did indeed download the latest version: Build 14b FINAL from moddb, then the 1st jan update dated from april 27th. My main menu screen reports it's the 2st Jan update version, and in my download history I do indeed have post_1Jan_updates_270422 as the only update.

 

[Grey Roger]

If the main menu screen reports it as the 2nd January version then you have not installed the update correctly. You need to unzip the update and then copy it into your game installation folder. (Or you can unzip it directly into the game installation folder.)

Note that if you do install the update, you will need to start a new game.

If you have enough disk space, you can create another installation. Do not copy the update to your current installation. Install the stock game to a new folder, e.g. "C:\Games\Pirates of the Caribbean - update", then run the January 2022 installer on that, and then copy the update into it. That would allow you to continue your existing game in your current installation, and to also start a new game in the newer installation.

 

[MrMister]

Oops; I may or may not have actually installed the update then, even though I did download it.

Probably did it initially but then I reinstalled a bunch of times trying to get it to use the nVidia card, and forgot to do it the last time.