***Actually ignore this, if you've come late. Amizaur did a thorough speed test and the engine is bugged for all torps from 58-159kts.***

Ok guys, from the strange but true file.


The game engine is hardcoded to treat the max speed of the ADCAP at 55kts for calculation purposes. Raising the max speed of the weapon to something above 55kts, in effect, tells the engine to compute the physics at 55kts, and then add whatever the value the max speed is above 55kts to *any calculation*, up to about 3-4kts, based on early tests. So, when you tell the weapon to run at a particular speed, the game calculates that speed, and then adds the value above max speed to the torpedo calculations.

I have tried to run at max speed 60kts, and for any setting, we get about 4 kts above, with max 63kts. When I changed it to 58kts, I got a max speed of 61kts, and an over of about 3kts. If the max speed is set to 56kts, then the over will be 1 kts and the max speed will be 56kts, where the two effects would intersect on a graph.

This is unfortunate and unexpected. I think Ive had an interesting day of discoveries. :88) I smell DARPA's hand in this. :-j

In all seriousness, why would SCS hardcode the algorithms to 55kts for the ADCAP? since that is the only explanation for this regular but odd behavior...

Edit: I just read Amizaur's post, it could be a bug in the physics engine, but this is very particular behavior.

I think it's not ADCAP-only issue, it's common for all torpedos. Make another AI used torpedo 60kts and see how fast it will go...

Just verified that some AI subs ARE COMPLETLY DEAF to the front !!!
That would explain some stories about ramming a Han without detection.

For example Han, Harusio and Ohio are deaf in front 60 degrees zone.
The deaf zone it's not 210 degrees, I forgot that 150 degrees cone of AI sensor means 150 each side, so efectively 300 degrees. But that still leaves 60deg deaf zone in front of many AI subs...

Does anyone have any idea what max and min "Beam width" do in the sensor profile?

That is the one attribute that makes me very hestitant to change cone geometries in any arbitrary way. :hmm:

Well, I don't know unfortunately... tried to change (increase) it to simulate worse angular resultion of towed array in front-rear axis, expected wider contact trace on broadband, but the result was target track scattered for whole sonar display :-(

SCS says it support modders, then some kind of modding documentation would be nice... all we know about database entries is what Ludger and jsteed have guessed.

Oops, Amizaur corrected me. The cones are actually double the value listed in the DB, around the axis of symetry.

So the AI platforms with only one sensor are only 60 degrees blind. That's not so bad, but still... the sensors are extremely weak, as it is, and should be corrected.

Amizaur, that's why I had the idea, as a "quick fix" of giving making the LF passive sonar an "uber sensor" similiar to a more deaf FFG TA (borrowing the geometry most importantly).

The the range of the HF passive sonar could be increased and that would be good enough, as many of those subs would have a baffle.

I just gave my 688i sphere the FG TA array geometry and it works beautifully!

It's up to you guys, we could have this very soon. :up:

Keep in mind, it might make the AI a bear to fight. :know:

Edit: Given that surface platform currently share the LF passive sonar with submarines, that solution has lost a little bit of taste for me, as it would either result in very sensitive submarines or very deaf surface ships at speed (currently they are more or less anyway). I think I will try something... :ping:

I believe I gave the AI ears in the DB I sent LuftWolf a few weeks ago and broke the generic LF Passive sensor into four sensors (only three of which are used) and gave the more capable ones to the more capable submarines and the less capable ones to the less capable submarine. The Han shouldn't have an LF Passive sensor as it doesn't have a towed array. The more capable generic LF Passive sensor (which most western and European and Russian AI subs are given) is equal to the TB-16 (which happens to be the same as the SQR-19, apart from beam widths and whatnot). I also set the AI sensor cones to the same as the playable TAs.

Did you actually look at what I sent you LuftWolf? Not trying to be mean, just curious.

Yes, I looked at the submarine sound level fixes. :88)

I either forgot or didn't read that you had done the sonars as well. :oops:

I'm really sorry about that. :damn: In case you were wondering, I was planning on including what you had done in consultation with you for v1.04, including it under the "more difficult" moddling heading, as I wanted the sound levels to be agreeable for everyone.

My bad. :dead:

Edit: Please see my email. :cry:

Take a look at what I did with the sensors and see if you and Amizaur think it makes sense. I put what I changed in the DB in the textfile that was also in the zip.

I'm not trying to nag you about crediting me in the readme or whatever, just think it's kinda silly that you didn't notice the sensor issue before especially when I sent you a DB that addressed the issue weeks ago. The AI being deaf is one of the top three things wrong with the DB IMO.

:)

And BTW, I'm thinking about adding additional AI platforms into the DB and just using generic models that come with the game to portray them.

I'm sometimes a very silly person and operate under a stress level that makes me miss somethings, of course, for no good reason at all, given what my responsiblities are. :-j

In my mind, I had your mod as, "the mod with the sound level changes" and that's my only excuse. Other than that, I hope you can accept my apologizies and explanation that we made a decision not to include any sound level changes, which was probably a mistake on my part in suggesting that.

I have looked at your changes, and to be honest, I don't know the various platforms well enough to have made those changes. There are a couple of things that I would change, and I'll consult with you and Amizaur about that, but largely, I believe you will get credit for that part of the mod, because I would have definately sought your help if you knew enough to make those changes.

In terms of the AI sensor fixes, I will email you with a couple of questions right now. :up:

Fuhgettabout it. :)

For those of you that want to know NOW:

Amizaur did a thorough test of the torpedo speeds. All torpedos from 58kts max speed to 159kts max speed exhibit all kinds of funny oscillations in speed and sometimes course and depth. This behavior demonstrates a problem in the physics engine, most likely. Note: 200kts shikvals and any torpedo with speed under 58kts work fine.

I think there will be more on this to come. :hmm:

LW I thought it might keep this fraternity up to speed if I posted an extract from yours on BFC 4/9/05 :-

Can't wait - heck you guys are busy. :up: :|\

Thanks Bellman, I was just going to post an update! :sunny:

We've got a couple of other things in this next version, too. :up:

Expect a full list of changes tonight, and perhaps the mod itself. :rock: :arrgh!:

Cheers,
David