It can be done, but that would cripple the game far more then it would be worth. I doubt luftwolf will do it, but you can do it yourself if you would like. Just download DW Edit, and remove everything related to a two stage weapon.

What he said. :)

My advice, if the Mission Debrief screen must be 100% accurate for GNSF matters, is to simply prohibit their use, but this means also banning ALL SUBROCS and the AI MH60 for the FFG... so that doesn't seem like a very attractive option.

The mission replay is pretty conclusive, so I'd adjust your reporting standards to allow manual entries for weapons that don't show kills on the debrief.

Cheers,
David

Not to mention banning matches that last past X amount of time after a platform is killed. (Where X= the amount of time it takes the game to remove the dead platform)

LW - I was going to load up torn stars last night but I got sidetracked playing DW with your latest mod. Good job by the way! I love it and thx!

By the way, you know the splash screen still reads 3.07 instead of 3.08?

-S

Try reading my last posts a short way up. That happens when you just install the new over the old mod.

[quote=LuftWolf]Thanks, we have manual entries in our reporting system so it is not a problem. What happen when i have enemy AI surface killed with ASM? If i have a kill trigger assigned? I think the game will not count those kills.

It is easier to remove all Russian boats - then also 2-stages of a misiles will not be launched :rotfl: :rotfl: :rotfl:

[quote=Micksp]I just tried to outsmart the game on this, but I couldn't. Triggers testing for side didn't fire. Triggers testing for the base missile didn't fire. Triggers testing for the final stage didn't fire. The only trigger that fires is the general kill trigger. This can be a problem for scenarios that count the number of neutrals one side has killed.

Does anyone know a way around this?

update: tried it using attached kill goals + attack doctrine and with detacthed automatic goals + kill doctrine. No joy.

ML, i've tried the same like you the last night and have the same results. If i have something possitive discovered i'll post here.

BRGDS

I was messing around with ASW missiles and I launched a ss-n-27 asw and I noticed that it didn't drop its torp but the whole thing bosster and all flew into the sea at impat point and then released its torp.

Before they dropped the torp quite high up and it slowed down before it hit the sea.

Anyone else find this?

Sometimes, yeah. He's got them releasing a lot closer than he used to, that's for sure. It seems to be only cosmetic, though.

I prefer when they dropped higher up.

Also I have noticed too that AI deployment of the SUBROC weapons is a joke, they are always way off. Maybe the AI doctrine could be improved to firm up the solution.

I think the AI is only shooting as accurately as their TMA solution allows. With the reduced torp seeker performance in LW/Ami, that means there will be more misses. The newer LW/Amis also have improved engagement ranges for AI subs, and with longer ranges come larger errors.

In stock DW, at least yet in 1.03 (not sure about 1.4) there is major error in SUBROC doctrine files, making them shoot SUBROCs at about 3 times larger distance (seems like imperial vs. metric units bug).

Even old versions of LWAMI fixed this. With LWAMI it should not happen anymore.
Also AI TMA works more or less like this: 1 LOB - big error .. 3 LOBS - smaller error .. 5 LOBS - nice solution.

With LWAMI if you meet enemy cruiser with SUBROCs and active sonar, in the moment he picks you up, 6-10 SUBROCS is heading at your EXACT location. Survive this ..