2018-09-26 11:36 EDT


View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001848FSSCPdockingpublic2012-07-01 04:56
ReporterFUBAR-BDHR 
Assigned ToGoober5000 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionduplicate 
Product Version3.6.9 
Target VersionFixed in Version 
Summary0001848: When ai-goal "undock" is set for the "fighers" game crashes
DescriptionReporting this for Orph3u5. Here's his description of the problem:

I'm currently working on an easy to reproduce solution for TBP Raider Carrier and a B5-cannonic approach to make it launch its fighter - now I appear to have hit an obstacle here which is appearently caused by docking code;
when the ai-goal "undock" is set for the "fighers"1) docked to Silent Hunt (a raider carrier) the debug build gives me this:

[code]Warning: There are multiple dock leaders in the docking group containing the leader Silent Hunt! Setting Silent Hunt as the sole leader...

File:D:\C++\Freespace\fs2_open 3.6.9 - BtRL\code\Mission\MissionParse.cpp
Line: 6328
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    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() game_main() WinMain() WinMainCRTStartup() kernel32.dll 75e34911()
    ntdll.dll 7753e4b6()
------------------------------------------------------------------[/code]

this still gives me options "Yes (debug)", "No (continue)" and "Cancel (exit)" -- when I press "No" to continue comes this:

[code]Assert: num_to_create == 0
File: D:\C++\Freespace\fs2_open 3.6.9 - BtRL\code\Mission\MissionParse.cpp
Line: 4410
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    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() game_main() WinMain() WinMainCRTStartup() kernel32.dll 75e34911()
    ntdll.dll 7753e4b6()
------------------------------------------------------------------[/code]

and it crashes... all the same with 3.6.9/3.6.9 INF/3.6.10

 
TagsNo tags attached.
Attached Files

-Relationships
duplicate of 0000530resolvedGoober5000 Multi-Dock And Wings 
+Relationships

-Notes

~0010422

0rph3u5 (reporter)

I've uploaded all files of the test (mission & tbm) here:


http://proxima-fleet.com/wo/current/Raider_Carrier_Docking.rar

~0010563

Goober5000 (administrator)

Okay, well there's no way I'm going to be able to figure this out without tracing through the debug build. So have the TBP guys remove the debug warnings and I'll give it a shot.

~0010804

FUBAR-BDHR (developer)

I've been playing with this and have had some success. It doesn't work with wings or rotating subsystems but I just got a transport to warp in with fighters docked, jettisoned them, and had them attack.

If I make the fighters into a wing well they just show up at the beginning of the mission docked and make the ship go nuts.


Note I haven't really tried it with the Raider Carrier. I did a couple of weeks ago and it semi-worked except for the dock points not working on rotating subsystems part.

~0013754

Goober5000 (administrator)

This is simply another manifestation of the fact that the game isn't set up to handle docked wings yet.

Marking as duplicate of 0000530.
+Notes

-Issue History
Date Modified Username Field Change
2008-12-16 12:59 FUBAR-BDHR New Issue
2008-12-16 12:59 FUBAR-BDHR Status new => assigned
2008-12-16 12:59 FUBAR-BDHR Assigned To => Goober5000
2008-12-16 17:11 0rph3u5 Note Added: 0010422
2009-01-19 23:32 Goober5000 Note Added: 0010563
2009-04-09 01:15 FUBAR-BDHR Note Added: 0010804
2012-07-01 04:55 Goober5000 Relationship added duplicate of 0000530
2012-07-01 04:56 Goober5000 Note Added: 0013754
2012-07-01 04:56 Goober5000 Status assigned => closed
2012-07-01 04:56 Goober5000 Resolution open => duplicate
+Issue History