Hard Light Productions Forums
Modding, Mission Design, and Coding => The Modding Workshop => Topic started by: asyikarea51 on March 14, 2014, 11:34:13 pm
-
I'm trying to port an old mod to use MediaVPs 2014 from 3.6.12 and I'm getting the following errors, anyone have a more layman explanation/roughly point me to the right direction on fixing the problem than what is stated in the fs2_open.log? (I have not touched FSO in at least 2 years, I am very very n00b now :banghead:)
WARNING: "Model 'fighter04.pof': insignia uses an invalid LOD (-1)" at modelread.cpp:2211
Model vortex.pof has a null moment of inertia! (This is only a problem if the model is a ship.)
WARNING: "Submodel <Selection> in model <vortex.pof> has a radius <= 0.1f" at modelread.cpp:1235
WARNING: "Model 'Medusa.pof': insignia uses an invalid LOD (-1)" at modelread.cpp:2211
WARNING: "Model 'Medusa.pof': insignia uses an invalid LOD (-1)" at modelread.cpp:2211
ASSERTION: "ti->texture.bitmap_id != -1" at trails.cpp:193
Weapon trail could not be loaded
I get the assertion when I try to fire off Hornets; I looked at my tables and the code looks okay... i.e. I haven't found where I'm wrong yet :nervous: unless this mod needing to load another mod to "cancel out" the MediaVPs tbm's has something to do with it. (several tbm's trying to cancel out each other)
I did this in the first place because of the MediaVPs tbm's preventing me from changing the missile lock range if I remember, among other things... POF related as well I think
-
Post your tables and the full fs2_open.log
-
I am not able to post the tables right now because they're a mess, with tbm's here and there that I'm slowly cleaning up. Attached the log if it helps.
EDIT: Attached the relevant missile entries that I could find. (more concerned with getting rid of the assert)
[attachment deleted by an evil time traveler]
-
For what it's worth, these are about exactly what they say and it's up to you whether they indicate a problem or not:
Model vortex.pof has a null moment of inertia! (This is only a problem if the model is a ship.)
WARNING: "Submodel <Selection> in model <vortex.pof> has a radius <= 0.1f" at modelread.cpp:1235
The latter is a warning simply because it's more likely that the radius of the submodel is messed up somehow, than that the submodel is really that small. The latter's still possible, of course.
The weapon trail thing must be a messed up trail bitmap reference somewhere.
-
Ships.tbl is : INVALID!!!!
Weapons.tbl is : INVALID!!!!
These sound problematic.
-
No, I don't think they are. I've seen that kind of warning all over the place in perfectly good logs.
-
These tables used to work
perfectly reasonably well before - I only remember crashing on WoD sounds back when I did up these tables rather than anything table related, and if the game spewed errors before, I more-or-less could figure out what was going on... only this time I don't. :lol: I don't know what changed between different builds and the VPs, but that's one point of this thread.
MoI I can just recalculate the thing in PCS or w/e, that vortex.pof is from INFR1 so it's old enough... I suppose...
Btw, when I load PCS I get this
file "", line 54: "=" expected.is it something I should worry about? (Especially since I resize pof's?)
At present it's the bothersome assert on the Hornet missiles that I can't pin down yet, and I think it's affecting all of them, not just one. (Is missiletrail05 the cause? But MediaVPs alone obviously doesn't crash. :nod:)
Pull trigger in flight, instant assert. Back to my own devices to find this error then...
-
Ships.tbl is : INVALID!!!!
Weapons.tbl is : INVALID!!!!
These sound problematic.
for the record, unless something was changed, those indicated if the tables were valid for multiplayer. nothing to do with their general validity.
-
What effect does this repeated "+Description:" line have?
$Name: Hornet
+Title: XSTR("", 3325)
+Description:
+Description:
XSTR("", 3326)
-
Probably ****s everything.
-
Yeah, I'm pretty sure the parser's going to quietly die on that.
-
Damn, I missed that? :banghead:
Had I not put up the tables, I would've missed it, so yey... or something.
EDIT: Nope, still getting crashes with the missiles, still finding unless I call it a day.