[REL] Dark Waters

[subdizzle]

Hey i just installed Sh4 again with the Ops Monsun 'Dark waters" updated mod to try out some more u-boating in 2021 but have an issue: Whats the best way in current year to force anti aliasing and other graphics in SH4? I have an Nvidia graphics card and the program "Geforce Experience" but it doesnt detect silent hunter 4 at all in order to edit its graphics settings. Thanks.

edit: And while we're at it, how do i bring up the stadmeter again in the UZO and periscope? For estimating range? Thanks Its been a while.

[Mad Mardigan]

Originally Posted by subdizzle

Hey i just installed Sh4 again with the Ops Monsun 'Dark waters" updated mod to try out some more u-boating in 2021 but have an issue: Whats the best way in current year to force anti aliasing and other graphics in SH4? I have an Nvidia graphics card and the program "Geforce Experience" but it doesnt detect silent hunter 4 at all in order to edit its graphics settings. Thanks.

edit: And while we're at it, how do i bring up the stadmeter again in the UZO and periscope? For estimating range? Thanks Its been a while.

See post below:

https://www.subsim.com/radioroom/sho...84&postcount=2

[DeathOrGlory]

Originally Posted by CapitainEA

Nice video, but is it really maximal difficulty when you're pausing the game to get range and AOB?

[KaleunMarco]

playing DW for the first time since it was released, formally, and i have noticed some strange behaviour by Allied aircraft.
the time line is Late 1943-Early 1944.
Missions are either Midlant or Iceland.
when we encounter a Coastal Command patrol aircraft, one of two things happens as the a/c nears our position:

1. the a/c presses home an attack
2. disappears

the Liberators and Sutherlands attack. The Marlets and Avengers disappear.
i am trying to figure out why there is disparate behaviour.

any hints as to what to look for?

Generic Mod Enabler - v2.6.0.157
[C:\Ubisoft\Dark Waters\MODS]

100 OM_DarkWaters_V6
110 OM_Harder_Escort_L2
120 OM_Strategic_Map_Symbols
130 OM_UMark
140 OM_Warm_Clothes
150 OM_U-Jagd
160 OM_Med_Env
180 OM_Voice Mod

[propbeanie]

As odd as it may sound, try removing the Warm Clothes mod. We found that any little bit of submarine crew configuration that is "off" will result in the crew not being able to see, and airplanes doing odd things, such as flying directly overhead and not bombing. It most likely is not that, but try it. My guess would be load-out conflicts. I'll run Hebe's mySH3-Tool on my install and see if it finds anything like that.

Edit: Loadouts can be a bear to deal with, and DW has its fair share of mis-configurations, probably left-overs from OM. But neither the Martlet nor the Avenger show on the list. However, the Hurricane has several mis-matches...

[KaleunMarco]

Originally Posted by propbeanie

As odd as it may sound, try removing the Warm Clothes mod. We found that any little bit of submarine crew configuration that is "off" will result in the crew not being able to see, and airplanes doing odd things, such as flying directly overhead and not bombing. It most likely is not that, but try it. My guess would be load-out conflicts. I'll run Hebe's mySH3-Tool on my install and see if it finds anything like that.

Edit: Loadouts can be a bear to deal with, and DW has its fair share of mis-configurations, probably left-overs from OM. But neither the Martlet nor the Avenger show on the list. However, the Hurricane has several mis-matches...

under the heading of: be careful what you ask for.....
there are a ****pot-full of bad dates (and a bunch of other gobbly-gook), however it DID find some things on the Martlet and Avenger

what do these lines from DB_Roster.csv mean? if i make a SWAG, i'd say that there is a file somewhere that is referencing the incorrect .CFG file for these planes, but that is just a SWAG. where in this report does it disclose the file with the bad pointers? or am i supposed to know that because i am running SH3-tool?

FBMartlet.cfg;C:\Ubisoft\Dark Waters\data\Roster\British\Air\FBMartlet.cfg;FBMartlet;British;300;Air;19370101;19480101
the file is actually named AFB_Martlet.cfg.

ASWAvenger.cfg;C:\Ubisoft\Dark Waters\data\Roster\American\Air\ASWAvenger.cfg;ASW_Avenger;American;302;Air;19420201;19480101
the file is actually named AFB_Avenger.cfg.
TBAvenger.cfg;C:\Ubisoft\Dark Waters\data\Roster\American\Air\TBAvenger.cfg;ATB_Avenger;American;302;Air;19420201;19480101
the file is actually named ATB_Avenger.cfg.

[KaleunMarco]

Originally Posted by propbeanie

As odd as it may sound, try removing the Warm Clothes mod. We found that any little bit of submarine crew configuration that is "off" will result in the crew not being able to see, and airplanes doing odd things, such as flying directly overhead and not bombing. It most likely is not that, but try it. My guess would be load-out conflicts. I'll run Hebe's mySH3-Tool on my install and see if it finds anything like that.

Edit: Loadouts can be a bear to deal with, and DW has its fair share of mis-configurations, probably left-overs from OM. But neither the Martlet nor the Avenger show on the list. However, the Hurricane has several mis-matches...

next question:


on the left is the EQP file and the right is the CFG file.
the error message: AFB_HurricaneMk1C (Air) ==Loadout "1x250Kg Bomb " not found in cfg

the error does not match what is stored in the files. what am i not understanding?

and....

follow-up question:

where are the ordnance files stored(1x250Kg Bomb)? they are NOT in the Ordnance folder.
edit: found it....\library\Bombs.dat

[propbeanie]

A spelling error, mis-placed semi-colon, any one of a number of typo errors can upset things in those files. You also have to have the "B" nodes, or "R" nodes, or whatever equipment you are attempting to mount, has to have that mount point on the platform itself. For the Loadouts themselves, you "Name" and outline a load-out in the cfg file, and you define it in the eqp file. Kind of like programming and sub-routine procedures. btw - The "DummyBomb" in your example is there as a "fake" so that the plane will come down and at least strafe you. So the cfg file names the load-outs, but each plane's eqp file should start with a "default" load-out, so make certain that set of nodes is at the top of the file. Most of the eqp files we've dealt with will call it "Basic", such as:

; Basic Loadout definition
[Equipment 1]
NodeName=B01
LinkName=Bomb250Kg
StartDate=19380101
EndDate=19431101

Five lines for each entry when including the dates. Notice the Start and End Date lines generally only have to be there for at least the first item of a loadout definition, and that everything about the plane is listed in ALL of the loadouts that are outlined (cfg) and defined (eqp). If there are five "B" nodes on a given plane that you wish to use in a load-out, the empty slots need a NULL listing in the other definitions. When you get to building the "named" loadouts, then you add another line to the equipment listing:

;3x250Kg Bomb Loadout definition
[Equipment 10]
NodeName=B01
LinkName=Bomb250Kg
Loadout=3x250Kg Bomb
StartDate=19431102
EndDate=19451231

There would now be six lines for each entry (including dates), adding the "Loadout=" line. Also, be certain that the headers are listed in proper numerical order. Blank lines are not necessary, and the ";3x250Kg Bomb Loadout definition" line isn't necessary either. Those are there for the human. The game uses the "Loadout=" lines for that. It is good practice (possibly necessary for the game) to keep all Load-outs with the same sequence of "[Equipment XX]" sections, and as mentioned, if not used in a given load-out, use "NULL". Also, don't overlap dates if the loadouts are for spawned assets... This particular plane above is set to "automatically" change its loadout by date. All items in a given loadout definition need to have the same dates, if listed. You can have overlapping dates if the mission builder chooses the loadouts when placing the asset in a mis file and chooses a particular loadout, such as one plane for ASW, another for divebombing, etc...

However, again, you are illustrating the Hurricane, but describing the Martlet and Avenger as avoiding you. Of course, each of those generally only has one bomb slot, so if they used it elsewhere, they won't tangle with you - unless they have a "loaded" "DummyBomb" still on a "B" node... Thanks to Hebe and Jeff-Groves for helping us to further understand loadouts - IF I did this correctly, that is...

[KaleunMarco]

Originally Posted by propbeanie

;3x250Kg Bomb Loadout definition
[Equipment 10]
NodeName=B01
LinkName=Bomb250Kg
Loadout=3x250Kg Bomb
StartDate=19431102
EndDate=19451231

There would now be six lines for each entry (including dates), adding the "Loadout=" line. Also, be certain that the headers are listed in proper numerical order. Blank lines are not necessary, and the ";3x250Kg Bomb Loadout definition" line isn't necessary either. Those are there for the human. The game uses the "Loadout=" lines for that. It is good practice (possibly necessary for the game) to keep all Load-outs with the same sequence of "[Equipment XX]" sections, and as mentioned, if not used in a given load-out, use "NULL". Also, don't overlap dates if the loadouts are for spawned assets... This particular plane above is set to "automatically" change its loadout by date. All items in a given loadout definition need to have the same dates, if listed. You can have overlapping dates if the mission builder chooses the loadouts when placing the asset in a mis file and chooses a particular loadout, such as one plane for ASW, another for divebombing, etc...

ok, in the example above and using your explanation as the basis, the line
Loadout=3x250Kg Bomb
is incorrect, and should be
Loadout=3xBomb250Kg
because that is the definition name in the Bombs.dat file.

did i read/learn correctly?

However, again, you are illustrating the Hurricane, but describing the Martlet and Avenger as avoiding you.

yes, the Hurri was a nice simple example.
AFB_HurricaneMk1C - "FBHurricaneMk1C" - "300" (Air) ==Loadout not exist in cfg (diff cfg<>eqp)==
when i inspected the Bombs file, it was obvious that the ordnance names were not the same.

in the case of the Martlet and Avenger, they did not appear in the DB_Diffs file, they appeared in the DB_roster.csv file.
that would lead me to believe that the name in the Names.cfg file did not match the actual file name in the Roster\Air\British folder (American for the Avenger).

ASWAvenger.cfg;C:\Ubisoft\Dark Waters\data\Roster\American\Air\ASWAvenger.cfg;ASW _Avenger;American;302;Air;19420201;19480101
TBAvenger.cfg;C:\Ubisoft\Dark Waters\data\Roster\American\Air\TBAvenger.cfg;ATB_ Avenger;American;302;Air;19420201;19480101
FBMartlet.cfg;C:\Ubisoft\Dark Waters\data\Roster\British\Air\FBMartlet.cfg;FBMar tlet;British;300;Air;19370101;19480101

when i checked the Roster folder(s), i discovered that the Avenger config file is named the same: ASWAvenger.cfg
However, when i checked the AIR folder (data\air\plane name) i discovered that the Avenger folder is named ASW_Avenger and the config file within the folder is named ASW_Avenger.cfg.

so.....to resolve this, i suspect that i need to change the Names.cfg file, under Avenger to match the AIR Folder name of ASW_Avenger.

does that seem correct?

edit: my suggested fixes did not fix the problems.

[KaleunMarco]

Originally Posted by propbeanie

A spelling error, mis-placed semi-colon, any one of a number of typo errors can upset things in those files.

it was discovered (although you and others may have known) that in the various CFG files in the Roster and Sea folders, SH4 does NOT like comments on the same line as the data.
for example.

DOD=19420931 ;comments

the above will give an error condition of some type because the user must enter spaces or a tab between the data and the comment and SH4 will consider the spaces part of the date, which they are not. hence an error, somewhere.

if you need to leave a comment (or you are cleaning up after the person who left the comment), this alternative is acceptable:

DOD=19420931
;comments

[propbeanie]

You usually have to run Hebe's tool multiple times to clear issues. You might fix what his tool found, but there is another lurking behind that one. But yes, the internal names have to match throughout. Take just a stock asset though, and copy its naming conventions, other than, do NOT use Conte Verde or the Porpoise, and some merchant that I can see, but cannot remember... but if you use the Kate for an airplane example, it has errors in the loadouts - in the Stock game... even the devs had issues with load-outs...

But anyway, the Kate is "ADB_B5N2_Kate" folder name. "ADB_B5N2_Kate.cfg" in that folder (think of a single mission file, that has the file matching the folder name). Inside that config is "ClassName=B5N2Kate * 3DModelFileName=data/Air/ADB_B5N2_Kate/ADB_B5N2_Kate * UnitType=303". Now, in the Roster Air folder for Japan is "TB_B5N2_Kate.cfg" and in it is "ClassName=B5N2Kate * UnitType=303" So they name it "DB" for "DiveBomber" in the Air folder, yet number it 303 for "Torpedo Bomber", and name it that in the Roster folder... sigh - but it does work like that.

in the Air cfg file is

[Loadout 1]
Name=3x500Kg Bombs
Type=3

[Loadout 2]
Name=4x250Kg Bombs ** no matching entry in the eqp file
Type=2

[Loadout 3]
Name=Torpedo
Type=4

and the eqp file has

;Basic Loadout values

All OK, seemingly

;3x500Kg Bombs loadout definition

All OK, seemingly

;5x250Kg loadout definition

All OK, seemingly, other than no matching cfg listing...

;Torpedo

Seemingly OK also

... and then list all of the "pilots" at the end, outside the other "loadout" definitions... not confusing. But notice that the cfg file names do not match, but the ClassName and Type must, of course... Probably what happened with this plane, is Bob was working on the plane, while Pete was working on the configuration for the Roster and Air folders, based on Bob's plane. Bob quits, and Steve takes over. He looks at the plane and goes "it be nice to have another bomb mount on this" and adds a B5 node, changing the Air folder, yet neglects to tell Pete for changes to the Roster. whatever - it actually only has four mounts, so it might just be someone got their finger in the wrong hole when typing a number four, and got "5" instead...

[KaleunMarco]

Originally Posted by propbeanie

You usually have to run Hebe's tool multiple times to clear issues. You might fix what his tool found, but there is another lurking behind that one. But yes, the internal names have to match throughout. Take just a stock asset though, and copy its naming conventions, other than, do NOT use Conte Verde or the Porpoise, and some merchant that I can see, but cannot remember... but if you use the Kate for an airplane example, it has errors in the loadouts - in the Stock game... even the devs had issues with load-outs...

i am cleaning up the "bad dates" (no Raiders jokes, please! asps, very dangerous....)but the rest of these errors have me all sixes and sevens.

==Entry not found== AppearanceDate
Line:34 "[Unit 6]" Sequential Order==
=="Eqp:9=41" Double Node entry==

...just to name a few.

the more i know, the less i understand.

if the My-SH3-Tool developers are still around, please do not mistake my comments as derogatory, far from it. you have my respect and admiration. however some of these identified issues are very difficult to not only understand but also to actually find and fix.

[propbeanie]

Follow the first part of the line for where the file is located, in this case, using your "Line:34 "[Unit 6]" Sequential Order==" listing, that is the Type23 in "D:\Game \DarkWaters \Data \Roster \German \Submarine \SSTypeXXIII.cfg" ("D" for drive, etc.) In that file, notice the listings for units:

[Unit 5]
Name=U-2329
DOC=19441231
DOD=19450630

[Unit 7]
Name=U-2336
DOC=19441231
DOD=19450630

[Unit 8]
Name=U-2337
DOC=19441231
DOD=19450630

It goes from Unit 5 to Unit 7, missing Unit 6. The "DB_EqpLoadout.csv Line 37:
ALB_B17g_Bomber;D:\Games\DarkWaters\data\Air\ALB_B 17g_Bomber\ALB_B17g_Bomber.eqp;=="Eqp:9=41" Double Node entry==" listing is similar (this is just one of several). Just navigate into the folder, and note in the eqp file and you'll find

[Equipment 9]
NodeName=B09
LinkName=NULL

[Equipment 41]
NodeName=B09
LinkName=NULL

I didn't look any deeper, but from the looks of it, there are more than just that one like that, but only the first mistake is listed. Hence the need for multiple runs of Hebe's tool. The "missing" stuff is all too common, and can sometimes take some digging. Some of the findings are indeed rather cryptic, but in those cases, check the spelling... Also, a "mistake" might be listed in one file, but is actually in its related file, so watch for those...


Additionally: The use of Notepad++, a freeware solution, or better still, SweeScape 010 Editor (payware) use line numbers in the left-hand column of their text editor pages. This can help immensely in finding some of these errors.

[s7rikeback]

Originally Posted by propbeanie

Follow the first part of the line for where the file is located, in this case, using your "Line:34 "[Unit 6]" Sequential Order==" listing, that is the Type23 in "D:\Game \DarkWaters \Data \Roster \German \Submarine \SSTypeXXIII.cfg" ("D" for drive, etc.) In that file, notice the listings for units:

[Unit 5]
Name=U-2329
DOC=19441231
DOD=19450630

[Unit 7]
Name=U-2336
DOC=19441231
DOD=19450630

[Unit 8]
Name=U-2337
DOC=19441231
DOD=19450630

It goes from Unit 5 to Unit 7, missing Unit 6. The "DB_EqpLoadout.csv Line 37:
ALB_B17g_Bomber;D:\Games\DarkWaters\data\Air\ALB_B 17g_Bomber\ALB_B17g_Bomber.eqp;=="Eqp:9=41" Double Node entry==" listing is similar (this is just one of several). Just navigate into the folder, and note in the eqp file and you'll find

[Equipment 9]
NodeName=B09
LinkName=NULL

[Equipment 41]
NodeName=B09
LinkName=NULL

I didn't look any deeper, but from the looks of it, there are more than just that one like that, but only the first mistake is listed. Hence the need for multiple runs of Hebe's tool. The "missing" stuff is all too common, and can sometimes take some digging. Some of the findings are indeed rather cryptic, but in those cases, check the spelling... Also, a "mistake" might be listed in one file, but is actually in its related file, so watch for those...


Additionally: The use of Notepad++, a freeware solution, or better still, SweeScape 010 Editor (payware) use line numbers in the left-hand column of their text editor pages. This can help immensely in finding some of these errors.

Anything I can help with pb ?

[s7rikeback]

Originally Posted by KaleunMarco

i am cleaning up the "bad dates" (no Raiders jokes, please! asps, very dangerous....)but the rest of these errors have me all sixes and sevens.

==Entry not found== AppearanceDate
Line:34 "[Unit 6]" Sequential Order==
=="Eqp:9=41" Double Node entry==

...just to name a few.

the more i know, the less i understand.

if the My-SH3-Tool developers are still around, please do not mistake my comments as derogatory, far from it. you have my respect and admiration. however some of these identified issues are very difficult to not only understand but also to actually find and fix.

Marco,

You have a PM sir.


Marco, your inbox is full, im unable to replt to your PM's.