CoastGuard71 said:
I don't like the map not locking for my ship to move rather than the map moving to keep my ship in center... maybe some like it... I don't. Past games had this feature and I've gotten used to it... how to lock the map?
Isn´t it just to press Tab
I've tried that since it is habitual from past versions, but, no, the map does not lock, the ship is centered and the map spins around... does your download not do the same?
Next time that happens, post the log files "compile.log", "system.log", and "error.log" if it exists. I've never seen that problem so I've no idea what's causing it.
No, I'm using Windows 7 myself.
Again, the way it is now is the way I've seen it for many a year. I've no idea how to change it.
B15 might be more reliable in that you might not have the problem with the game freezing when a ship sinks. The map probably won't work differently.
A lot of bugs have been fixed since 2016. But I don't recall the map changing since then, and I know I was playing in 2016 because that's about the time I started work on the "Ardent" storyline. (In the Chinese zodiac, 2016 was the Year of the Monkey, which is why there's a monkey-themed Easter egg in the story.)
Problem is with the screen freeze everything locks up and Windows doesn't generate an error diagnotics citing the cause for the error. Only way to reset is ctrl-del-alt reset which reboots... no clue why this is happening, not even a diagnostic! However, same freeze happened in v21 when the second ship in a usual pair is sunk... freeze, reboot, resume at last save. Coder needs to identify cause and correct seems the issue in 21 carried over into 22?
That's odd. I also have the 2003 Akella/Bethesda version with 2 CD's and Windows 7, and have no problem installing and running the stock game. I didn't even need to use any compatiblity settings.
The reason you can't save during a boarding is that the save won't work and that will cause trouble.
You should unzip the January 2024 update after running the Build 14 installer. The update contains files which were changed or added after the 2022 installer was created. If you unzip the 2024 update and then run the installer, the installer will overwrite the 2024 files, leaving you with the 2022 version without any updates.
You should be able to sail out of Antigua, though you need to navigate a narrow channel on the east side of the crater. Edit "PROGRAM\InternalSettings.h" and change "DISCOVER_SAIL_TO" from 1 to 0, so that you can use sail-to to get to Muscetto Cove without needing a map. That's a beach on the outside of the crater and it's easier to sail away from there.
What browser are you using? MS Edge tells me the file is "incompatible"
I don't know anything about the bug with the second ship. You can't save while boarding because even if you did change the game to allow it, the saves wouldn't work properly. I'm not sure why you can't save while sailing, unless it's while there's a battle in progress, in which case again the save would probably not work properly.
So, what locks out the save feature during boarding... sounds like a restriction in the code to make game play more difficult not consistent with the factual instability in the code that causes frequent hangs or crashes during the boarding. So, has anyone at least found the subroutine that prohibits save during a boarding? Why only during boardings if no other time? Consistent with a designed logic lockout that should be removable. The code has a restriction... how can I remove it? Give me the module and line number and I'll take care of it.
I don't know anything about the bug with the second ship. You can't save while boarding because even if you did change the game to allow it, the saves wouldn't work properly. I'm not sure why you can't save while sailing, unless it's while there's a battle in progress, in which case again the save would probably not work properly.
Have you played v21? Give it a try... when I play 21 and the second ship in a surface action is sunk the screen freezes... this kind of "crash" gives no MS diagnostic so I have no idea what is at fault and can't resolve the code error.
That's odd. I also have the 2003 Akella/Bethesda version with 2 CD's and Windows 7, and have no problem installing and running the stock game. I didn't even need to use any compatiblity settings.
The reason you can't save during a boarding is that the save won't work and that will cause trouble.
You should unzip the January 2024 update after running the Build 14 installer. The update contains files which were changed or added after the 2022 installer was created. If you unzip the 2024 update and then run the installer, the installer will overwrite the 2024 files, leaving you with the 2022 version without any updates.
You should be able to sail out of Antigua, though you need to navigate a narrow channel on the east side of the crater. Edit "PROGRAM\InternalSettings.h" and change "DISCOVER_SAIL_TO" from 1 to 0, so that you can use sail-to to get to Muscetto Cove without needing a map. That's a beach on the outside of the crater and it's easier to sail away from there.
I've tried both your suggestions of installation order with the same result. I suspect MS security updates being pushed on my system is doing this. It also won't accept .exe files from sites without certification, requiring several actions to override the block. Why doesn't Pirates have a certification?
seems everyone is requiring that because of the criminal activity so common online.
Not being able to save during boarding is a program lockout since that and when "sailing" are the only times it happens... sounds like a logic Y/N step during that program. Just give me module and line number... someone must have found this during all the revisions conducted.
That's odd. I also have the 2003 Akella/Bethesda version with 2 CD's and Windows 7, and have no problem installing and running the stock game. I didn't even need to use any compatiblity settings.
The reason you can't save during a boarding is that the save won't work and that will cause trouble.
You should unzip the January 2024 update after running the Build 14 installer. The update contains files which were changed or added after the 2022 installer was created. If you unzip the 2024 update and then run the installer, the installer will overwrite the 2024 files, leaving you with the 2022 version without any updates.
You should be able to sail out of Antigua, though you need to navigate a narrow channel on the east side of the crater. Edit "PROGRAM\InternalSettings.h" and change "DISCOVER_SAIL_TO" from 1 to 0, so that you can use sail-to to get to Muscetto Cove without needing a map. That's a beach on the outside of the crater and it's easier to sail away from there.
Never the less, the fact is my ship when direct sale to the cove outside the caldera is used shows inside the NW corner of the ring. When I change to sailing I'm outside in the cove area... inconsistency with previous versions and indicative of a positioning error in the logic caused by slippage of the grid system under the sailing map. No matter how far I sail in sailing mode on map my ship remains inside the caldera, any other explanation?
B14 is certainly playable because, since I haven't got B15 working on my own PC yet, B14 is what I'm playing. So the use of the past tense in describing B14 is incorrect, and if you are hoping to see a final version of B14, you're going to be waiting for some time! Indeed, next time an update for B14 is released, it's going to include a whole new quest added to "Tales of a Sea Hawk", which will hopefully be copied into B15 as well.
The main snag with B14 is that first you need the original "Pirates of the Caribbean" game because B14 is a mod for that. By contrast, B15 is standalone.
What that means, though, is that my instructions are actually for B14 and I'm assuming they can also be used for B15.
Back to one of your original questions:
By far the biggest parts are "RESOURCE\Models" and "RESOURCE\Textures", about 5GB and 9GB respectively. They're needed regardless of which storylines you keep or discard. The whole of "PROGRAM\Storyline" is about 26MB and the whole of "RESOURCE\INI\TEXTS" is about 5.8MB. So there's little point in separating out the storylines - the common files used by all of them take up so much space, and the individual storylines take so little space. And if your SSD/HDD is so full that deleting the unwanted storylines makes a significant difference then you won't be able to fit both B14 and B15 on there!
I have no intention of trying B15 since the B14 is such a disaster why should I waste more time and frustration on another until the issues corrupting B14 are identified and resolved... why take on more trouble when the present trouble is unresolved? B14 22 has issues found with 21 but not earlier versions, and 22 poses yet another critical failure of program logic or coding that makes the game unplayable as it is. Try sailing into Antigua and then leaving... let me know what happens.
B14 is certainly playable because, since I haven't got B15 working on my own PC yet, B14 is what I'm playing. So the use of the past tense in describing B14 is incorrect, and if you are hoping to see a final version of B14, you're going to be waiting for some time! Indeed, next time an update for B14 is released, it's going to include a whole new quest added to "Tales of a Sea Hawk", which will hopefully be copied into B15 as well.
The main snag with B14 is that first you need the original "Pirates of the Caribbean" game because B14 is a mod for that. By contrast, B15 is standalone.
What that means, though, is that my instructions are actually for B14 and I'm assuming they can also be used for B15.
Back to one of your original questions:
By far the biggest parts are "RESOURCE\Models" and "RESOURCE\Textures", about 5GB and 9GB respectively. They're needed regardless of which storylines you keep or discard. The whole of "PROGRAM\Storyline" is about 26MB and the whole of "RESOURCE\INI\TEXTS" is about 5.8MB. So there's little point in separating out the storylines - the common files used by all of them take up so much space, and the individual storylines take so little space. And if your SSD/HDD is so full that deleting the unwanted storylines makes a significant difference then you won't be able to fit both B14 and B15 on there!
Installed 22 takes 19GB ... is that what you are seeing?
I don't know anything about the bug with the second ship. You can't save while boarding because even if you did change the game to allow it, the saves wouldn't work properly. I'm not sure why you can't save while sailing, unless it's while there's a battle in progress, in which case again the save would probably not work properly.
It's while I've disengaged from the battle having captured my target and leave the combat until the "All-Clear" theme plays any attempt to save is blocked with "can't save while sailing" non-sense. It is a set condition in the program by a Y/N logic switch which can be removed to remove this condition that is causing the lock-out. The bug with sinking the second (escort) ship is a programming error in a revision of the program creating a conflict within the logic that has no action associated with a logic step. A logic flow chart, if one exists, would show a link with a blank action resulting from the Y switch trigger. Or, could simply be save overflow of the available save file limit crashes the game because of an infinite loop error... with no "timeout" step. Since it's a freeze MS gives no fault diagnostic of the critical file fault.