I just started taking a look around with FRED1 and to learn a couple of tricks I unpacked the original missions of The Great War to see how scripting works in missions.
Excellent! We have a bona fide tinkerer on our hands. I predict that this mindset will make you an excellent FREDder.


Unfortunately I have a problem with nameplated Orions, every time I try to open a mission with the Galatea or Bastion FRED tells me that it encountered an unknown data ship/weapons and the problem is probably due to a mission data disk I do not have. Obviously it's pretty easy to add another common Orion ship, but honestly I would like to know where the problem actually is.
This is a well-known problem. (At least, it was well-known in the early days of FRED, but since karajorma is focused pretty exclusively on FSO I'll forgive him for the lapse.

)
The problem is the # character. Volition put # in the middle of ship class names so that multiple ship classes could display the same thing on the HUD. (This was before the $Alt Name feature in FS2.) This is so that "GTD Orion", "GTD Orion#1 (Galatea)", and "GTD Orion#2 (Bastion)" all appear as "GTD Orion" on the HUD -- note that the # and everything following it is chopped off.
Unfortunately, a bug in FRED (which is also present in FRED2 as well) prevented the chopped-off names from working. As a result, any mission with these ship classes will not load properly. The solution is to load the mission in Notepad (or Wordpad) and change "GTD Orion#1 (Galatea)" to "GTD Orion". Then the mission will load correctly, but it will display the common GTD Orion. If you want to build a mission using the Galatea or the Bastion, create the mission with a common GTD Orion, and then when you're finished, change the ship class using Notepad.
Seriously though now that we have the port I have no idea why anyone would use FRED1 in preference to FRED2.
Maybe he wants to make a campaign that runs on FS1.
