JG7_X-Man Posted November 13, 2020 Posted November 13, 2020 (edited) Question about the events and reports tables. Do they run from top to bottom in sequential order and skip events or reports on the tables that their target id are not available? Example: Target IDs 18, 630 and 1163 are Command: Attack MCUs targeting the different bomber groups (BG) which spawn at random (21890 is Command: Formation). If the BG assigned to Target ID 18 is not active (i.e. did not spawn), will Target ID 630 fire next or will it continuously look for Target ID 18 indefinitely? Note: This is the player's group (flying in the non-lead position). Edited November 13, 2020 by JG7_X-Man
JG7_X-Man Posted November 13, 2020 Author Posted November 13, 2020 Let me explain what I am trying to do: I would like to set a group of fighters (one being "player") to attack any randomly generated group (1 of 4). After the Command: Formation triggers, It seems that only Target ID 18 triggers when generated. When Target ID 630, 1163 or 1751 are randomly generated, the aircraft simply circle the airfield in formation. Any ideas of a work around?
coconut Posted November 13, 2020 Posted November 13, 2020 It should be pretty easy for you to verify your hypothesis in your first port: Add a link to something obvious, like a smoke effect, subtitle, end mission... after a trigger of a command to a inactive unit. As for your second post, there's exactly 1542857 reasons (I've counted them all) why a group of planes may circle aimlessly instead of doing what you think you told them, but without the mission we can't tell you. The potential reason you mentioned in the first post is not one I have noticed, but I haven't checked for it. A suggestion to the devs: Please give us a log of the MCUs that are triggered during a mission execution, I think it would help a lot to understand why things don't work the way we expect them to. 1
JG7_X-Man Posted November 13, 2020 Author Posted November 13, 2020 16 minutes ago, coconut said: ...A suggestion to the devs: Please give us a log of the MCUs that are triggered during a mission execution, I think it would help a lot to understand why things don't work the way we expect them to. Bingo! A log would be an awesome idea! As the logic is sound, I will make a smaller mission to check my logic since the idea isn't far-fetched.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now