Strike Tutorial #2, Strike mission not triggering
Posted: Tue Apr 23, 2024 8:07 pm
I googled and found a steam discussion, regarding same issue, the devs asked them to create an issue here, which as per one comment they did, but when i opened those links they were 404
- [ ] in first mission Hi-lo-hi, ship doesn't get low alt as described in scenario instructions
- [ ] in 3rd mission fails to trigger which was supposed to auto trigger when a contact was going to be detected by second mission
after setting up everything waited/checked/rechecked the instructions and my mission setup to no avail.
at this point i started googling and came across this steam discussion https://steamcommunity.com/app/1076160/ ... 677063710/
however after reading others facing same issue and manually triggering the mission, i started to experiment with it.
Took inspiration from one tutorial instruction which said, leave targets blank, i noticed that target section for strike mission already had SA-5 listed, (ironically this was also mentioned in instructions, that's why we set 320nm to prevent it from being target). So in spirit of scenario instructions i removed this target from list, i.e. made target list blank, voila instantly my mission triggers and scenario proceeds as expected. after checking i figured out that target list was updated and target detected by mission-2 was being listed there.
so i think one of these should have happened but didn't happen
1. the target list should have not considered the SA-5 and kept itself empty due to max-strike distance?
2. the mission should have been able to include more then one target and considering the building target was within max strike range and should have triggered itself?
- [ ] in first mission Hi-lo-hi, ship doesn't get low alt as described in scenario instructions
- [ ] in 3rd mission fails to trigger which was supposed to auto trigger when a contact was going to be detected by second mission
after setting up everything waited/checked/rechecked the instructions and my mission setup to no avail.
at this point i started googling and came across this steam discussion https://steamcommunity.com/app/1076160/ ... 677063710/
however after reading others facing same issue and manually triggering the mission, i started to experiment with it.
Took inspiration from one tutorial instruction which said, leave targets blank, i noticed that target section for strike mission already had SA-5 listed, (ironically this was also mentioned in instructions, that's why we set 320nm to prevent it from being target). So in spirit of scenario instructions i removed this target from list, i.e. made target list blank, voila instantly my mission triggers and scenario proceeds as expected. after checking i figured out that target list was updated and target detected by mission-2 was being listed there.
so i think one of these should have happened but didn't happen
1. the target list should have not considered the SA-5 and kept itself empty due to max-strike distance?
2. the mission should have been able to include more then one target and considering the building target was within max strike range and should have triggered itself?