View Issue Details

IDProjectCategoryView StatusLast Update
0000592FSSCPtablespublic2007-10-22 03:33
ReporterWMCoolmon Assigned Totaylor  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0000592: XMT weapons not working properly
DescriptionAccording to StratComm there's an error when using +nocreate for the modular weapons table.

See this thread: http://dynamic.gamespy.com/~freespace/forums/showthread.php?s=&threadid=35797

Mostly this is a TODO for myself to reproduce & fix it.
Additional Information#Secondary Weapons
$Name: EMP Adv.
+nocreate
$Model File: EMPulse.pof
#End
TagsNo tags attached.

Activities

StratComm

2005-10-16 00:39

reporter   ~0003571

Last edited: 2005-10-16 00:55

Don't waste time chasing this down and close it. I just did a little more testing and the error has nothing to do with that particular modular table. Turns out there's something in my mod directory that is independent of this but which only causes problems with the builds with extensible tables. It'd be a ship that's causing the problem, but I need to chase that down as that particular directory is a bit of a mess at the moment.

Well, turns out there were two bugs that were crashing those builds. One was a semicolen in a tech description (I know better), but the other appears to be that in my primary mod directory (which contains all my experimental non-retail stuff), the game has "lost" the identity of the countermeasure POF. Any idea where that is even defined?

edited on: 10-15-05 20:55

WMCoolmon

2005-10-17 01:36

developer   ~0003575

I'm not even sure what you're talking about. Is the game displaying an error?

StratComm

2005-10-17 06:22

reporter   ~0003577

Last edited: 2005-10-17 06:24

Yeah, that's me trying to figure out what the hell was going on. I'm getting a crash with your xmt-enabled build with one particular mod when the game is trying to load the model after interceptor.pof (which should be cmeasure01.pof, the countermeasure) and the debug spew reports that the model it's attempting to load has a null string for its name. Debug spew likewise reports that an assert failed because the string was of length 0 (to paraphrase the assert syntax, as I don't have it in clipboard anywhere). I'm not redefining countermeasures anywhere, it doesn't happen with retail tables, and I can't reproduce it outside of that one mod directory thus far. Removing all tables from that mod directory doesn't help at all, so I really don't know what it's doing.

edited on: 10-17-05 02:24

StratComm

2005-10-17 07:34

reporter   ~0003579

Last edited: 2005-10-17 08:00

Well that was strange. The error actually was coming from DaBrain's shockwave.pof that was in the models directory, which the game was trying to load as a null-named model (???). No earthly idea where that came from or why it was causing the crash. Minor bug still, though this should probably be renamed.

Out of curiousity, what builds are supposed to support these extensible modular tables and the +nocreate flag?


EDIT: Realized that shockwave.pof was not, in fact, old data. Bugnote updated.

edited on: 10-17-05 04:00

WMCoolmon

2005-10-18 03:56

developer   ~0003586

Recent CVS builds should support them.

So is there any reason to keep this open? (Check that last bug on the most recetn CVS, I did something particularly stupid in some of the weapons table code, although I doubt you used the field in question.)

StratComm

2005-10-18 09:06

reporter   ~0003587

No, there's not. If anything comes up, I'll open a new one after I've had the chance to do some testing, so go ahead and close this bug.

taylor

2005-10-19 20:18

administrator   ~0003598

Try the next available build from redmenace. I just fixed a problem in CVS having to do with spawn type weapons and parsing. It would always crash (or cause strange errors) if you were using a weapon tbm.

This probably didn't get noticed sooner because of the buggy way that WMCoolmon handled spawn type weapon names. This created a big memory problem which I fixed but with it broken it masked the parsing problem. With the fix in place it would run into an out-of-bounds problem after parsing tbms.

WMCoolmon

2005-10-20 02:09

developer   ~0003599

Again, taylor, thanks. I'd managed to push the memory of even doing that to the back of my mind so I probably wouldn't've caught it for awhile. :nod:

Issue History

Date Modified Username Field Change
2005-10-15 18:24 WMCoolmon New Issue
2005-10-15 18:25 WMCoolmon Status new => assigned
2005-10-15 18:25 WMCoolmon Assigned To => WMCoolmon
2005-10-16 00:39 StratComm Note Added: 0003571
2005-10-16 00:55 StratComm Note Edited: 0003571
2005-10-17 01:36 WMCoolmon Note Added: 0003575
2005-10-17 06:22 StratComm Note Added: 0003577
2005-10-17 06:24 StratComm Note Edited: 0003577
2005-10-17 07:34 StratComm Note Added: 0003579
2005-10-17 08:00 StratComm Note Edited: 0003579
2005-10-18 03:56 WMCoolmon Note Added: 0003586
2005-10-18 09:06 StratComm Note Added: 0003587
2005-10-19 20:18 taylor Note Added: 0003598
2005-10-20 02:09 WMCoolmon Status assigned => closed
2005-10-20 02:09 WMCoolmon Note Added: 0003599
2007-10-22 03:33 taylor Assigned To WMCoolmon => taylor
2007-10-22 03:33 taylor Resolution open => fixed