So, in the process of putting togeather some 'high-detail' ships, I've bumped into something of a wall; when a platform fires a weapon with the <RequiresPlatformFireControl> tag as True, it will light up ALL the sensors on platform, even if one of them is already active and tracking the target. I noticed this as the DDG51 I had put togeather despite having is SPY-1D array active, lit up both the SPS-67 and SPS-73 surface radars when firing a SM-2 missile at an air target, despite the fact that activating either of radars wouldnt really help at all.
So now I find myself in a dilemma; do I cut the <RequiresPlatformFireControl> to False on everything? Not optimal, since it means that even with weapons that do need actives, they wont be needed (this isnt actually the case on the DDG51, as the SPY-1D can be turned off if target data is fed in from elsewhere, only the SPG-62 FC Radar needs to be online).
It would be nice if we could define exactly WHAT sensor needs to active for each weapon; for example, adding a new field into each <UnitClassWeaponLoad> section as follows would allow for much greater detail;
<UnitClassWeaponLoad>
<WeaponClassId>mod_rim66m</WeaponClassId>
<XPosition>0</XPosition>
<YPosition>-10</YPosition>
<HeightPosition>20</HeightPosition>
<WeaponBearingDeg>0</WeaponBearingDeg>
<WeaponPitchDeg>90</WeaponPitchDeg>
<MaxAmmunition>60</MaxAmmunition>
<IsPrimaryWeapon>false</IsPrimaryWeapon>
<PlatformFireControl>mod_anspg62</PlatformFireControl>
</UnitClassWeaponLoad>
This should either point to a sensor on the ship, or be 'undefined' for weapons with completely integrated FCS like Phalanx (though I guess if you wanted to get REALLY detailed, you could include all the separate FC radars for them) or that dont need FC.
Lastly a question; when sensors have a <SensorBearingRangeDeg> less than 360; what determines their facing? For weapons its defined through the <WeaponBearingDeg> fields, but what about sensors?
So now I find myself in a dilemma; do I cut the <RequiresPlatformFireControl> to False on everything? Not optimal, since it means that even with weapons that do need actives, they wont be needed (this isnt actually the case on the DDG51, as the SPY-1D can be turned off if target data is fed in from elsewhere, only the SPG-62 FC Radar needs to be online).
It would be nice if we could define exactly WHAT sensor needs to active for each weapon; for example, adding a new field into each <UnitClassWeaponLoad> section as follows would allow for much greater detail;
<UnitClassWeaponLoad>
<WeaponClassId>mod_rim66m</WeaponClassId>
<XPosition>0</XPosition>
<YPosition>-10</YPosition>
<HeightPosition>20</HeightPosition>
<WeaponBearingDeg>0</WeaponBearingDeg>
<WeaponPitchDeg>90</WeaponPitchDeg>
<MaxAmmunition>60</MaxAmmunition>
<IsPrimaryWeapon>false</IsPrimaryWeapon>
<PlatformFireControl>mod_anspg62</PlatformFireControl>
</UnitClassWeaponLoad>
This should either point to a sensor on the ship, or be 'undefined' for weapons with completely integrated FCS like Phalanx (though I guess if you wanted to get REALLY detailed, you could include all the separate FC radars for them) or that dont need FC.
Lastly a question; when sensors have a <SensorBearingRangeDeg> less than 360; what determines their facing? For weapons its defined through the <WeaponBearingDeg> fields, but what about sensors?
Last edited: