Fixed.
But don't ask me why as I can't explain it. I figured if it's not the script itself then maybe there's a problem with the trigger itself (although I couldn't find any). So I deleted the 3 triggers (LW_Spawn_7C / LW_Spawn_7B / LW_Spawn_7A) using the FMB, saved the mission, restarted the game and proceeded to create them again using the exact same groups, times, etc. I didn't have much to lose after wasting a day banging my head on the table over this problem.
Sure enough. The triggers fired as they had always done with the side effect of the groups
actually spawning and the mission purring along as initially intended. At this point my house was filled with loud, booming vocal expletives #censored# because it made absolutly no sense whatsoever and (repeat) - scratch one day with the kind help of CloDs FMB.
This morning I decided to compare the mission files themselves since I make regular 2 hour incremental backups with storagecraft and therefore always have a copy of any files past gone. There is no deviation between yesterday (mission not working) and todays (mission working) portions of the mis file that pertain to the triggers
except for the listed order.
Code:
Excerpt from triggers and actions group in non working .mis:
[Trigger]
LW_Spawn_7C TTime 15
LW_Spawn_7B TTime 25
LW_Spawn_7A TTime 65
GB_Radio_7B TPassThrough 1 BoB_LW_ErprGr210.22 206231 212690 2000
GB_Radio_7A TPassThrough 1 BoB_LW_ErprGr210.36 178666 197324 2000
LW_Radio_7A TPassThrough 1 BoB_LW_ErprGr210.22 202886 180347 2000
GB_Radio_7D TPassThrough 1 BoB_LW_ErprGr210.02 217559 252014 1900
GB_Radio_7C TPassThrough 1 BoB_LW_ErprGr210.12 246488 235993 2000
ALL_Radio_7A TPassThrough 1 BoB_LW_ErprGr210.12 262178 197723 2000
[Action]
LW_Spawn_7C ASpawnGroup 0 BoB_LW_ErprGr210.12
LW_Spawn_7B ASpawnGroup 0 BoB_LW_ErprGr210.02
LW_Spawn_7A ASpawnGroup 0 BoB_LW_ErprGr210.36
GB_Radio_7C ASpawnGroup 0 Empty
LW_Radio_7A ASpawnGroup 0 Empty
GB_Radio_7A ASpawnGroup 0 Empty
GB_Radio_7B ASpawnGroup 0 Empty
GB_Radio_7D ASpawnGroup 0 Empty
ALL_Radio_7A ASpawnGroup 0 Empty
Excerpt from triggers and actions group in working .mis:
[Trigger]
GB_Radio_7B TPassThrough 1 BoB_LW_ErprGr210.22 206231 212690 2000
GB_Radio_7A TPassThrough 1 BoB_LW_ErprGr210.36 178666 197324 2000
LW_Radio_7A TPassThrough 1 BoB_LW_ErprGr210.22 202886 180347 2000
GB_Radio_7D TPassThrough 1 BoB_LW_ErprGr210.02 217559 252014 1900
GB_Radio_7C TPassThrough 1 BoB_LW_ErprGr210.12 246488 235993 2000
LW_Spawn_7C TTime 15
ALL_Radio_7A TPassThrough 1 BoB_LW_ErprGr210.12 262178 197723 2000
LW_Spawn_7B TTime 25
LW_Spawn_7A TTime 65
[Action]
GB_Radio_7C ASpawnGroup 0 Empty
LW_Radio_7A ASpawnGroup 0 Empty
GB_Radio_7A ASpawnGroup 0 Empty
GB_Radio_7B ASpawnGroup 0 Empty
LW_Spawn_7C ASpawnGroup 1 BoB_LW_ErprGr210.12
GB_Radio_7D ASpawnGroup 0 Empty
ALL_Radio_7A ASpawnGroup 0 Empty
LW_Spawn_7A ASpawnGroup 1 BoB_LW_ErprGr210.36
LW_Spawn_7B ASpawnGroup 1 BoB_LW_ErprGr210.02
There's a lesson of insanity in all this. FMB scripted missions don't function properly using logical (human) load orders. They need anarchy to work properly.
<sideswipe> Probably the reason why the patch is taking so long </sideswipe>
Hats off and cheers to all you masochistic FMB junkies out there
Grom