Out of Memory: Increase Swap File Size - Error

posted on September 14th, 2011, 9:25 pm

Alright before anyone goes and tells me that this is because of a missing " (or 1 to many ") in a file, I already know that. I am now getting this error with my Dominion Alliance Race. Recently, I set all the Dominion, Breen, and Son'a ships to be in the stock Armada II ODF form. I was very careful when I did this and didn't remove any " or add any. I just copied and pasted the needed information from the ship's ODF file that I was editing to one that was in the form that I wanted that I copied to my desktop. I checked after for any errors and there wasn't any I moved on to the next ship that needed this type of fixing.

I only found out that this error was occuring because I decided to test out the Dominion Alliance through the Map Editor. The first Sub-section for ships crashed then and gave me that error. I then looked through all the ships that were named in that file and checked them over for any errors (at least the ones that were in there that I edited) no missing anything was in the file.

So I moved on to the next given set of ships, the second one. The crash happened again with the same error, so I repeated the same thing that I did for the first one but then again no go on finding an error.

So last I decided to see if the stations caused this problem. So I started from the bottom up of all the listed Station files for the Map Editor. The first (last one in the ed_dom.odf file) didn't cause the "Out of Memory: Increase Swap File Size" Crash, but the next one up did. That one has 4 shipyards in it. Is the problem possibly related to one of the ships in those four shipyards or is it the shipyard itself?

posted on September 14th, 2011, 10:12 pm

Hmm, well I never had any OoM crashes except for the missing quotation marks, so I'm not sure I can halp you on this one. The first thing I'd suggest is double-checking the map editor odfs for any errors (unlikely, but always a possibility). Next thing would be yards. Specifically, the number of ships they can build. I know there's a limit for them (14 or 13 methinks), so that might be responsible as well. One other thing I could think of: You specifically mention stock A2 odfs. Does that imply that you had FO odfs for them before? If so, I'd check for any left-over ODF comands stock doesn't have.

These are the ones I would check for in your place, if it's note of these then hopefully someone else can figure it out.

posted on September 14th, 2011, 10:46 pm

Hmm, well I never had any OoM crashes except for the missing quotation marks, so I'm not sure I can halp you on this one. The first thing I'd suggest is double-checking the map editor odfs for any errors (unlikely, but always a possibility). Next thing would be yards. Specifically, the number of ships they can build. I know there's a limit for them (14 or 13 methinks), so that might be responsible as well. One other thing I could think of: You specifically mention stock A2 odfs. Does that imply that you had FO odfs for them before? If so, I'd check for any left-over ODF comands stock doesn't have.

These are the ones I would check for in your place, if it's note of these then hopefully someone else can figure it out.

There is no ODF files from Fleet Ops in my Armada II Install. I have some SODs but modeled ODFs after my Stock ODF files, that is if I am using a ship or station from FO in my mod after all, it is a personal mod.

Every Build Menu that I have goes from 0 - 13 (the same as the some of the stock construction ships) I was told that 13 has to be the last # but you have to start at 0 so thus I would say 14 is the highest a build menu can go.

Ok, in the attached .ZIP Files are only the ODF files for each of the given races ships that are being apart of the Dominion Alliance. They are the ones that I edited. Note, I do have the files that I created that are part of

Code: Select all

#include ".odf"

, I have also checked them for errors as well.

The ODF files in the ZIP files I have checked and double checked and I am still missing any possible cause for the "Out of Memory: Increase Swap File Size" Error.

Attachments

Son'a.zip

(18.73 KiB) Downloaded 318 times

Cardassians.zip

(138.02 KiB) Downloaded 283 times

Dominion-Jem'Hadar.zip

(66.03 KiB) Downloaded 341 times

Breen.zip

(21.53 KiB) Downloaded 340 times

posted on September 14th, 2011, 11:27 pm

Actualy, you can only have 12 buildable items per list in a2, this might be you problem

posted on September 14th, 2011, 11:28 pm

I think going over would just cause the item to not appear in the list.

posted on September 15th, 2011, 12:55 am

Actualy, you can only have 12 buildable items per list in a2, this might be you problem

It's 14 total build items, and as Tyler pointed out it will just cause the item to not appear in the buildlist

[jetnova16]

posted on September 15th, 2011, 2:28 am

Last edited by jetnova16 on September 15th, 2011, 2:34 am, edited 1 time in total.

Actualy, you can only have 12 buildable items per list in a2, this might be you problem

You are wrong on this. I have had Armada II since 2007 and have had 14 ships in a shipyard or starbase to be built and the same number of stations on construction ships and every last buildable ship or station (on either the construction ship or the starbase/shipyard) was totally available to me. I have even counted the number of ships in available to build and I started at 0 and the last buildable item was # 13 (0 - 13 = 14 buildable).

It's 14 total build items, and as Tyler pointed out it will just cause the item to not appear in the buildlist

I think I got into explaining that and stating why I disagreed about not being able to build 14 (0-13) before I saw your post.

Well discussing the amount of buildable items that you can have in the game hasn't yet found the cause to my: "Out of Memory: Increase Swap File Size" Error. I did though go back and edit some of the Cardassian Units and I noticed that the csensor.odf wasn't edited, fixed that problem and noticed that the original file that worked in the game had a " out of place. Who knows though, that could be the cause but since it never happend before and I have had the Cardassian Full Race Replacement mod in my game for almost a year or 2 now, I don't know if that was the cause though.

