View Issue Details

IDProjectCategoryView StatusLast Update
0001762FSSCPdockingpublic2008-09-20 17:51
ReporterTrashMan Assigned ToGoober5000  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version3.6.9 
Summary0001762: ships refuse to undock no matter how the order is given
DescriptionShips, once docked, don't undock. Doesn't matter if the order is given with a ai-goal SEXP or if it's in the inital orders.

the test mission contains a transport that docks with an Arcadia, undocks later and jumps.
The transport undocked from the Arcadia and started to rise, but about a second later, the Arcadia snapped into the dock position and the transport jumped out with the station, causing the game to crash.
Either that, or it never undocks, not even for a second.
TagsNo tags attached.

Activities

TrashMan

2008-09-20 11:52

reporter   ~0009698

Last edited: 2008-09-20 11:53

I think I just figured what went wrong.

Apparently, the warp-out order overrides the undock order. The transports start to warp out before he finished the undocking procedure. I have set it up that 5 seconds after event X (which is the undock order trigger) the transport gets the depart order. After 5 seconds he still wasn't finished undocking, so the warp out order took effect (it had a bigger priority).

A silly error, once that can be avoided by better scripting.
Consider this issue resolved.

Goober5000

2008-09-20 17:51

administrator   ~0009700

Ok. Closing then.

Issue History

Date Modified Username Field Change
2008-09-13 19:34 TrashMan New Issue
2008-09-13 19:34 TrashMan Status new => assigned
2008-09-13 19:34 TrashMan Assigned To => Goober5000
2008-09-20 11:52 TrashMan Note Added: 0009698
2008-09-20 11:53 TrashMan Note Edited: 0009698
2008-09-20 17:51 Goober5000 Note Added: 0009700
2008-09-20 17:51 Goober5000 Status assigned => closed
2008-09-20 17:51 Goober5000 Resolution open => no change required