[PotzUK]

Aye, I like them too - I'm using them in the campaign I'm working on...

OK, here are the debug errors I've found so far

Code: [Select]

Warning: Could not load in the HUD shield ani: shieldNfight1

File:c:\fs2_open\code\hud\hudshield.cpp
Line: 855
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    fs2_open_d-P420060731.exe 008243b9()
    fs2_open_d-P420060731.exe 006fb180()
    fs2_open_d-P420060731.exe 006e6eff()
    fs2_open_d-P420060731.exe 006e7031()
    fs2_open_d-P420060731.exe 006e71be()
    fs2_open_d-P420060731.exe 006f4a34()
    fs2_open_d-P420060731.exe 008a54bd()
    fs2_open_d-P420060731.exe 006f337c()
    fs2_open_d-P420060731.exe 008a5adc()
    fs2_open_d-P420060731.exe 006f6a65()
    fs2_open_d-P420060731.exe 006f6ce9()
    fs2_open_d-P420060731.exe 00b94117()
    kernel32.dll 7c816d4f()
------------------------------------------------------------------


Code: [Select]

Warning: Subsystem "communications" in model "ncarrier.pof" is represented as "communication" in ships.tbl.  Although FS2_OPEN 3.6 and later will catch and correct this error, earlier versions (as well as retail FS2) will not.  You are advised to fix this if you plan to support earlier versions of FreeSpace.

File:c:\fs2_open\code\model\modelread.cpp
Line: 1720
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    fs2_open_d-P420060731.exe 00886c88()
    fs2_open_d-P420060731.exe 008895e8()
    fs2_open_d-P420060731.exe 008246d0()
    fs2_open_d-P420060731.exe 006fb180()
    fs2_open_d-P420060731.exe 006e6eff()
    fs2_open_d-P420060731.exe 006e7031()
    fs2_open_d-P420060731.exe 006e71be()
    fs2_open_d-P420060731.exe 006f4a34()
    fs2_open_d-P420060731.exe 008a54bd()
    fs2_open_d-P420060731.exe 006f337c()
    fs2_open_d-P420060731.exe 008a5adc()
    fs2_open_d-P420060731.exe 006f6a65()
    fs2_open_d-P420060731.exe 006f6ce9()
    fs2_open_d-P420060731.exe 00b94117()
    kernel32.dll 7c816d4f()
------------------------------------------------------------------


Code: [Select]

---------------------------
Assertion Failed!
---------------------------
Assert: sip->subsystems[j].model_num == sip->modelnum

File: c:\fs2_open\code\ship\ship.cpp

Line: 14393

[This filename points to the location of a file on the computer that built this executable]



Call stack:

------------------------------------------------------------------

    fs2_open_d-P420060731.exe 006fb180()

    fs2_open_d-P420060731.exe 006e6eff()

    fs2_open_d-P420060731.exe 006e7031()

    fs2_open_d-P420060731.exe 006e71be()

    fs2_open_d-P420060731.exe 006f4a34()

    fs2_open_d-P420060731.exe 008a54bd()

    fs2_open_d-P420060731.exe 006f337c()

    fs2_open_d-P420060731.exe 008a5adc()

    fs2_open_d-P420060731.exe 006f6a65()

    fs2_open_d-P420060731.exe 006f6ce9()

    fs2_open_d-P420060731.exe 00b94117()

    kernel32.dll 7c816d4f()

------------------------------------------------------------------



[ This info is in the clipboard so you can paste it somewhere now ]





Use Ok to break into Debugger, Cancel to exit.


---------------------------
OK   Cancel   
---------------------------


Code: [Select]

Warning: Invalid subobj_num or model_num in subsystem 'fighterbay01' on ship type 'Nightmare Carrier'.
Not linking into ship!

(This warning means that a subsystem was present in shivan-shp.tbm and not present in the model
it should probably be removed from the table or added to the model.)

File:C:\Languages\Visual Studio Projects\Visual C++\fs2_open_3_6_9\code\ship\Ship.cpp
Line: 5505
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    fred2_open_3_6_9_debug.exe 0051ee47()
    fred2_open_3_6_9_debug.exe 005275ec()
    fred2_open_3_6_9_debug.exe 004ea99f()
    fred2_open_3_6_9_debug.exe 004ea877()
    fred2_open_3_6_9_debug.exe 004eda76()
    fred2_open_3_6_9_debug.exe 004f0044()
    fred2_open_3_6_9_debug.exe 004f1d07()
    fred2_open_3_6_9_debug.exe 004f1cc1()
    fred2_open_3_6_9_debug.exe 004f2b38()
    fred2_open_3_6_9_debug.exe 00432ce4()
    fred2_open_3_6_9_debug.exe 004321c8()
    fred2_open_3_6_9_debug.exe 009aa706()
    fred2_open_3_6_9_debug.exe 009b09a5()
    fred2_open_3_6_9_debug.exe 009bc995()
    fred2_open_3_6_9_debug.exe 009c8d79()
------------------------------------------------------------------


Code: [Select]

---------------------------
Warning!
---------------------------
Warning: Invalid subobj_num or model_num in subsystem 'fighterbay02' on ship type 'Nightmare Carrier'.
Not linking into ship!

