SUBSIM Radio Room Forums - View Single Post - [REL] mySH3-TooL_v1 small SH3 Mod-Helper Tool (this is not a Mod)

Hebe Vollmaus · 04-10-22, 05:40 AM

[Bump]

Proud to present Update to v2.0

This version introduce some more headaches.
You may study the ReadMe again. Please have a look onto the changelog.
If you have the old v1.9 version of the "ReadMe" you can use WinMerge to see some of the differences very fast.

And once more, the mass of things that can be found now does not mean each and every quirk is found.
Over all, whats left, is a complete Binary part.
I'm always faszinated, by this great amount of quirks, the game runs almost smooth. So the original Devellopers had made a very good job. In most cases, so my impression, when Users ask for a "fix" LOL, the origin reason is based on Modders work.

This version has the Campaign-Check splitted into a "Danger only" and a "Full blown" part. The 'Danger only' will find the typical 'Crash'-things only, in-game Campaign-related and MissionEditor.

Also mentioning a new Check-Button dedicated and around to interrelated en|de_menu.txt, Flotilla.cfg and Campaign_LND.mis. Also here - not all what should be checked are really integrated. I make a break and decided to release it now, instead of never, in the hope it will be useful.

-----
-----
The "Must have" of WinMerge is no longer true. Now you may use your favorite Compare-Tool instead, if you like. But the use of WinMerge is highly recommended!

To stress yourself you can use the HEX-Editor "HxD" for the CMP= entry Compare, or a Tool like "WinDiff" out of the MS Platform SDK, or "Notepad++" with Compare plugin, or something like that.

If you prefer a bit more challenge and absolut unwilling to use an additional external Compare-Tool you can even use the "FC" Command out of the Operating-System. This has to be embedded into a Batchfile like this:

Code:

@echo off
set FCout="%~dpnx1_FC.txt"
echo.
cmd.exe /C FC /L /N "%1" "%2" >%FCout%
echo.
IF %ERRORLEVEL% EQU 0 (
  echo No differences found.
) ELSE (
  echo files are different.
  Start "" /WAIT Notepad.exe %FCout%
)
del %FCout%

echo READY.
echo.
set FCout=
pause

The Config-file entry should then look like this:
CMP=C:\Batch\mySH3TooL_TEST_Run-CMD-FC.bat

LOL

I'm sure you will comeback to WinMerge asap.
Using WinMerge is a Feature, not a Mistake.

-----
-----
In the past there was a feature-request to include a check for SNS- and EQP-dates the same way as it is released in "SHValidator" for DefSide.cfg. The next StartDate should be one day later as the last EndDate.

Some of the points against including it:

Thread SUBSIM Kendras "[TEC] My discoveries about wrong appearance dates":
https://www.subsim.com/radioroom//sh....php?p=2470026

The EQP-files in blanc SH3 have a big amount of these quirks. For example in 5 of 8 Submarines and 31 of 49 Sea-units have these quirks.
To me it looks like the pedantic change of these dates have no real impact in-game due to the games great amount of randomization of these dates.
I have only included a check when next StartDate lives befor the last EndDate, since Modders has written those dates too often to my gusto, original GameMakers only once.
For SNS-files the sittuation is not better. If there is a need for more dates for one node i have not found any single sns-file in unmodified SH3 which is 'correct' in that sense.

There is a nice description in the SH3_MISSION_EDITOR_EN.pdf page 15:
"One word on the unit versions – supply during wartime can never be 100% counted
on. Sometimes, units that are supposed to receive a certain loadout may end up with an
older one."

This clearly shows that this is a Feature of the game, not a Bug. It may be a waste of time to go further in this direction. Before do so i need to look into the Source-codes, to know whats really going on internally.

-----
-----
BTW, two hints for find some things a little bit faster related to the [csv Campaign Check]:

You may ask how to find a --CHECK--entry among of thousends of entries in the original Campaign file using Sh3Missioneditor (ME).
Its easy, but needs a temporary file to work with (for Security-reason).
For example you try to find "[Unit 1708];Name=BR Armed Trawler#67;Class=PCTrawler" in the original v1.4 Campaign_SCR.mis. Open this file with Notepad and change Name= to "xBR Armed Trawler#67". Little x just before its Name. So the result will be "Name=xBR Armed Trawler#67". Then save this file with a New Name(!), for example as Campaign_SCR--TEMP.mis and open this newly created file in ME. In the right pane TreeView-Window move the Cursor to "Units" and press "x" on the Keybord. The Cursor jumps magicaly to the interested item. After you know what you are look for, delete this TEMP-file.
If the Search is a Group, then use the "GroupName=x" and not the Units Name for this x-Name change.

You may ask how to find only one sort of --CHECK--entries in the Mass-amount of different --CHECK--entries to compare only these entries with WinMerge.
Also easy, and needs also some TEMP-files.
You can use the Operating-systems Commandline Tool "FIND" for this task. Only reverse its output to not show the uninterested things with the Operator "/V". Do this as long as the interested entries remain.
For example:
find /V "--CHECK-- SpeedWP" Drive:\Path\Campaign_RND--mis2--Check.csv >Drive:\Path\Campaign_RND--mis2--Check1.csv
will get out all SpeedWP entries.

-----
-----
If you have more then one SH3-installation and/or more then one "mySH3-TooL" running, strange things may happen. For example the [csv Campaigne Check] puts out some Quirks you cannot find a reason why. The lastly created DB-files may be for the Other one, and not for the currently used. Therefor i have integrated another Requester to ask if you be sure you have actual upto-date DB-files created with [MakeDBs].

-----
-----
Greetings.
Have fun!

--
487 Mods found (94 activated)

04-10-22, 05:40 AM	#43
Hebe Vollmaus Officer Join Date: Jun 2010 Location: Germany Posts: 246 Downloads: 3 Uploads: 1	v2.0 [Bump] Proud to present Update to v2.0 This version introduce some more headaches. You may study the ReadMe again. Please have a look onto the changelog. If you have the old v1.9 version of the "ReadMe" you can use WinMerge to see some of the differences very fast. And once more, the mass of things that can be found now does not mean each and every quirk is found. Over all, whats left, is a complete Binary part. I'm always faszinated, by this great amount of quirks, the game runs almost smooth. So the original Devellopers had made a very good job. In most cases, so my impression, when Users ask for a "fix" LOL, the origin reason is based on Modders work. This version has the Campaign-Check splitted into a "Danger only" and a "Full blown" part. The 'Danger only' will find the typical 'Crash'-things only, in-game Campaign-related and MissionEditor. Also mentioning a new Check-Button dedicated and around to interrelated en\|de_menu.txt, Flotilla.cfg and Campaign_LND.mis. Also here - not all what should be checked are really integrated. I make a break and decided to release it now, instead of never, in the hope it will be useful. ----- ----- The "Must have" of WinMerge is no longer true. Now you may use your favorite Compare-Tool instead, if you like. But the use of WinMerge is highly recommended! To stress yourself you can use the HEX-Editor "HxD" for the CMP= entry Compare, or a Tool like "WinDiff" out of the MS Platform SDK, or "Notepad++" with Compare plugin, or something like that. If you prefer a bit more challenge and absolut unwilling to use an additional external Compare-Tool you can even use the "FC" Command out of the Operating-System. This has to be embedded into a Batchfile like this: Code: @echo off set FCout="%~dpnx1_FC.txt" echo. cmd.exe /C FC /L /N "%1" "%2" >%FCout% echo. IF %ERRORLEVEL% EQU 0 ( echo No differences found. ) ELSE ( echo files are different. Start "" /WAIT Notepad.exe %FCout% ) del %FCout% echo READY. echo. set FCout= pause The Config-file entry should then look like this: CMP=C:\Batch\mySH3TooL_TEST_Run-CMD-FC.bat LOL I'm sure you will comeback to WinMerge asap. Using WinMerge is a Feature, not a Mistake. ----- ----- In the past there was a feature-request to include a check for SNS- and EQP-dates the same way as it is released in "SHValidator" for DefSide.cfg. The next StartDate should be one day later as the last EndDate. Some of the points against including it: Thread SUBSIM Kendras "[TEC] My discoveries about wrong appearance dates": https://www.subsim.com/radioroom//sh....php?p=2470026 The EQP-files in blanc SH3 have a big amount of these quirks. For example in 5 of 8 Submarines and 31 of 49 Sea-units have these quirks. To me it looks like the pedantic change of these dates have no real impact in-game due to the games great amount of randomization of these dates. I have only included a check when next StartDate lives befor the last EndDate, since Modders has written those dates too often to my gusto, original GameMakers only once. For SNS-files the sittuation is not better. If there is a need for more dates for one node i have not found any single sns-file in unmodified SH3 which is 'correct' in that sense. There is a nice description in the SH3_MISSION_EDITOR_EN.pdf page 15: "One word on the unit versions – supply during wartime can never be 100% counted on. Sometimes, units that are supposed to receive a certain loadout may end up with an older one." This clearly shows that this is a Feature of the game, not a Bug. It may be a waste of time to go further in this direction. Before do so i need to look into the Source-codes, to know whats really going on internally. ----- ----- BTW, two hints for find some things a little bit faster related to the [csv Campaign Check]: You may ask how to find a --CHECK--entry among of thousends of entries in the original Campaign file using Sh3Missioneditor (ME). Its easy, but needs a temporary file to work with (for Security-reason). For example you try to find "[Unit 1708];Name=BR Armed Trawler#67;Class=PCTrawler" in the original v1.4 Campaign_SCR.mis. Open this file with Notepad and change Name= to "xBR Armed Trawler#67". Little x just before its Name. So the result will be "Name=xBR Armed Trawler#67". Then save this file with a New Name(!), for example as Campaign_SCR--TEMP.mis and open this newly created file in ME. In the right pane TreeView-Window move the Cursor to "Units" and press "x" on the Keybord. The Cursor jumps magicaly to the interested item. After you know what you are look for, delete this TEMP-file. If the Search is a Group, then use the "GroupName=x" and not the Units Name for this x-Name change. You may ask how to find only one sort of --CHECK--entries in the Mass-amount of different --CHECK--entries to compare only these entries with WinMerge. Also easy, and needs also some TEMP-files. You can use the Operating-systems Commandline Tool "FIND" for this task. Only reverse its output to not show the uninterested things with the Operator "/V". Do this as long as the interested entries remain. For example: find /V "--CHECK-- SpeedWP" Drive:\Path\Campaign_RND--mis2--Check.csv >Drive:\Path\Campaign_RND--mis2--Check1.csv will get out all SpeedWP entries. ----- ----- If you have more then one SH3-installation and/or more then one "mySH3-TooL" running, strange things may happen. For example the [csv Campaigne Check] puts out some Quirks you cannot find a reason why. The lastly created DB-files may be for the Other one, and not for the currently used. Therefor i have integrated another Requester to ask if you be sure you have actual upto-date DB-files created with [MakeDBs]. ----- ----- Greetings. Have fun! -- 487 Mods found (94 activated)