jedidia
shoemaker without legs
There seem to be some issues with scenario files that have a whole lot of vessels in them. We currently have one where I would guess the number around 200, and only few of them get loaded. There are two things that strike me as interesting:
First, there isn't a hard cut-off. If we make the scenario a bit smaller, suddenly all vessels are present. That is, there are more vessels present than when the larger scenario was loaded so it seems that the larger scenario just terminates reading somewhere (there's no premature END_SHIPS line anywhere, I made sure of that). So this can't be a case of "that's too many vessels, I'll just not load more than X". It seems more like "There's too many vessels, I'll just load an arbitrary number of them (although the arbitrary number does seem to be constant, as are the vessels loaded, I just can't make out a clear pattern).
The second thing is that there's absolutely nothing in the log. I would rather assume that some meshes were not found or some vessels couldn't be created or somesuch, but the log is just pretending as if everything went just perfectly. I ave my share of expierience with vessels unable to load for different reasons, but usually the log always gave me a hint on where the problem was. This time it seems that the scenario gets loaded just fine.
Here's the scenario in question, if you want to take a look at it, though I'm afraid you won't be able to run it:
http://www.icedown.net/images/IMSAssemblyComplete.scn
Are there known occurences of this behavior with large scenario files?
---------- Post added at 09:46 AM ---------- Previous post was at 09:02 AM ----------
A bit more info: The scenario does indeed terminate loading at line 477. All vessels before that are loaded, none after. I deliberately deleted a few config files of vessels that are loaded later, the log doesn't bother to mention them, so the parser indeed does not reach those entries. Anyone knows what this might be caused by?
First, there isn't a hard cut-off. If we make the scenario a bit smaller, suddenly all vessels are present. That is, there are more vessels present than when the larger scenario was loaded so it seems that the larger scenario just terminates reading somewhere (there's no premature END_SHIPS line anywhere, I made sure of that). So this can't be a case of "that's too many vessels, I'll just not load more than X". It seems more like "There's too many vessels, I'll just load an arbitrary number of them (although the arbitrary number does seem to be constant, as are the vessels loaded, I just can't make out a clear pattern).
The second thing is that there's absolutely nothing in the log. I would rather assume that some meshes were not found or some vessels couldn't be created or somesuch, but the log is just pretending as if everything went just perfectly. I ave my share of expierience with vessels unable to load for different reasons, but usually the log always gave me a hint on where the problem was. This time it seems that the scenario gets loaded just fine.
Here's the scenario in question, if you want to take a look at it, though I'm afraid you won't be able to run it:
http://www.icedown.net/images/IMSAssemblyComplete.scn
Are there known occurences of this behavior with large scenario files?
---------- Post added at 09:46 AM ---------- Previous post was at 09:02 AM ----------
A bit more info: The scenario does indeed terminate loading at line 477. All vessels before that are loaded, none after. I deliberately deleted a few config files of vessels that are loaded later, the log doesn't bother to mention them, so the parser indeed does not reach those entries. Anyone knows what this might be caused by?