posted on September 15th, 2011, 2:31 am

I think OOm is caused by names that are too long(specifically check the list of ship names) and missing ,'s in the DLS.h

Other than that, there is no other cause unless you really have limited RAM.

[jetnova16]

posted on September 15th, 2011, 2:37 am

Last edited by jetnova16 on September 15th, 2011, 2:40 am, edited 1 time in total.

I think OOm is caused by names that are too long(specifically check the list of ship names) and missing ,'s in the DLS.h

Other than that, there is no other cause unless you really have limited RAM.

The longest ship or station name that I have in the game is actually a Cardassian Stock Unit Name. And that is the Cardassian Super Station and since that name is long, I would have to count the size o the file names as not the cause.

Code: Select all

cardassian_super_station.odf

As for RAM, I have almost 2GB of RAM in my laptop, surely more than enough RAM to run Star Trek Aramda II and even Star Trek Legacy, LOL

I think that the answer is somewhere in the ZIP files I attached to my second post. Which I have kept combing through htose files all last night and until 9:30AM today (EST).

posted on September 15th, 2011, 3:09 am

I don't know enough to help you out, but I think Adm Zaxxon was referring to the ship name list inside the odf, not the names of the odf files themselves.

posted on September 15th, 2011, 3:33 am

I don't know enough to help you out, but I think Adm Zaxxon was referring to the ship name list inside the odf, not the names of the odf files themselves.

I am not sure really, but I don't think that is the problem here, I am really using the same ship names that came with the original versions of the ships. I never edit the names, just add some but never that long.

posted on September 15th, 2011, 9:14 am

i would try removing the stuff unit by unit until the crash disappears. That way you might find out which unit causes the crash.

[Anonymous]

posted on September 15th, 2011, 11:40 am

Last edited by Anonymous on September 15th, 2011, 5:34 pm, edited 1 time in total.

The longest ship or station name that I have in the game is actually a Cardassian Stock Unit Name. And that is the Cardassian Super Station and since that name is long, I would have to count the size o the file names as not the cause.

Code: Select all

cardassian_super_station.odf

As for RAM, I have almost 2GB of RAM in my laptop, surely more than enough RAM to run Star Trek Aramda II and even Star Trek Legacy, LOL

I think that the answer is somewhere in the ZIP files I attached to my second post. Which I have kept combing through htose files all last night and until 9:30AM today (EST).

that could definitly do it.  try removing that ship from your game completely or shortening the name.

posted on September 15th, 2011, 8:44 pm

i would try removing the stuff unit by unit until the crash disappears. That way you might find out which unit causes the crash.

I did something like that with the help of the Map Editor. I first found out though that any building ship or station also had to be commented out from either a construction ship, starbase, or shipyard. All because it appears the game when checking one ship actually seems to check all the way down the line of wverything that is buildable. Once that minior problem was fixed I was able to narrow the crash down to the ship being listed in ed_comb4.odf, thus in that file I commented out all the ships and left only one in and if that worked uncommented the next in line until I got the "Out of Memory: Increase Swap File Size" message. After I got it, I recommented out that ship and commented in all the ones after it to make sure it was the only problem.

Well the ship causing the problem is "cminelayer".
I have checked and checked this file over and over again but I can't find any problems. The weapons on it are connected to other ships except some of the mines, the special weapons.
I checked the special weapon files for the mines and found nothing that involves a missing ".
Now I am attaching the ship, the special weapons.
For the #include "warship.odf",  Iknow that can't be the problem file because other ships are using that as well and they don't do this.

I have looked through the attached files more than once and haven't found what could be causing the "Out of Memory: Increase Swap File Size" Error. I am starting ot wonder if it has something to do with the ship and model being from the Star Trek Armada II Future Wars mod. I know that the ships and stations there have unique emitters and sprites, but I have the information added to my files that needed it.

Attachments

[The extension has been deactivated and can no longer be displayed.]

[The extension has been deactivated and can no longer be displayed.]

[The extension has been deactivated and can no longer be displayed.]

[The extension has been deactivated and can no longer be displayed.]

[The extension has been deactivated and can no longer be displayed.]

[jetnova16]

posted on September 15th, 2011, 8:55 pm

Last edited by jetnova16 on September 15th, 2011, 8:59 pm, edited 1 time in total.

that could definitly do it.  try removing that ship from your game completely or shortening the name.

The

Code: Select all

cardassian_super_station.odf

is actually a stock file name. Meaning I never named that station, and no one else did either. It was and is how Activison (the creators of Star Trek Armada II) named the file. If you check the original game and the original tech1 file you will find it already listed there in that length. Also they even have a longer ship (station) name, it is a Species 8472 station by the name of

Code: Select all

8472_ShipUpgradeResearch.odf

.

On further examination,

Code: Select all

cardassian_super_station.odf

&

Code: Select all

8472_ShipUpgradeResearch.odf

have the exact same number of character in their name counting the .odf part, 28 characters. So I would have to say that the stock version of Armada II can hold an odf file name of 28 characters or less.