CTD when Weapons Free to AI
-
Hi Falcon BMS fans,
:?:
When flying offline Campaign missions (KTO - Tiger Spirit/Veteran) and my wingman (no 2) asks for a ‘Permission to engage’ most of the times (not always) I get a CTD when I give him a ‘Weapons Free’ command.
Thank you for taking notice of this issue.
Falcon BMS 4.34 (U1 + U2) installed. :headb:
-
I have now had two CTDs when doing the same, i.e. hitting “W” and “4” for weapons free. Seems to be a repeatable bug at this point. Log file attached.
Paul
-
I re-flew the mission that kept crashing and I was able to complete it by avoiding all contact with my wingman. I did a quick test, though, and found that hitting “W” and “4” very early in the mission did not result in a CTD. I closed and restarted BMS and then flew and completed the mission as noted just above.
Paul
-
unmodded 4.34 U2 - KTO ?
-
Thanks Paul, and the same procedure you did I did the same. Not sure what May-jp mean with 'umodded 4.34 U2 - KTO. Is it required to modify U2? If so, how and what is needed to modify? Sorry for the nitwit stuff from my side
-
Thanks Paul, and the same procedure you did I did the same. Not sure what May-jp mean with 'umodded 4.34 U2 - KTO. Is it required to modify U2? If so, how and what is needed to modify? Sorry for the nitwit stuff from my side
He mean that you haven’t installed any 3d party mods over U2, and you fly the default Korea campaigns. You don’t need to modify anything after U2 installation, but in case you have any mods, it is harder to find the cause of the crashes.
-
unmodded 4.34 U2 - KTO ?
In my case, yes, up-to-date, unmodded and default Korea campaign. This is not a completely repeatable error, though. After getting through the problem mission as noted above, I saved the campaign file and continued on from there. In the next mission I had no CTDs after contacting my wingman to fence-in, go weapons-free or to give me their status.
Thanks,
Paul -
The source of your CTD cannot be « weapons free » command since the community uses it thousands of times every day
It is related to a IR factor of a Unit which is very weird and could indicate a corrupted mission / campaign file