• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

MB breakthrough...

Rami

Rami

Administrator
Staff member
To all,

I'd like to pass along some recently discovered info about Mission builder. If you are crazy enough to convert missions from CFS1 to CFS2, you will be benefited enormously from this.

Those familiar with the way CFS2 mission builder works knows that if you do not have the correct airbase.dat entries for the mission, you can still look at it, but you can't modify it and / or save it without losing your work in a CFS2 crash, known as a CTD (Crash to desktop) error.

If you attempt to convert CFS1 missions, bear in mind that you need to have these airbase.dat IDs in your in your airbase.dat before even loading the mission, or else the mission will simply show an error message and not load at all. (This is an "unknown error" or "mission formatted improperly" message.)

Once you have corrected that, you can save the mission and it will automatically convert the mission to CFS2, though you'll still need to create a .dyn file and all that fun stuff.

Now, had I known this about a year ago, I wouldn't have had such a difficult time with "Barbarossa." :banghead:
 
Rami said:
Now, had I known this about a year ago, I wouldn't have had such a difficult time with "Barbarossa." :banghead:
Click to expand...

Hi Rami,

Yea..The downside of progress, it usually always seems to include retrospect! :d Thanks for the MB information.

Cheers,
O
 
Good find Rami!

Here's another tip that I've found helpful when converting missions. I use a program called NoteTab Light, available at http://www.notetab.com/downloads.php. It allows me to replace text in multiple mis files all at once. For example, if I had ten CFS1 missions where I wanted to replace the CFS1 P-51 with a CFS2 version I can open all ten missions in NoteTab Light and use the "Replace" function to change every occurance of P51D to ALPHA P-51D with a single keystroke. It's a real time saver and reduces the number of "Do you want to replace with the Zero" messages. I still need to open the mission in MB to tweak it, but this really saves me time.

I didn't post it there, but this would help with the issue raised in the Default CFS2 Airfields thread of replacing airbases. You can use this same technique to replace all of the longitude, latitude, heading, etc. information for any airbase entry in a mis file. So, if you had 50 missions leaving from Henderson and now Henderson is in a different spot, you could open them all in NoteTab Light then replace the airbase coordinates. You can only replace one field at a time, but when you click "Replace All" you'll change that field in all 50 missions at once.

I really like this little program for global changes such as this. It also make a great permanent replacement for Microsoft's Notepad. And here's the best news - NoteTab Light is free!
 
You must log in or register to reply here.
Back
Top