[Tempest]

The source files might be the problem.

Try scanning the ships.tbl for ";". This will cause the shiplist to malfunction and several bad, bad things to happen if you put a semicolon in the wrong place. If you find any semicolons where they shouldn't be, remove them. I've gotten my list cut off before because I had a semicolon in the description of my ships. Alternatively, try running a debug FRED build and seeing what it says when it loads ships.tbl.

[CaptainX]

Okay, doing that now. Will update shortly.

UPDATE: I get several errors when running FRED debug mode, but they are all related to missing weapons - one of the ships I converted over hasn't had its weapons changed to WC weapons yet.

What are appropriate places to find ";" in the ships.tbl file? There are several in there, and they are used in a coupla different contexts.

I see everal comment lines which are proceeded by either one or two semicolons, like this:

; comment
;; comment

I also see a coupla lines that look like this:

; $ND:    42 42 244

Any insights?

[CaptainX]

Update above ^^^

[Tempest]

Comments should be commented out by:

; This is a comment
Or
;; This is also a comment, but the second semicolon makes no difference

The ND is short for No Dim, which was FS2's origional hackish support of lights. Basically, it's an RGB value of what color to not dim as the ships were rendered, so that they would glow in the darkness. These are left out for good reason, as we now have magical glow maps.

The weapons problems probably aren't the problem. And where did you get your ships table? All I can suggest is a thorough examination of each entry, or perhaps the deletion of all description fields. :V: Actually had this problem too- with one of their missions, they accidentally put a semicolon in the briefing stage, and didn't realize the semicolon was the problem, so they just ended up deleting it. In all honesty, that's kind of difficult given your lack of expertise with the ships.tbl.

[CaptainX]

Does anyone want to take a look at the ships.tbl file and see what they can find? It's the WCS version of it and only has about 30 ships in it.

I desperately need to fix this problem.

[Wanderer]

It would be somewhat easier to check the ships.tbl file if there was one to be checked...

[karajorma]

I notice you don't mention running the debug builds which should be your first port of call for something this strange (Debug builds have much better error reporting).

Check the fs2_open.log you'll find in your data folder too.

[CaptainX]

It would be somewhat easier to check the ships.tbl file if there was one to be checked...

I didn't figure it was necessary to post it until someone actually wanted to look at it. I've attached it now.

I notice you don't mention running the debug builds which should be your first port of call for something this strange (Debug builds have much better error reporting).

When I ran the FRED2 debug builds, the only errors I received were ones I was expecting - weapons errors from ships that have not had their weapons changed from FS2 weps to WC weps.

[attachment deleted by admin]

[karajorma]

Ummmmm. You don't have 59 classes on that table as far as I can see.

[CaptainX]

Yes I know. I have 32 ships that have their own separate tbm files.

[karajorma]

What happens if you stick together two of the tbm files? Does it now stick at 60?

[CaptainX]

No luck.

The limit remains the same regardless of how many ship tbms I combine.

[karajorma]

Stick the lot together and post it. Let's see if any of us can replicate this.

[CaptainX]

The whole thing? That's a LOT of files... the entire folder consists of 963 MB.

Do you want me to post EVERYTHING, or only certain files?


EDIT: Actually, if you guys already have WC Saga, then the total amount of files is about 350 MB uncompressed.

[karajorma]

Just the tables

[CaptainX]

Roger that, they're attached.

[attachment deleted by admin]

[karajorma]

Hmmmm. I'm getting the same error you're getting but with all the errors in the debug output it's really hard to figure out where the cause is.

I recommend getting all the errors that the debug build complains about fixed. Check the logs too cause there are a lot of errors like this

Code: [Select]

At least one of the following tags was used on ship Amadeus Class, subsystem ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌContainer01a:
+untargetable
+carry-no-damage
+use-multiple-guns
+fire-down-normals
Use of deprecated subsystem syntax.  Please use the $Flags: field for subsystem flags.
Or this

Code: [Select]

WARNING:  Animation trigger #0 on subsystem 'turret01a', for ship 'Caernaven Class', has a negative reverse_start value!  Capping it at 0!
Once those are fixed it will be a lot easier to track down the actual cause.

[CaptainX]

I'll check those when I get home at 3pm CST, I'm at work at the moment.

Were you using the main exe debug build or the FRED2 debug build? I remember running the FRED2 build but haven't tried the exe build yet.

The only errors that came up in FRED were related to the Archangel battleship, which I am converting over to WCS from FS2. I haven't had a chance to change all the weapons on it to WC weapons - they're all still FS2 weapons, which are obviously throwing up some errors.

When I get home, I'll check into each error and get to work on fixing them. If I find any I don't know how to fix, I'll post here.

Someone be sure to tell Scooby to be watching this thread, these are all his ships and tables, after all 

[karajorma]

I was using a 3.6.10 build since that picks up a few extra problems that 3.6.9 doesn't.

[CaptainX]

Karajorma,

I'm not getting any of the errors you described above. I get several errors, but they are all related to not finding the glow textures for weapons. Nothing like you have listed above.