Briefing import?

[Brad_Edmondson]

Just wanted to impress you all with how non-computer savy I really am:

How do I import text from other sources into SB? I've never figured out how to cut from somewhere and past it into SB chat windows or scenario briefings because there's no right-click 'paste' function.

<bows head in shame>

By the way, I made an important discovery about naming files tonight...

Never, ever, ever put a colon in your scenario name. If you do when you try and test the scenario it will crash it and delete the file.

Awfully sporting way to lose a few hours of work so you have to start over :mad2:

[colin]

I just went through this issue of trying to import a briefing. I have done mine up in Word and then save into the SB scenario folder as .txt file. Now for the quirk, For some reason SB does not see the file in the folder, even though your computer swears it is there, what I to work around this is to make a new copy of the .txt file while in the SB folder and resave it. Then SB will allow you to import it. Next time I will save it in Word as an .txt file and then copy it over to see if that works. Hope this helps

[Werewolf]

Create your briefing using a text editor (Word is OK but you have to remember to save it as a .txt file - notepad is better or one of the numerous free text editors available).

Save your text file to the /scenario directory (you must put it there or you want be able to import it). You can name it whatever you want but I use the scenario name just to make it easier to find.

In the mission editor go to the briefing screen for blue or red (the side you want to import a briefing for).

Click file at the menu then select briefing/import

Select your briefing and voila it's in your scenario. :thumbup:

It's as easy as that...

[Brad_Edmondson]

Well, after some digging about I found that CTRL-V will past Word documents into the briefing, although you have to reformat it.

Yay me! :D

Another scenario issue has come up:

What the hell is the 'exclude' function under 'penalty zone?' It just lists the CO and XO and I haven't been able to test a measurable purpose. I tried making an 'expose to enemy' zone that would 'exclude' the CO, but it caused the first condition to fail and the enemy never saw other vehicles moving through the zone.

[GsMcAmis]

Never, ever, ever put a colon in your scenario name. If you do when you try and test the scenario it will crash it and delete the file.

Awfully sporting way to lose a few hours of work so you have to start over :mad2:

I actually made this 'discovery' sometime back. I know I never reported it and honestly have no idea why. I am very sorry for boling this cause I understand completely what it does to scenario maker moral. Also be careful what you name your scenario's in other ways (I have no idea the combinations required to achieve these bolo's exactly. But namign them wrongly can also cause them to become corrupted in a few other ways. For instance it can cause the height map to freak right out of the mission (ok I just showed my computer ineptitude as well being thats te best I can explain it)

Nassty Boloss... we hatess them.


Oh yea... try Werewolf's way of doing it. Its the easiest and most user friendly way.
WW is wise of muzzle as it pertains to these things. ;)

[Werewolf]

Well, after some digging about I found that CTRL-V will past Word documents into the briefing, although you have to reformat it.

Yay me! :D

Another scenario issue has come up:

What the hell is the 'exclude' function under 'penalty zone?' It just lists the CO and XO and I haven't been able to test a measurable purpose. I tried making an 'expose to enemy' zone that would 'exclude' the CO, but it caused the first condition to fail and the enemy never saw other vehicles moving through the zone.

If you select CO exclude then the CO can go in the zone without suffering the zone's penalty. I've never found much use for that but that doesn't mean it doesn't have one.