(This warning means that a subsystem was present in shivan-shp.tbm and not present in the model
it should probably be removed from the table or added to the model.)


File:C:\Languages\Visual Studio Projects\Visual C++\fs2_open_3_6_9\code\ship\Ship.cpp

Line: 5505

[This filename points to the location of a file on the computer that built this executable]



Call stack:

------------------------------------------------------------------

    fred2_open_3_6_9_debug.exe 0051ee47()

    fred2_open_3_6_9_debug.exe 005275ec()

    fred2_open_3_6_9_debug.exe 004ea99f()

    fred2_open_3_6_9_debug.exe 004ea877()

    fred2_open_3_6_9_debug.exe 004eda76()

    fred2_open_3_6_9_debug.exe 004f0044()

    fred2_open_3_6_9_debug.exe 004f1d07()

    fred2_open_3_6_9_debug.exe 004f1cc1()

    fred2_open_3_6_9_debug.exe 004f2b38()

    fred2_open_3_6_9_debug.exe 00432ce4()

    fred2_open_3_6_9_debug.exe 004321c8()

    fred2_open_3_6_9_debug.exe 009aa706()

    fred2_open_3_6_9_debug.exe 009b09a5()

    fred2_open_3_6_9_debug.exe 009bc995()

    fred2_open_3_6_9_debug.exe 009c8d79()

------------------------------------------------------------------



[ This info is in the clipboard so you can paste it somewhere now ]





Use Yes to break into Debugger, No to continue.

and Cancel to Quit
---------------------------
Yes   No   Cancel   
---------------------------


Code: [Select]

Assert: mp->nverts > 1
File: C:\Languages\Visual Studio Projects\Visual C++\fs2_open_3_6_9\code\Model\ModelRead.cpp
Line: 3397
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    fred2_open_3_6_9_debug.exe 0059d737()
    fred2_open_3_6_9_debug.exe 0059d4a5()
    fred2_open_3_6_9_debug.exe 005270a9()
    fred2_open_3_6_9_debug.exe 0045597f()
    fred2_open_3_6_9_debug.exe 004566d7()
    fred2_open_3_6_9_debug.exe 00455808()
    fred2_open_3_6_9_debug.exe 0043eab7()
    fred2_open_3_6_9_debug.exe 0098e561()
    fred2_open_3_6_9_debug.exe 0098da44()
    fred2_open_3_6_9_debug.exe 0098b5e9()
    fred2_open_3_6_9_debug.exe 0098ba85()
    USER32.dll 77d48734()
    USER32.dll 77d48816()
    USER32.dll 77d4c63f()
    USER32.dll 77d4c665()
------------------------------------------------------------------


[Dark Hunter]

That's the Carrier, not the Destroyer. The first two look like really simple fixes, don't know about assertations though...

[karajorma]

Right. Some of these are somewhat self explainatory.

1) Your HUD.tbl (if you have one, if not it in another table or tbm) is specifing that the nightmare fighter has a shield animation called shieldNfight1 but the game can't find it. Not certain of the solution but I'm sure someone who knows more about tabling can explain.

2) figure out what ncarrier.pof is used by (Nightmare Carrier most likely). Scroll down from the start of it's table entry and change communication to communications. End of problem

3) Not sure about this one. I've seen it earlier this week though.

4) Does the nightmare carrier actually have fighterbays so that it can launch fighters? If not they should be added. If so then the table entry doesn't match them exactly. Grab modelview from my FAQ and check the names of the subsystems against what you have in the tables.

5) As above

6) No idea

[Wanderer]

Hasnt HUD.tbl been buried for a long time now? That is isnt all that currently handled via ships.tbl?

[Dark Hunter]

No, it hasn't. You still need to put shield animations into the hud.tbl for them to take effect. The line of code is extremely simple:


$Shield:            <name of shield file>


That's seriously all hud.tbl needs. But it can only handle 40 entries total (I think 29 are used by the main game's fighters/bombers).

[karajorma]

I believe Wanderer is actually correct and Hud.tbl is obsolete but the tables for the nightmares are pretty old so it's easy to imagine that they'd have a hud.tbl with them.

[Goober5000]

1) Your HUD.tbl (if you have one, if not it in another table or tbm) is specifing that the nightmare fighter has a shield animation called shieldNfight1 but the game can't find it. Not certain of the solution but I'm sure someone who knows more about tabling can explain.

Wrong. Hud.tbl isn't used anywhere anymore.  All that happened is the game couldn't find the animation.

[karajorma]

Wrong. Hud.tbl isn't used anywhere anymore.  All that happened is the game couldn't find the animation.

I was under the impression that it wasn't required but would be used if found. If you're playing with no mods how does FS2_Open figure out which shield ani to use then?

[Wanderer]

Just with $Shield icon:?

[aldo_14]

The Nightmares haven't been used yet.... at least I don't think so. Noise is using them in ITDOH 5, and I'm using them in my campaign... I think Reciprocity was to introduce them, but it never made it to release.


Some intrepid modeller needs to make some more Nightmare ships. I love these things, like to see more designs than the fighter, bomber, corvette/carrier, and destroyer....

No they don't.

[karajorma]

Just with $Shield icon:?

Ah. In that case it's his ships.tbl that he needs to look at and HUD.tbl (if present) can be deleted.