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

[Mister_M]

Hi ! Is your program able to merge two or more mission files (SCR, LND or RND) ?
There is the option to do that with the Mission Editor, but sometimes there is a bug and all data is deleted from the final mission file...

[propbeanie]

Originally Posted by Hebe Vollmaus

"--CHECK--" should be clear, means you may (or may not) put your attention to following things.

"EQPb" is like 'EQP the 2nd', since "EQP" already exist above. The list shows all Equipment from LinkName= out of all scanned eqp-files not found in all scanned dat-files. Look into DB_Datb.csv, what my tool has been found.
Use a separate Search-tool to find the 1st example "14inchTriple_USNB" in SH3:\data for *.eqp. Then you have the name.eqp. Then, maybe, try check this one thing with single [eqp Check] (grayed for SH4). The ouput should be somewhat similar.

"(try DataSort first!)" exist only if some not sorted files came to the scanner. The files should be also shown in a DB-file enclosed with "==".
Most of the time, i do not scan like the DATA-files are made of. Step by step, or better walk, over Header, id, Node, lenght, data... Especialy the lenght is the problem, since too often the lenght is wrong. So my scanner is based on sorted files like the files in original SH3. All these files are very well structured.
Some external mod-files are not this way created, which _not_ mean they are broken! It means my tool can not find what it serches for, due to unsorted internal file-structur. Normaly it is 3D-object first, then Node, then Name. If the Name is not there, my tool will not find the name.
In S3D this can be seen on the "Index:"-number, which will also be the internal file-position. If you change this number in S3D then this will also change the position where the Node will be positioned in the written file.
So "try DataSort first" means it makes no sense to try search for something else, related to eqp, as long there are files unsorted. When the name is not found, how can i say the eqp is there or not? I cant.

It has nothing to do with Library-file or not. *.dat is *.dat. All *dat-files are scanned. Also sim zon cam val are scanned. But not as a "Full-Scan", the whole complete file, yes, but not tested for all known things. I do not know all and everything what can be exist in DATA-files.

Yes, writing Documentation is a pain. It takes much too much time concadenate the right words together.
The actual ReadMe is already too big. Especialy for the 1st time reader. So i have no plans to make it bigger.

Thank you for the clarification. We are beginning to see the light of the greater understanding afforded by your insight into the files Hebe! lol -

Originally Posted by Mister_M

Hi ! Is your program able to merge two or more mission files (SCR, LND or RND) ?
There is the option to do that with the Mission Editor, but sometimes there is a bug and all data is deleted from the final mission file...

He has Campaign to csv and csv to campaign, with a Campaign renumbering also in there, such that you could take your two files, make certain they are properly numbered from "Group 1" numerically to the end first, using Hebe's tool. Then do the merge in the Mission Editor, and they should properly merge without data loss. Just do not mix RndGroup with Group (ie: RND with SCR files).

[Hebe Vollmaus]

Originally Posted by Mister_M

Hi ! Is your program able to merge two or more mission files (SCR, LND or RND) ?
There is the option to do that with the Mission Editor, but sometimes there is a bug and all data is deleted from the final mission file...

Mister_M, some additions.

My tool will not merge files.
This is a very simple task, so until now i have never think about it.
As you found out, i would also never use the Sh3MissionEditor (ME) for merge.
I use the ME only to visualize something for better understanding what where when, and "Validate Mission".
Instead i use a Notepad-like Tool after created a CSV, and use this csv vor merging.
For this you should know how, as written by propbeanie or here by me:
http://www.subsim.com/radioroom/show...28&postcount=2
These rules (Groups under Groups, Units under Units, AND others...) must be consequent followed.

After merging you should do a [Campaign Renum] and then a [Campaigne Check], wether it is a SingleMission or Campaign file. But Campaign-files should not be mixed. SCR + SCR = OK, RND + SCR = NOP (will not work), as they have different internal structure. For merged LND you should use [mkDB-LonLat0] to find things like double entries, after it is installed as "Campaign_LND.mis".

Keep in mind that my tool can not find Units at the same place in different times. So you may get No Warnings at all for your newly added merges. Only the internal Groups are checked for its unit distances. So you should always look at your result in ME with your own eyes.
Use this "x"-trick to find something in ME very fast, the second last paragraph begin with "BTW".
https://www.subsim.com/radioroom/sho...4&postcount=43

HTH