[REL] mySH3-TooL_v1 small SH3 Mod-Helper Tool (this is not a Mod)

[Anvar1061]

Originally Posted by Hebe Vollmaus

[Bump]

Just recently i stumbled on some file-collections which my Tool does not handle correct.

Update to v1.6b as an Bugfix.
Last v1.6a crashes on make Database-files and can produce false results.

Sorry about that.

Greetings.

Errare humanum est

[Hebe Vollmaus]

Originally Posted by Anvar1061

Errare humanum est

Absolut correct.
YMMD!

Greetings.

[Anvar1061]

It is difficult to work with Submarine. Instead of the Objects folder, the program tries to search the Library.

LinkName=data/objects/Turm7b_1_hd;<--ERR: not in [SH3\Library\*.dat]--

[Hebe Vollmaus]

Originally Posted by Anvar1061

It is difficult to work with Submarine. Instead of the Objects folder, the program tries to search the Library.

LinkName=data/objects/Turm7b_1_hd;<--ERR: not in [SH3\Library\*.dat]--

Yes. Thats why the "ReadMe" (*.txt) says:
Works slightly Ok for Air- or Sea-files but
not with Submarines (Objects\Turm* now not detected).

This means the Search in data\Objects is currently not implemented.

I can not garantee it ever will be, since it has ultra low priority.

Greetings.

[Hebe Vollmaus]

[Bump]

Update to v1.7

You may be amused (or angry) what quirks my Tool now can find.
There are added checks like BOM Byte Order Marks, Komma instead of Points on some often found Positions, Sequential Ordering quirks, Dates should always be 8 letters ( not 9 or 7 ), and forgotten entries.

So you may get an overview, here follows an result of [makeDBs] what the Developers of my old DVD-Install have forgotten:

8<------------------------------
--CHECK-- AirLndOrdSeaSub:
"DDHuntII" - "4" (Sea) ==not (or Err) in Roster==
"DDSomers" - "4" (Sea) ==not (or Err) in Roster==
"DEBuckley" - "3" (Sea) ==not (or Err) in Roster==

--CHECK-- Roster:
DB_ROSTER.csv Line 22:
DDSomers.cfg;E:\SilentHunterIII\data\Roster\Americ an\Sea\DDSomers.cfg;==Line:59 "[Unit 11]" Sequential Order==
DB_ROSTER.csv Line 23:
DEBuckley.cfg;E:\SilentHunterIII\data\Roster\Ameri can\Sea\DEBuckley.cfg;==Line:327 "196700801" Date-Lenght==
DB_ROSTER.csv Line 101:
DDHuntII.cfg;E:\SilentHunterIII\data\Roster\Britis h\Sea\DDHuntII.cfg;==Line:154 "[Unit 30]" Sequential Order==
DB_ROSTER.csv Line 128:
CDAAPlatform.cfg;E:\SilentHunterIII\data\Roster\Ca nadian\Land\CDAAPlatform.cfg;==Entry not found== AppearanceDate
DB_ROSTER.csv Line 129:
CDBunkerLarge.cfg;E:\SilentHunterIII\data\Roster\C anadian\Land\CDBunkerLarge.cfg;==Entry not found== AppearanceDate
DB_ROSTER.csv Line 130:
CDBunkerMedium.cfg;E:\SilentHunterIII\data\Roster\ Canadian\Land\CDBunkerMedium.cfg;==Entry not found== AppearanceDate
DB_ROSTER.csv Line 131:
CDBunkerSmall.cfg;E:\SilentHunterIII\data\Roster\C anadian\Land\CDBunkerSmall.cfg;==Entry not found== AppearanceDate
DB_ROSTER.csv Line 132:
CDSearchLight.cfg;E:\SilentHunterIII\data\Roster\C anadian\Land\CDSearchLight.cfg;==Entry not found== AppearanceDate
DB_ROSTER.csv Line 134:
NavalBase.cfg;E:\SilentHunterIII\data\Roster\Canad ian\Land\NavalBase.cfg;==Entry not found== AppearanceDate
DB_ROSTER.csv Line 341:
CDAAPlatform.cfg;E:\SilentHunterIII\data\Roster\So uthAfrica\Land\CDAAPlatform.cfg;==Entry not found== AppearanceDate DisappearanceDate DisplayName
DB_ROSTER.csv Line 342:
CDBunkerLarge.cfg;E:\SilentHunterIII\data\Roster\S outhAfrica\Land\CDBunkerLarge.cfg;==Entry not found== AppearanceDate DisappearanceDate DisplayName
DB_ROSTER.csv Line 343:
CDBunkerMedium.cfg;E:\SilentHunterIII\data\Roster\ SouthAfrica\Land\CDBunkerMedium.cfg;==Entry not found== AppearanceDate DisappearanceDate DisplayName
DB_ROSTER.csv Line 344:
CDBunkerSmall.cfg;E:\SilentHunterIII\data\Roster\S outhAfrica\Land\CDBunkerSmall.cfg;==Entry not found== AppearanceDate DisappearanceDate DisplayName
DB_ROSTER.csv Line 345:
CDSearchLight.cfg;E:\SilentHunterIII\data\Roster\S outhAfrica\Land\CDSearchLight.cfg;==Entry not found== AppearanceDate DisappearanceDate DisplayName
DB_ROSTER.csv Line 346:
NavalBase.cfg;E:\SilentHunterIII\data\Roster\South Africa\Land\NavalBase.cfg;==Entry not found== AppearanceDate DisappearanceDate DisplayName
8<------------------------------

