[SypheDMar]

I'm not sure what these mean, but it doesn't seem to stop me from playing. Anyway, is there a way to fix this? I'm using taylor's new xt build.


Warning: Too many beam sections for weapon BFRed - max is 5
File: Weapons.cpp
Line: 3021


Call stack:
------------------------------------------------------------------
    parse_weaponstbl()    parse_modular_table()    weapon_init()    game_init()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------

Warning: GTF Myrmidon (fighter2t-05.pof) has a null moment of inertia!
File: Ship.cpp
Line: 5624


Call stack:
------------------------------------------------------------------
    ship_set()    ship_create()    parse_create_object_sub()    parse_create_object()    mission_parse_maybe_create_parse_object()    post_process_ships_wings()    post_process_mission()    parse_mission()    parse_main()    mission_load()    game_start_mission()    game_enter_state()    gameseq_set_state()    game_process_event()    gameseq_process_events()------------------------------------------------------------------

Warning: GTF Myrmidon (fighter2t-05.pof) has a null moment of inertia!
File: Ship.cpp
Line: 5624


Call stack:
------------------------------------------------------------------
    ship_set()    ship_create()    parse_create_object_sub()    parse_create_object()    parse_wing_create_ships()    post_process_ships_wings()    post_process_mission()    parse_mission()    parse_main()    mission_load()    game_start_mission()    game_enter_state()    gameseq_set_state()    game_process_event()    gameseq_process_events()------------------------------------------------------------------

[FUBAR-BDHR]

Are you running the debug build or the regular one?  If your running debug just switch to regular.  Debug builds normally end in _debug or _d. 

[SypheDMar]

I ran in debug purposely to see if there was anything wrong. I'm guessing this is normal then?

[FUBAR-BDHR]

Well the null moment of inertia ones are common.  Not sure about the BFRed one.

[SypheDMar]

I see... Never mind then. Thanks.

[Wanderer]

Those errors are caused by model and/or table problems in the 3.6.10 beta mediavps... You might sometime see some missing graphics but they should not prevent you from playing the game

And besides... those errors should appear only with debug builds (marked with d). Try playing with 'r' (release) builds.

[taylor]

You can just use the -no_warn cmdline option to disable the warning popups if you still want to use a debug build (as there are various reasons to do so).  The warning messages themselves will still go into your fs2_open.log file though, so you can always go back and check out the warnings later if you are actually interested in them.

[FUBAR-BDHR]

You can just use the -no_warn cmdline option to disable the warning popups if you still want to use a debug build (as there are various reasons to do so).  The warning messages themselves will still go into your fs2_open.log file though, so you can always go back and check out the warnings later if you are actually interested in them.

Thank you for that info.  Will help out a lot in debugging multi.  Those popup warnings are killers.  Will that flag work in 3.6.9 as well? 

[taylor]

Will that flag work in 3.6.9 as well? 

I can't remember when it was actually added, but I think it was for 3.6.9.  However, the warning messages getting added to the log file is a 3.6.10 feature, something that I added to the Xt builds last year and then committed to SVN a few months later.