[TEC] Another 1.5 bug with mission editor?

Sniper297 · 05-06-17, 12:14 AM

Trying to edit EastAsiaCampaign.mis and kept getting a CTD with the error message. Tried US_NavalBases.mis and that opened okay. So then I went back to my 1.4 folder, opened the EastAsiaCampaign.mis in the 1.5 folder with no problem.

Looking at the difference between 1.4 and 1.5;

SH4 1.4 Sh4MissionEditor.exe - 556 kilobytes, date 11/20/2007
SH4 1.5 Sh4MissionEditor.exe - 572 kilobytes, date 12/20/2007

Anyone know what the difference is? This is the first time I've tried to use the new editor, can't recall ever getting a CTD with the earlier one.

Bubblehead1980 · 05-06-17, 12:01 PM

Quote:

Originally Posted by Sniper297

Trying to edit EastAsiaCampaign.mis and kept getting a CTD with the error message. Tried US_NavalBases.mis and that opened okay. So then I went back to my 1.4 folder, opened the EastAsiaCampaign.mis in the 1.5 folder with no problem.

Looking at the difference between 1.4 and 1.5;

SH4 1.4 Sh4MissionEditor.exe - 556 kilobytes, date 11/20/2007
SH4 1.5 Sh4MissionEditor.exe - 572 kilobytes, date 12/20/2007

Anyone know what the difference is? This is the first time I've tried to use the new editor, can't recall ever getting a CTD with the earlier one.

Editing RSRD mission layers(assuming RSRD, the east asia campaign sounds liek an RSRD layer) with the ME is asking for trouble. RSRD is very sensitive and it layers with traffic included should only be edited via notepad. Lurker mentions this in the readme.

Edit via notepad and if trying to add traffic, add it via the appropriate blank layers such as a subhunter layer or the troopship layers he did not use.

propbeanie · 05-06-17, 01:52 PM

... 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...

Sniper297 · 05-06-17, 02:57 PM

No, this is all stock 1.5 game, using the mission editor in the stock 1.5 game, and EastAsiaCampaign.mis is one of the defaults dated 2/25/2007 in 1.4 and 1.5, hasn't changed. The earlier mission editor opens it happily, the new 1.5 mission editor crashes every time. And yes, I did double check that I'm using the mission editor from the 1.5 folder and editing the EastAsiaCampaign.mis in the same folder, that was the first thing I checked after the first crash. I can duplicate this every time, that mission opens flawlessly with the 1.4 editor, crashes every time with the 1.5 editor.

Another bug is CTD at random times while playing - I think the common denominator is the FUBUKI class destroyer, although I've changed nothing in that. Tried with and without GFO, I can't duplicate the gripe at will but so far every time it happens there are destroyers hunting me. Half tempted to give up and go back to 1.4, this version seems to have 10 times as many bugs in it. Not much of a patch.

propbeanie · 05-06-17, 08:46 PM

Ahhh, but you paid money for it, therefore - it is an "upgrade"... Sorry, bad joke...

I've got v1.3 (for some strange reason), v1.4 and v1.5 all on my hard drive. I can try tomorrow with mine on that EastAsiaCampaign file. Seems to me, that there's a bad call in that thing, but I don't remember what, whether a ship or plane or objective or what... We found that while updating things in Fall of the Rising Sun Ultimate. I just figured it was from the mod...

Sniper297 · 05-07-17, 03:50 PM

Yeah, the funny thing is my biggest gripe was the SJ radar shutting off when a wave broke over it, and the crew AI not having enough sense to turn it back on after the wave passed. The actually fixed that (hooray!) but in the process added a new bug with the sweep hiccup passing 000 on every cycle. And failed to fix the reversed PPI/Ascope or make the default the PPI when you click the radar button or get rid of the automatic focus when changing to the PPI scope.

Anyway, back to the mission editor, had a few minutes to kill this morning so I started opening some of the 41 missions, then when I got to the 42 missions I got;

ERROR: random group 42b_Jap_TroopConvoys_001 contains an invalid class entry PLConteVerde!!!

(in addition to their 7s with the funny crossbar, Europeans are fond of using exclamation marks by firing them from a scattergun)

Followed by 002, 003, couple dozen repetitions of similar errors!!! and after clicking through all of those it loaded the mission without crashing. After that I tried the problem child, EastAsiaCampaign.mis, and this time it decided to load that one without crashing. I dunno, maybe the new mission editor only works on Sundays or something.

05-06-17, 12:14 AM	#1
Sniper297 The Old Man Join Date: Dec 2005 Location: Philadelphia Shipyard Brig Posts: 1,386 Downloads: 160 Uploads: 19	Another 1.5 bug with mission editor? Trying to edit EastAsiaCampaign.mis and kept getting a CTD with the error message. Tried US_NavalBases.mis and that opened okay. So then I went back to my 1.4 folder, opened the EastAsiaCampaign.mis in the 1.5 folder with no problem. Looking at the difference between 1.4 and 1.5; SH4 1.4 Sh4MissionEditor.exe - 556 kilobytes, date 11/20/2007 SH4 1.5 Sh4MissionEditor.exe - 572 kilobytes, date 12/20/2007 Anyone know what the difference is? This is the first time I've tried to use the new editor, can't recall ever getting a CTD with the earlier one.

05-06-17, 01:52 PM	#3
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 10,098 Downloads: 451 Uploads: 2	... 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... __________________ "...and bollocks to the naysayers" - Jimbuna

05-06-17, 08:46 PM	#5
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 10,098 Downloads: 451 Uploads: 2	Ahhh, but you paid money for it, therefore - it is an "upgrade"... Sorry, bad joke... I've got v1.3 (for some strange reason), v1.4 and v1.5 all on my hard drive. I can try tomorrow with mine on that EastAsiaCampaign file. Seems to me, that there's a bad call in that thing, but I don't remember what, whether a ship or plane or objective or what... We found that while updating things in Fall of the Rising Sun Ultimate. I just figured it was from the mod... __________________ "...and bollocks to the naysayers" - Jimbuna

05-06-17, 02:57 PM	#4
Sniper297 The Old Man Join Date: Dec 2005 Location: Philadelphia Shipyard Brig Posts: 1,386 Downloads: 160 Uploads: 19	No, this is all stock 1.5 game, using the mission editor in the stock 1.5 game, and EastAsiaCampaign.mis is one of the defaults dated 2/25/2007 in 1.4 and 1.5, hasn't changed. The earlier mission editor opens it happily, the new 1.5 mission editor crashes every time. And yes, I did double check that I'm using the mission editor from the 1.5 folder and editing the EastAsiaCampaign.mis in the same folder, that was the first thing I checked after the first crash. I can duplicate this every time, that mission opens flawlessly with the 1.4 editor, crashes every time with the 1.5 editor. Another bug is CTD at random times while playing - I think the common denominator is the FUBUKI class destroyer, although I've changed nothing in that. Tried with and without GFO, I can't duplicate the gripe at will but so far every time it happens there are destroyers hunting me. Half tempted to give up and go back to 1.4, this version seems to have 10 times as many bugs in it. Not much of a patch.

05-07-17, 03:50 PM	#6
Sniper297 The Old Man Join Date: Dec 2005 Location: Philadelphia Shipyard Brig Posts: 1,386 Downloads: 160 Uploads: 19	Yeah, the funny thing is my biggest gripe was the SJ radar shutting off when a wave broke over it, and the crew AI not having enough sense to turn it back on after the wave passed. The actually fixed that (hooray!) but in the process added a new bug with the sweep hiccup passing 000 on every cycle. And failed to fix the reversed PPI/Ascope or make the default the PPI when you click the radar button or get rid of the automatic focus when changing to the PPI scope. Anyway, back to the mission editor, had a few minutes to kill this morning so I started opening some of the 41 missions, then when I got to the 42 missions I got; ERROR: random group 42b_Jap_TroopConvoys_001 contains an invalid class entry PLConteVerde!!! (in addition to their 7s with the funny crossbar, Europeans are fond of using exclamation marks by firing them from a scattergun) Followed by 002, 003, couple dozen repetitions of similar errors!!! and after clicking through all of those it loaded the mission without crashing. After that I tried the problem child, EastAsiaCampaign.mis, and this time it decided to load that one without crashing. I dunno, maybe the new mission editor only works on Sundays or something.