Have Fun!
Greetings.

[Anvar1061]

I did not understand anything of the above.

[Jeff-Groves]

I see some of the issues listed in my Vanilla install.
I'll have to download this and see if I get all the same results.

[Hebe Vollmaus]

Originally Posted by Anvar1061

I did not understand anything of the above.

You are not alone. Sometimes i read here also posts that i cant understand.

But hopefully i can enlighten it a bit. As an first example i use this line:

"CDAAPlatform.cfg;E:\SilentHunterIII\data\Roster\S outhAfrica\Land\CDAAPlatform.cfg;==Entry not found== AppearanceDate DisappearanceDate DisplayName"

This is one line taken out the result from my Tool above, used from my old SH3-DVD-install. Vanilla without any Mods installed. I can not say, if the same will be found on youre Reworked-Rus Mod.

Look in Roster\SouthAfrica\Land Drawer there is CDAAPlatform.cfg located. Look into this file. Maybe you will see that there is no AppearanceDate no DisappearanceDate and no DisplayName.

On my Install it looks so:
8<------

[UnitClass]
ClassName=CDAAPlatform
UnitType=404
FirstAppearanceDate=19380101

[Unit 1]
Name=CDAAPlatform
DOC=19380101
DOD=19480101
8<------

This is not really a big problem to this specific file, since (to my knowledge) this CDAAPlatform (AA Defense) from SouthAfrica ist not used anywhere in the original SH3-Campaign files. But there may be other files that may be anyhow related to the Campaign. So the Tool tries to check all files.
You will see whats wrong with this file, if you open the Missioneditor ME and try to import this AA Defense (from SouthAfrica) into the Campaign_LND.mis. First you may notice the "UnitName" and the "Unit new name" looks ugly. On my sytem it is "8÷ ". (3 digits in hex 38 F7 18) This cant be right. The reason is no DisplayName entry in the file. The ME seems to use some uninitialised Memory to display the Name.
Next try to change the Date in FirstAppearanceDate to something different. Maybe change only the Year from 19380101 to 19390101. You may then reload ME. You may see that there is no difference in the "Entry Date" entry. ME seems to use something default only. The reason is the FirstAppearanceDate has to be in fact to work propperly AppearanceDate.
So my Tool says "==Entry not found== AppearanceDate..." and the other entries which are not there.


As a second example i use this line:

"DDSomers.cfg;E:\SilentHunterIII\data\Roster\Ameri can\Sea\DDSomers.cfg;==Line:59 "[Unit 11]" Sequential Order=="

Go to Roster\American\Sea\DDSomers.cfg Line 59. There you may find a second entry of "[Unit 10]". The Units are not sequential ordered. My Tool says "==Line:59 "[Unit 11]" Sequential Order==".
The effect for the game may be probably only a waste of space, but i do not know for shure what other effect this will have.


"==not (or Err) in AirLndOrdSeaSub (or Roster)=="
can be mean two things. Either this Entry is not in AirLndOrdSeaSub (or Roster) or there is an Quirk in the AirLndOrdSeaSub (or Roster) files found.

The first one (==not in...) can be risky when these also used in the Campaigne.


Hope this helps.
Greetings.