BMS Stops Working
-
When I try to start a mission. BMS just stops working and goes back to my windows desktop. Like it was never running. I did just add some older 6.32 T.E.'s But I think that this has happened before without those missions. If anyone can help me figure out what to do to rectify this situation I’d really appreciate it.
-
It COULD be a corrupted logbook. Assume you not trying to run those suspect TE`s but testing with campaign, instant action or provided TE
Try creating a new logbookThinking again its probably not that as would not even load to UI without crashing. Try deleting dx9display.dsp
-
When I try to start a mission. BMS just stops working and goes back to my windows desktop. Like it was never running. I did just add some older 6.32 T.E.'s But I think that this has happened before without those missions. If anyone can help me figure out what to do to rectify this situation I’d really appreciate it.
Tactical Engagements made with 4.32 are not directly compatible with 4.33.5. You need to open them in Mission Commander (available on the forum) and convert them. [Ref: BMS-Manual.pdf pp. 17]
-
Has there been any training missions from 4.32 converted over to 4.33?
I can not find them by searchin “training misions” and suchOk edit,
I found them
https://www.benchmarksims.org/forum/showthread.php?29819-4-32-Ported-TEs-with-weather&p=415976&viewfull=1#post415976 -
Have you tried them? I can’t seem to get the scripts to work properly. Or maybe I’m just doing something wrong. For example with the Ramp Start, shift k does not advance the training script.
-
That’s right, also “shift + k” does not delete entries:target:
-
Have you tried them? I can’t seem to get the scripts to work properly. Or maybe I’m just doing something wrong. For example with the Ramp Start, shift k does not advance the training script.
they are pointless to use. even converted they won’t work
Use the 4.33, wait for the 4.34 or create your own -
Just yes, or install 4.32 and after the problem:drink: I just have it 4.32:yo:
-
Once I had this kind of silent crash because I messed up some textures. Restored the original files and resolved.
-
Yeah I reverted back to the original 4.33 files. Looking forward to 4.34.