I also agree with Jeffrey.
Increasing the number of the people fighting is ok, but the crew ratio between the 2 ships must be taken into consideration when spawning the sailors.

Jeffrey:
OK, with these 4 arrays, I can’t find a way to resize them and play a previous save game: Locations, Characters, Islands, Colonies. A new game must be started to avoid problems. Items, Ships, etc. are OK if a reinit is called and it’s because of where they are defined/stored…in .c code not of global scope.

The Locations, Chara…

[Read more]

Jeffrey:
OK, with these 4 arrays, I can’t find a way to resize them and play a previous save game: Locations, Characters, Islands, Colonies. A new game must be started to avoid problems. Items, Ships, etc. are OK if a reinit is called and it’s because of where they are defined/stored…in .c code not of global scope.

The Locations, Chara…

[Read more]

I started another game with max_locations = 705. Tested a boarding and everything was ok.

Changed the max_locations to 707, reloaded the save and the boarding crashed.

In the error.log there is this:

RUNTIME ERROR - file: seadogs.c; line: 867
invalid index 705 [size:705]
RUNTIME ERROR - file: seadogs.c; line: 867
invalid index 706…[Read more]

If I understood correctly, he started with the patch 1.5.7, that has a max locations of 700.

Then he applied your patch, that includes my modified globals.c with two more locations (one cabin for “peace” and one cabin for boarding), taking the max locations to 702. And his game didn’t crash! He only had the empty scene with only water.

So why…[Read more]

No, even after a reinit of all the locations, the boarding crashed with MAX_LOCATIONS = 703.
This is not really a problem now, but it means that if new locations will be added, a new game is required, even after a reinit…

No, even after a reinit of all the locations, the boarding crashed with MAX_LOCATIONS = 703.
Now this is not really a problem now, but it means that if new locations will be added, a new game is required, even after a reinit…

If you reinit all the locations, I see that LocationInitBoarding(n) is called at the end of InitLocations(); so there is no need to call it again, and also to have that 631. And “Locationsinitboarding.c” is included in InitLocations().

The console.c should be like the following I think, right? Just to avoid unnecessary things.

#include…[Read more]

It seems that changing the MAX_LOCATIONS in an existing game causes crashes when boarding a ship…

I never experienced this when I tested the new cabins, but probably I always started the test games with the updated MAX_LOCATIONS number, so I didn’t need to change it after the start.

But at this point I wonder why boardings didn’t crash when…[Read more]

It seems that changing the MAX_LOCATIONS in an existing game causes crashes when boarding a ship…

I never experienced this when I tested the new cabins, but probably I always started the test games with the updated MAX_LOCATIONS number, so I didn’t need to change it after the start.

But at this point I wonder why boardings didn’t crash when…[Read more]

It seems that changing the MAX_LOCATIONS in an existing game causes crashes when boarding a ship…

I never experienced this when I tested the new cabins, but probably I always started the test games with the updated MAX_LOCATIONS numbers, so I didn’t need to change it after the start.

But at this point I wonder why boardings didn’t crash when…[Read more]

It seems that changing the MAX_LOCATIONS in an existing games, causes crashes when boarding a ship…
I never experienced this when I tested the new cabins, but probably I always started the test games with the updated MAX_LOCATIONS numbers, so I didn’t need to change it after the start.

But at this point I wonder why boardings didn’t crash when…[Read more]

Mmmm try to put the number in #define MAX_LOCATIONS back to 702.
I tried to replicate your problem, and when I changed that number to 703 the CTDs started.

And putting back 702, the boarding didn’t crash anymore. Actually 702 is right, it was my mistake to make you change it.

Mmmm try to put the number in #define MAX_LOCATIONS back to 702.
I tried to replicate your problem, and when I changed that number to 703 the CTDs started.

engini.ini, in the directory were the game executable is, find these lines and make sure they are like this:
tracefilesoff = 0
debuginfo = 1

Then, after the game crashes, you should see 3 files in the game directory: compile, error and system. Post them here.

Strange, never happened to me during testing. Usually I just had the empty scene with only water. Do you have logging enabled? You should post the logs here.

Mmmm this may have mixed things up! Anyway, reinstall Jeffrey’s patch and then do the following.

The console.c is correct. I guess you didn’t add new locations on your own, so all you have to do is press F4 after loading your save. You should read ‘operation successful’.

Also, to be sure, check that ‘#define MAX_LOCATIONS’ in Programglobals.c is…[Read more]

I know what that is. You are using Jeffrey’s patch/files with a previous save game, right?

If I recall correctly, he included my new cabin for caravels. When using an old save, you must reinit the boarding locations or else you will get this bug. Can you post the content of this file: Programconsole.c? I don’t know if he included the necessary…[Read more]

I also found it kind of funny that he just posted the content of a log file, knowing that on the log it’s possible to write whatever one wants. The same for the game cover.

I don’t know what to think about the other story, that the game is DX 8 but can be made DX 9 simply changing paths and other things he said. My experience in programming is…[Read more]

I quickly tried the new DX 9 version, and the FPS drop seemed disappeared. Good job!

I didn’t check if the framerate is still lower than that of the DX 8 version, but this time the game is playable. I will try it again though, to be really sure!