|
|
|
|
|
Can you attach a screenshot of the error, as well as your fs2_open.log? I'm surprised this causes a problem because FSO should accommodate this already. |
|
|
|
|
|
dockerror.png (60,663 bytes) |
|
|
Additional info, debug throws a repeating warning when the comm menu is brought up. As you can see the standard build throws the error when the support ship has jumped in. |
|
|
You said it throws an error, but the log has only warnings. I don't see a problem with throwing a warning here... EDIT: Apparently reading is hard (I blame tiredness). So the constant warnings prevent you from ever trying to call the support ship in the first place? What if you use shift+R? |
|
|
Debug keeps the support ship from jumping in. This should probably the target behavior (minus the warning message). Standard build allows the support ship to jump in and trigger the error. |
|
|
Ugh... So yes, I remembered correctly and FSO does check for this. The problem is that for optimization purposes, and because mods should disallow this situation, it only performs the check on debug mode. A simple fix would be to perform the check in all circumstances, but this would remove the optimization. More thought is needed. |
|
|
I've committed an accommodation so that release builds won't crash and debug builds will only display the warning once. But this is really a mod error and mod authors should take care that all their player-flyable ships that fly in missions where support is allowed should have support ship dockpoints. |
- Anonymous
