... and if you have v1.5, and try to open a v1.4 file, you might crash anyway. Same thing if you have mods. If you have TMO2.5 installed and make a mission, it can only be "safely" opened in the TMO2.5 Mission Editor, so that it calls in the correct library files for the ships, planes, land units, etc. If you try to open a TMO2.5 file with the GFO ME, you might very well CTD, or at the least, lock-up the ME. Those are all due to different ship and airplane calls, ie: a DE might change from a Type=4 to a Type=3.
If you have multiple installs of Silent Hunter: Wolves of the Pacific on your machine, using MultiSH, you have to be sure you're using the Mission Editor from the mod that you're building / editing the Mission for. Also remember that the ME will remember sessions you had in other mods, so watch the folder structure you're working in. You can edit RSRDC files in the ME, but you have to have RSRDC activated, and run the ME from that folder - remembering the caveat that Bubblehead1980 alludes to from lurker_hlb3 in his ReadMe files, that you will trash the "timetable" of the RGG, among other things. What happens is that the Mission Editor will "see" certain parameters set to values different than IT wants, and will put those parameters the way it wants them ~AND~ oftentimes will add back in extraneous lines in each Groups "definition" that usually aren't needed. This will change the behavior of the "layer", sometimes drastically. As an example, a file in RSRDC with this "definition":
[RndGroup 1]
GroupName=FakeCruDiv
Category=0
CommandEntry=0
Long=17071670.000000
Lat=3189400.000000
Height=0.000000
DelayMin=0
DelayMinInterv=0
SpawnProbability=100
RandStartRadius=0.000000
ReportPosMin=-1
ReportPosProbability=100
Heading=175.645004
Speed=14.000000
ColumnsNo=2
Spacing=1000
DeleteOnLastWaypoint=true
CurrentInstanceID=0
GameEntryDate=19411204
GameEntryTime=0
GameExitDate=19421011
GameExitTime=0
MaxInst=1
MaxUnitsCreated=7
DockedShip=false
NextWP=0
after editing in the ME becomes:
[RndGroup 1]
GroupName=FakeCruDiv
Category=0
CommandEntry=0
Long=17071670.000000
Lat=3189400.000000
Height=0.000000
DelayMin=60
DelayMinInterv=1440
SpawnProbability=100
RandStartRadius=0.000000
ReportPosMin=-1
ReportPosProbability=100
HighPrioContact=false
Heading=175.645004
Speed=14.000000
ColumnsNo=2
Spacing=1000
DeleteOnLastWaypoint=true
CurrentInstanceID=0
GameEntryDate=19411204
GameEntryTime=0
GameExitDate=19421011
GameExitTime=0
MaxInst=10000
MaxUnitsCreated=1000
DockedShip=false
TacticalGroup=false
AvailStartDate=19411204
AvailEndDate=19421011
ControlZoneRadius=100.000000
NextWP=0
Not all of the "orange" lines above change everytime, such as the
DelayMinInterv= line, but quite often they do, dependent upon circumstances, what you've changed and how you save the file. The
DelayMin= line ~always changes if set to less than "60". Work on copies, and watch the changes after you edit, because you ~will~ have to re-edit in a text editor after using the Mission Editor. This even applies for files that are
NOT RSRDC files. The Mission Editor will put in things that its "logic" says is missing or erroneous. It's just that lurker_hlb3 relied upon especially the
DelayMin= and
DelayMinInterv= working with the
MaxInst= and
MaxUnitsCreated= lines to adhere to his "schedule" of events, and only getting ONE instance of a Group. The other five lines are redundant, unless you specifically need to use them.
The
HighPrioContact= line works with the two lines above, if you're going to have a spawn be reported like "Friendly convoy reported at 167E 24N" sort of thang, and have your game interrupted by the report. The
ControlZoneRadius= line defines how big of an area the RGG might spawn in, adding a bit more randomness to it, but adding to the issues. It is recommended to eliminate this line ALL the time. The
AvailStartDate= and
AvailEndDate= lines are used when you want to spawn a Unit or Group (cannot be an RGG) upon a Trigger / Event sequence in a MIS file. I have not been able to figure out the significance of
TacticalGroup=. It remains a mystery to me - for now... I can certainly crash my computer good with the experiments...
As Bubblehead1980 says, adding traffic to RSRDC is easiest if you use one of Lurker's empty files, or add one of your own, else you have to do some heavy double-clutching with the edits. Just be sure the file is listed in the Campaign.cfg file, else it won't load...
Sorry 'bout the verbosity... The 34th Flotilla (Dietrich) used to have a v17 of the Silent Hunter III Mission Editor Manual, but I can only find links for v6 now. If you have v17, read it...