I am wondering now to get default objects that I destroy on maps in the FMB to remain destroyed when I load the mission. Right now, I destroy several objects and save the mission (.mis file), but when I load the mission to test it in a dogfight sever, the objects have all returned to their un-destroyed state. I found the following threads dealing with the problem, but the map I am trying to do this for lacks an actors.static file in the maps folder.
(The link is inoperative)
(The link is inoperative)
Does anyone know how to resolve this if there is no actors.static file?
Just use the destruction brush, it's their for a reason.
I guess I wasn't clear enough. I want to destroy the objects that come default on a map, not extra ones that I place in the FMB. It's the default objects that keep reverting to being not destroyed when I load the mission. I want them to remain destroyed when I play the mission and the next time I open the mission in the FMB.
I already told you, use the destruction brush!
Posts: 1.222
Threads: 42
Joined: Nov 2007
A little trick I use is to place a plane, bomber, whatever about 100 ft above the area you want blasted (make sure it's loaded with a bomb).
Give it 0 fuel and a forward speed of 0. As soon as the mission starts and the plane spawns, the AI will immediately drop it's bomb to try and stay aloft.
The subsequent explosion will destroy your target plus the plane that dropped it.
You have to experiment with bomb size to get the right blast radius, but it works well for a quick destruction effect.
Though I fly through the valley of death, I will fear no evil.....
For I am the meanest SOB in the valley!
I did some more testing and it appears that the objects all "fix" themselves when I load the mission as a dogfight in the multiplay server. When I run it as a coop or test it using "Play" in the FMB, there are no problems.
It's obvious from the OP's first sentence, that he *was* using the destruction brush, even if he did not explicitly say so. His problem is not how to *create* destruction in the FMB, but that the destruction was not getting *saved* in the mission file.