Enemy transport VTOL lands in map and can't be destroyed so can't complete mission #4340
Comments
throndjohnson uploaded file contains saved games from 2nd and 3rd missions in gamma campaign |
throndjohnson commented I will be working on this bug myself, but I'm not sure where to start. Can someone give me a hint? |
klasskill changed _comment0 which not transferred by tractive |
klasskill commented you cant kill transports in campaign |
vexed changed blockedby which not transferred by tractive |
vexed commented Well, the super transports are the ones that can never die in campaign games, since they are script controlled, and you would break the script if those died. I don't recall any changes that would break this on 3.1.3 though. When I get time, I'll check it out. |
vexed changed blocking which not transferred by tractive |
klasskill commented if you use cheat codes this can happen |
vexed changed status from |
vexed changed resolution from `` to |
vexed commented Works fine on this end (that mission), from the saves I had before. |
Dg-vr_ commented Oh, hello, i'd like to say that this bug seems to appear again in the current version (3.1.5) or atleast that what i have noticed, there's any other way to win on this mision aside using cheats? |
alfred007 uploaded file |
alfred007 commented This bug ist (still?) alive in 3.2.1. I add the saved game, where the transport stands in the map. |
resolution_worksforme
type_bug
| by throndjohnsonAt the end of the third mission in the gamma campaign, the enemy transport VTOL is in the far Northwest corner of the map or it lands in an enemy base south of that position. It can't be destroyed even when its hit points are zero, and therefore, the mission never ends. I tested this six times starting from the previous mission. It was working fine in 3.1.2. I believe this vehicle is supposed to be landing off the map somewhere. I will attach the saved games from the previous mission and the one with the UN-killable enemy VTOL.
Issue migrated from trac:4340 at 2022-04-16 11:53:32 -0700
The text was updated successfully, but these errors were encountered: