Escort radar in 1.4b

[Hebe Vollmaus]

I have found my old Test-file and made some more tests.

To me it is clear that in unmodified v1.4b the red RWR-lines used with Metox in 1943 cannot be seen on Nav-map. The Range is too low. Only one enemy Radar (Type286=3000) has lower range. Every other radar will detect you long before you get a chance the RWR-lines can appear.

This is much more different on other installs.
This is a table of some major Big-mods. The ranges has been more then doubled.

RWR                        SH3     GWX    NYGM   WAC
FuMB1Metox          4000    22000    24000    18000
FuMB10Borkum     5000    18000    20000     8000
FuMB7Naxos          7500    15000    20000     8000
FuMB26Tunis       10000    25000    24000    20000

And only here, with modified longer ranges for RWR, can this ugly "Config Date Bug" jump in.
As said above, this can happen when one or more Units in a Random RND group has on old CfgDate.
This cannot be avoided on long-Wartime-convoys. The only alternative may be split such convoys in time, when new Equipment is available. This would be impractical and blow up the filesize of the campaign. As a result also blows up the Load-time.
Or - the Class= must be deleted. I'm not sure this makes sense. Since it may have a reason why the Class is there.
Anyway, the result in this CfgBug is that the RWR-lines does not appear from these units.

Again, this may not happen in blanc SH3. Regardless of the RWR. Even the ranges for RWR grows within wartime, the ranges for allies Radar will also grow. This may not fully true in other installs.

BTW, the "Radar Warning range factor=2" in Sensors.cfg is useless.
Alas found this lately.

[John Pancoast]

Originally Posted by Hebe Vollmaus

I have found my old Test-file and made some more tests.

To me it is clear that in unmodified v1.4b the red RWR-lines used with Metox in 1943 cannot be seen on Nav-map. The Range is too low. Only one enemy Radar (Type286=3000) has lower range. Every other radar will detect you long before you get a chance the RWR-lines can appear.

This is much more different on other installs.
This is a table of some major Big-mods. The ranges has been more then doubled.

RWR                        SH3     GWX    NYGM   WAC
FuMB1Metox          4000    22000    24000    18000
FuMB10Borkum     5000    18000    20000     8000
FuMB7Naxos          7500    15000    20000     8000
FuMB26Tunis       10000    25000    24000    20000

And only here, with modified longer ranges for RWR, can this ugly "Config Date Bug" jump in.
As said above, this can happen when one or more Units in a Random RND group has on old CfgDate.
This cannot be avoided on long-Wartime-convoys. The only alternative may be split such convoys in time, when new Equipment is available. This would be impractical and blow up the filesize of the campaign. As a result also blows up the Load-time.
Or - the Class= must be deleted. I'm not sure this makes sense. Since it may have a reason why the Class is there.
Anyway, the result in this CfgBug is that the RWR-lines does not appear from these units.

Again, this may not happen in blanc SH3. Regardless of the RWR. Even the ranges for RWR grows within wartime, the ranges for allies Radar will also grow. This may not fully true in other installs.

BTW, the "Radar Warning range factor=2" in Sensors.cfg is useless.
Alas found this lately.

Excellent as always Hebe, thanks ! I halve the rwr ranges in the megamods anyway, so as to make the aircraft at least somewhat interesting.
They still can't hit the broadside of a barn anyway, but it makes the crash dive a little less boring, time after time after...

[Jeff-Groves]

Originally Posted by Hebe Vollmaus

Or - the Class= must be deleted. I'm not sure this makes sense. Since it may have a reason why the Class is there.

Class=, is a misnamed thing as I see it in the Campaign Files.
Should be Unit=
But the Game don't see it that way.
A Class is WarShip, Merchant, etc.
A Type is 4, 104, etc.

A Unit is DDTribal and so on.

So to make the decision of what a Type=4 is?
The Game reads the file in the Sea folder to decide what the Class is.

And then We descend into the WTF zone.

[Mister_M]

Originally Posted by Jeff-Groves

And then We descend into the WTF zone.

Tell us more !

[Jeff-Groves]

So. Why have a list of Type= in one file that seems to do ABSOLUTELY Not a damned thing?
Ever see an Iceberg do ANYTHING different in GWX 3 even though it's a type 16?
And Stock SH3 don't even LIST a type 16! SO.
WTF?

[Mister_M]

Because they have different behaviour.

For example, if you assign the type 4 to a battleship, it will work as a destroyer (trying to ram you, doing DC runs....).

Also, type 408 can't be spotted by the crew.

But considering ALL the English.cfg, it shows again that some ideas were finally not taken into account in the final released game (Type202=Missile Submarine, Type305=Helicopter, Type405=Missile....)

[Kapitän]

Originally Posted by Hebe Vollmaus

This is much more different on other installs.
This is a table of some major Big-mods. The ranges has been more then doubled.

RWR                        SH3     GWX    NYGM   WAC
FuMB1Metox          4000    22000    24000    18000
FuMB10Borkum     5000    18000    20000     8000
FuMB7Naxos          7500    15000    20000     8000
FuMB26Tunis       10000    25000    24000    20000

Thanks! Do you happen to know the ranges for CCoM?

[John Pancoast]

Originally Posted by Kapitän

Thanks! Do you happen to know the ranges for CCoM?

Grab S3D and you can see for yourself. Sensors.dat file. Or if you want send me that file and I'll tell you.

[Kapitän]

Originally Posted by John Pancoast

Grab S3D and you can see for yourself. Sensors.dat file. Or if you want send me that file and I'll tell you.

Ok, will check ...