RUb 1.44 and UZO-CTDs off Hull (Britain).

Stiebler · 10-31-05, 01:49 PM

This thread has come about from a previous investigation into occasional CTDs caused in RUb 1.44 while patrolling in the North Sea, off the east coast of Britain, and whether minefields were involved (see thread 'Minefields and RUb 1.44').

Teddy Bar's new minefields have, I feel confident, solved the problem of regular CTDs in RUB 1.44 caused by the GB minefield#8 problem of the original.

However, there still remains a rare CTD apparently caused by sighting an enemy warship in the North Sea (problem never seen with original SH3 patched with 1.4). I've carried out further trials, crossing files between SH3 and RUB, and I believe that the problem lies with RUb's campaign_scr.mis and/or campaign_rnd.mis files, possibly (unproven) by interaction with local minefields.

I've examined the original SH3 _scr and _rnd files versus the RUb versions in the Mission Editor.

If you "Open (Normal Mission)...", the original SH3 campaign_scr.mis file, then try to save it (unchanged) with "Save (Normal Mission)...", the save fails, you get a warning about errors, and the file "SH3MissionEditor.log" is saved to your file "My Documents\SH3\Data\cfg\". On examination, this file contains a stream of warnings about units being placed too close together, but nothing else. Since the game plays fine, this isn't a serious difficulty.

If you open and save the RUB 1.44 campaign_scr.mis file in the same way, you also get the same error message, but now the log file contains (as well as the "too close" errors) a number of other errors, such as:
ERROR: no player unit found, and
WARNING: unit xyz. No way-points attached.

I reckon this may be the underlying cause of the rare RUb CTD - defective groups or units based in the North Sea area.

Would anyone with more experience than me of these files like to comment?

10-31-05, 01:49 PM	#1
Stiebler Fuel Supplier Join Date: Oct 2005 Location: London, UK Posts: 1,237 Downloads: 29 Uploads: 4	RUb 1.44 and UZO-CTDs off Hull (Britain). This thread has come about from a previous investigation into occasional CTDs caused in RUb 1.44 while patrolling in the North Sea, off the east coast of Britain, and whether minefields were involved (see thread 'Minefields and RUb 1.44'). Teddy Bar's new minefields have, I feel confident, solved the problem of regular CTDs in RUB 1.44 caused by the GB minefield#8 problem of the original. However, there still remains a rare CTD apparently caused by sighting an enemy warship in the North Sea (problem never seen with original SH3 patched with 1.4). I've carried out further trials, crossing files between SH3 and RUB, and I believe that the problem lies with RUb's campaign_scr.mis and/or campaign_rnd.mis files, possibly (unproven) by interaction with local minefields. I've examined the original SH3 _scr and _rnd files versus the RUb versions in the Mission Editor. If you "Open (Normal Mission)...", the original SH3 campaign_scr.mis file, then try to save it (unchanged) with "Save (Normal Mission)...", the save fails, you get a warning about errors, and the file "SH3MissionEditor.log" is saved to your file "My Documents\SH3\Data\cfg\". On examination, this file contains a stream of warnings about units being placed too close together, but nothing else. Since the game plays fine, this isn't a serious difficulty. If you open and save the RUB 1.44 campaign_scr.mis file in the same way, you also get the same error message, but now the log file contains (as well as the "too close" errors) a number of other errors, such as: ERROR: no player unit found, and WARNING: unit xyz. No way-points attached. I reckon this may be the underlying cause of the rare RUb CTD - defective groups or units based in the North Sea area. Would anyone with more experience than me of these files like to comment?