Pivot2163 Posted May 18, 2013 Posted May 18, 2013 Dear developers, it seems there needs to be a way to fail the mission if a certain trigger has been missed that is required to continue. I am sure it can be done hence why missions are failed if you stray to far from the flight lead on a couple missions. I have been flying the new UH-1H campaign recently and have hit this issue a couple of times and if not for just giving up as nothing seemed to happen I would have been flying around in limbo forever. Maybe it could be as easy as noting required targets within the briefing. Anyway, this isn't a rant just an observation which definitely occurs in both campaign and user created missions. I hope there can be some resolution involved or this could turn into a first person shooter where you run around blind searching for that illusive hole in the wall (over & over & over).. :smilewink: On another note, this Huey is a dream to fly! :pilotfly: Regards, Pivot i9-10900K * MSI RTX 4070 * Oculus Rift S * Arctis Pro Wireless Headset * Win11 X64 Home * 64 Gb Ram * TM Warthog Combo & Saitek Pro-Rudders
Telomere Posted May 28, 2013 Posted May 28, 2013 This is definitely an issue in some missions. There is already an inbuilt way to implement a fix: the trigger condition "TIME SINCE FLAG". The problem is this must be manually implemented for each flag. I've tried to do this in missions I've created, but it definitely requires extra effort on the part of the mission creator. It also needs to be implemented separately for each trigger flag in the mission. I don't know that there's an easy solution for this. The best approach at the moment is for released missions to be thoroughly play-tested, and (this is the harder part) for players to report "limbo" type issues to mission designers when they find them.
Pivot2163 Posted May 29, 2013 Author Posted May 29, 2013 This is definitely an issue in some missions. There is already an inbuilt way to implement a fix: the trigger condition "TIME SINCE FLAG". The problem is this must be manually implemented for each flag. I've tried to do this in missions I've created, but it definitely requires extra effort on the part of the mission creator. It also needs to be implemented separately for each trigger flag in the mission. I don't know that there's an easy solution for this. The best approach at the moment is for released missions to be thoroughly play-tested, and (this is the harder part) for players to report "limbo" type issues to mission designers when they find them. Telomere, I thank you for the reply since I was beginning to wonder if this only happens to me.. :helpsmilie: Hopefully DCS will come up with some approach to, at least, minimize the lost time spent flying around wondering what, if anything, I did wrong.. :joystick: Regards, Pivot i9-10900K * MSI RTX 4070 * Oculus Rift S * Arctis Pro Wireless Headset * Win11 X64 Home * 64 Gb Ram * TM Warthog Combo & Saitek Pro-Rudders
Recommended Posts