Patch Suggestions (Monitored by Sonalysts)

[MaHuJa]

Originally Posted by Wildcat

if you assign an sm2 to a target then fire it, the missile will launch then the sm2 button will flash for a while. That's fine. When you reload the missile however, the new sm2 will (sometimes) not be available for launching until you deassign then reassign the target.

There is a bug there, but it's not what you describe. Hold off a few seconds before loading the next missile, and you'll see the FCR status switch to "CWI" - and pressing that button then will shut down the missile. The bug is that it won't switch to CWI if you're too quick about reloading.

In reality, CWI is needed for the missile to home on a target.

Then again, it's possible for the real STIR and CAS to guide multiple missiles, though only at a single target. According to some forum poster anyway.

Aditionally I ask that all inbound contacts, regardless of whether they appear as sea, air or subsurface, exceeding 400 knots, automatically be assigned to the FCR when clicked on, if the air search radar is enabled. This would allow easier hard kills in the face of a missile attack, rather than having to bungle around with a ton of buttons.

Sounds like a bad idea to me. At the very least, I want to be able to turn that off.

On the other hand, I could imagine an autocrew function for it that automatically launched weapons at (at least) airborne targets in the target queue. (excepting, of course, held ones)

[TopTorp '92]

Recommendations to improve DW performance (Seawolf):

1. Ping steal bearings & ranges should be a part of game-play. Pingsteal is a way sonar can compute target’s range based on the target’s use of active sonar. In addition, any active sonar may return a signal on any nearby target, thus providing a bearing and a range to listening platforms. This too should be included in DW gameplay. Example, you have a scenario with three units: 1 blue team surface warship actively pinging, 1 blue team submarine nearby, 1 red team submarine nearby. Based on the use of the surfaces warship’s use of active sonar, both blue and red submarines will have bearing and range to blue surface warship. Red submarine will also get a bearing and range to blue submarine from blue surface warship’s sonar. Blue submarine will get a bearing and range to red submarine from surface warship’s sonar. (This is almost like link data, but the blue team submarine need not be in communication with blue team surface warship.)

2. ADCAP post launch wire information should be included in gameplay. This includes the mode of operation (searching, homing, C/M, & weapon armed, etc.), weapon depth, course, speed.

3. Cosmetic: can we make the Seawolf periscope viewing window (eyepiece) larger?

4. Include a position keeper in the TMA module. See http://www.maritime.org/tdc.htm for background information on a position keeper. WWII style Position Keepers were modeled in Fire Control software and used to dial in very quick solutions for a variety of purposes, including snapshot scenarios. This should be very easy for the DEV Team to model in DW.

[Deathblow]

Originally Posted by TopTorp '92

ADCAP post launch wire information should be included in gameplay. This includes the mode of operation (searching, homing, C/M, & weapon armed, etc.), weapon depth, course, speed.

Quoted for agreement

4. Include a position keeper in the TMA module. See http://www.maritime.org/tdc.htm for background information on a position keeper. WWII style Position Keepers were modeled in Fire Control software and used to dial in very quick solutions for a variety of purposes, including snapshot scenarios. This should be very easy for the DEV Team to model in DW.

I remember this option being present of the old Fast Attack by Sierra. Was pretty handy.

[TopTorp '92]

Torpedoes should not detonate on CMs. Please create a fix where torpedoes don't do this.

[LuftWolf]

The fix is already available.

Amizaur corrected the torphoming doctrine as part of the LWAMI mod package.

IF TgtClass $= weap and NOT TgtName $= "Towed Decoy" AND TgtRng <= 30 THEN Drop ENDIF

Sonalysts will not change this in the stock game because they believe it is good for sales to have torpedoes explode on CMs.

[TopTorp '92]

Originally Posted by LuftWolf

The fix is already available.

Amizaur corrected the torphoming doctrine as part of the LWAMI mod package.

IF TgtClass $= weap and NOT TgtName $= "Towed Decoy" AND TgtRng <= 30 THEN Drop ENDIF

Sonalysts will not change this in the stock game because they believe it is good for sales to have torpedoes explode on CMs.

LWAMI? Where? Who?

hi everybody...Good to be back
I have to add a little comment here. The SA N 8 behaviour is more realistic than the stinger's. You'll see it is somewhat harder to hit with the SA N 8 than with the stinger.

Two points I think require some attention.
First, in some cases weapon stats have been underated or overated. For example, most of the times (arguably all of the times) you can avoid a type-40 torp with a 688i class sub simply by running away from it. Also, the 65cm torpedo should have (as in reality it does) a greater range. The range of the ADCAP varies with speed, as well as the 65 cm torpedo.

Second, the maximum speed of the 688 subs is 30-32 Knots. You'll never see them going 34 or 35, their test depth is 300m and collapse depth 450 meters.

A very good introductory text on naval weapons engineering can be found at:
http://www.fas.org/man/dod-101/navy/...0/syllabus.htm

[LoBlo]

Can we have more access to the "AttackBest" and "FireBest" logic?

Its such a intergral part of the doctrine and being able to understand it would allow some better modding efforts. Especially in the since of trying to improve aircraft behavior.

http://www.subsim.com/radioroom/showthread.php?t=93941

thx
lb

ps) Its unprecedented, but if some of the game programmers would stop by from time to time in the mod workshop to drop tips and hints in our efforts it would be nice. Perhaps create a login that doesn't reveal your a SCS DW programmer if you want to remain anonymous.

[LuftWolf]

LoBlo... the logic is set entirely by the parameters in the database. You have total control from there.

Also, you can use the command Attack "<WeaponName>" instead of AttackBest and FireBest, but you have to create a unique doctrine for every platform you want to use that command.

Yes, I wish Jamie would stop over again at some point.

[LuftWolf]

Check the bottom of my signature for a link to the mod readme and a place you can download it, check the mod forum here, or go to www.subguru.com , the best place for DW Mods and Missions on the internet, courtesy of Bill Nichols!

Cheers,
David

[LoBlo]

I would suggest increasing the complexity and control over Aircraft carrier behavior. Although DW is a ASW sim, CVs are the linchpin of the modern USN fleet and major operations, inlcuding ASW patrols center around their presence and firepower.

Being able to trigger more aggressive aircraft launches (right now the CV launch only 2-4 aircraft at any threat) and/or being able to script aircraft launches at the doctrine level would be a big help. Also, the aircrafted launched have a mind of their own and it would be nice to have more control/input on their behavior.

[LuftWolf]

Aircraft launches can be scripted at the doctrine level, just no doctrines currently use this function, although LWAMI will probably change that sooner or later.

[LoBlo]

Originally Posted by LuftWolf

Aircraft launches can be scripted at the doctrine level, just no doctrines currently use this function, although LWAMI will probably change that sooner or later.

I didn't no that.

What's the doctrine command for "launch"?

[LuftWolf]

Launch "<value>" where value is the name of the aircraft to be launched.