Author Topic: ships/weapons.tbl various warnings/errors  (Read 2820 times)

0 Members and 1 Guest are viewing this topic.

Offline asyikarea51

  • 210
  • -__-||
ships/weapons.tbl various warnings/errors
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:)

Code: [Select]
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

 

Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: ships/weapons.tbl various warnings/errors
Post your tables and the full fs2_open.log

 

Offline asyikarea51

  • 210
  • -__-||
Re: ships/weapons.tbl various warnings/errors
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]
« Last Edit: March 15, 2014, 12:21:15 am by asyikarea51 »

 

Offline zookeeper

  • *knock knock* Who's there? Poe. Poe who?
  • 210
Re: ships/weapons.tbl various warnings/errors
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:

Code: [Select]
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.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: ships/weapons.tbl various warnings/errors
Code: [Select]
Ships.tbl is : INVALID!!!!
Weapons.tbl is : INVALID!!!!
These sound problematic.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: ships/weapons.tbl various warnings/errors
No, I don't think they are. I've seen that kind of warning all over the place in perfectly good logs.

 

Offline asyikarea51

  • 210
  • -__-||
Re: ships/weapons.tbl various warnings/errors
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
Code: [Select]
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...

 

Offline pecenipicek

  • Roast Chicken
  • 211
  • Powered by copious amounts of coffee and nicotine
    • Skype
    • Steam
    • Twitter
    • PeceniPicek's own deviantart page
Re: ships/weapons.tbl various warnings/errors
Code: [Select]
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.
Skype: vrganjko
Ho, ho, ho, to the bottle I go
to heal my heart and drown my woe!
Rain may fall and wind may blow,
and many miles be still to go,
but under a tall tree I will lie!

The Apocalypse Project needs YOU! - recruiting info thread.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: ships/weapons.tbl various warnings/errors
What effect does this repeated "+Description:" line have?
Code: [Select]
$Name: Hornet
+Title: XSTR("", 3325)
+Description:
+Description:
XSTR("", 3326)
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: ships/weapons.tbl various warnings/errors
Probably ****s everything.

 

Offline The E

  • He's Ebeneezer Goode
  • 213
  • Nothing personal, just tech support.
    • Steam
    • Twitter
Re: ships/weapons.tbl various warnings/errors
Yeah, I'm pretty sure the parser's going to quietly die on that.
If I'm just aching this can't go on
I came from chasing dreams to feel alone
There must be changes, miss to feel strong
I really need lifе to touch me
--Evergrey, Where August Mourns

  

Offline asyikarea51

  • 210
  • -__-||
Re: ships/weapons.tbl various warnings/errors
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.
« Last Edit: March 15, 2014, 12:39:30 pm by asyikarea51 »