LuftWolf and Amizaur's Weapons and Sensors Database Mod v3.072 --- Now Available!!! - Page 6

Janus · 03-02-07, 04:50 AM

Quote:

Originally Posted by Dr.Sid

You could also have frequency range set to low frequencies. TA NB shoould show something anyway. Something simmilar never ever happend to me and I use all the mods all the time.

The frequency range is set to 2000 and I see the contact now (it was rather faint and a bit off bearing the first time).

Quote:

Originally Posted by Dr.Sid

I guess you should try to repeat the situation. If it happens, save the mission. Try if it exists after mission reload.

I've done that and unfortunately it does not help. The situation is I have the contact at bearing 30 on TA and sphere broad- and narrowband and I can assign trackers on all arrays but sphere broadband although it is very clear.

I have uploaded the mission file and save file on rapidshare.

Dr.Sid · 03-02-07, 07:16 AM

I've tried the save and I see both contacts perfectly on NB. The sphere contact is quite dim .. I believe you could miss it if you don't have screen properly set. But the TA contact is nice and bright.

http://roger.questions.cz/other/dump00053459.jpg
http://roger.questions.cz/other/dump00046891.jpg

Edit: OIC .. you can't mark the sphere on BB .. that's perfectly OK .. it's just too weak yet. Such situations happens in stock too, but at different ranges/sound levels. Mark it on NB and be happy.

Janus · 03-02-07, 07:43 AM

Quote:

Originally Posted by Dr.Sid

Edit: OIC .. you can't mark the sphere on BB .. that's perfectly OK .. it's just too weak yet. Such situations happens in stock too, but at different ranges/sound levels. Mark it on NB and be happy.

Thank's for your help. The screenshots resemble what I was seeing too.
I am a bit disappointed to hear that this is normal. I find it lame to be able to mark a relatively dim sphere NB contact but cannot mark the same contact on BB which is clearly visible in short and intermediate timescale whereas the TA is more washed out and only visible in intermediate

Okay I'll have to cope with it...

Dr.Sid · 03-02-07, 07:45 AM

Yes .. it is lame .. but it is not LWAMI issue.

Molon Labe · 03-02-07, 08:28 AM

This is actually a very old issue, and it's sort of a LW/Ami issue, but not really.

Sometimes, BB traces will appear that just aren't markable. It has to do with the thresholds set in the sim. LW/Ami increased the BB sensititivy of the spherical array. Is it turned out, this also increased the gap between the visual threshold and the markable threshold, which means that the bug occurs more with LW/Ami than it does with stock DW.

LuftWolf · 03-02-07, 08:53 AM

READ THE README!!!

Quote:

Originally Posted by LWAMI Readme

Sphere and Hull Arrays—The sensitivity of the Sphere and Hull arrays has been increased relative to the Towed Array (to be clear, the TA is still much more sensitive in terms of long range performance) to better simulate their reported real world specifications. Also, the stern facing baffle of the Sphere has been increased to 120 degrees for active and passive modes, including the FFG and all AI platforms. It is not uncommon for contacts to show up on the broadband sphere before they show up on the narrowband sphere, and loud contacts will also show up more clearly on the sphere array broadband than the towed array broadband once both arrays have detected the contact. Expect to use the Sphere and Hull arrays more now to track and identify surface traffic and build situational awareness utilizing DEMON and TMA, and reserve the TA for finding and tracking those quiet hostile submarines or distant warships on narrowband. NOTE: Known Issue. It will be possible to see and hear contacts on the Sphere array before you can assign a Broadband tracker to them. You can immediately assign a narrowband tracker to all contacts on the sphere with a narrowband signature, although it is intended that generally contacts will be detected on the sphere broadband first. The broadband tracker issue is not intended, although it is present in stock DW as well, and the mod does not make it any worse in game play terms.

Cheers,
David

Molon Labe · 03-02-07, 08:58 AM

Yeah, what he said!

We're going to need a new acronym: RTFRM

Bellman · 03-02-07, 09:37 AM

Well here's another one - we know about in stock but I leave others to interpret whether the feature has intensified in LwAmi.
I would label it Psychic NB Classification.

Facts - my SW 6 kts 492 ft other side layer and 14.4 nm from Collins at 3 knts and 147 ft. SA BB has no indications except a very infrequent spasmodic SNR 1 which would mostly be missed. NB 'Search' has no indication nor does a slow scan reveal any tonals BUT (as we know) the 'Ship classification window' attempts an incorrect classification which is adequate for attack purposes !

The TA had both BB and NB tonals so as has been claimed previously that for some reason the software is porting extra info. from the TA to the SA. OK we know, we know, but come on a Collins at 3 knts at 12.4 NM on SA ??

And what if this feature is not TA dependent !

Now I can live with that just but when I take the MH60 for testing I still get the very prescient 'Pschic classifications' reported above, mainly with the dipping sonar.:hmm:

Dr.Sid · 03-02-07, 09:44 AM

Somehow I don't understand what is the problem.

Molon Labe · 03-02-07, 09:56 AM

Definitely a stock issue.

Don't forget about the sonobuoy filters seeing one more dot than is displayed on the screen.

LuftWolf · 03-02-07, 10:02 AM

I love it, I release a new version of the mod, and everyone forgets what they've been experiencing for two years.

Forget "psychic classifications", I've got the Memory Erasing Mod here!

Cheers,
David

Bellman · 03-02-07, 10:02 AM

In the SW its merely inconvenient NP but in the MH60 it provides a cheat and if its present in non TA subs its a big cheat.

Sid: Simple there shouldnt be a line twitching 'ship classification ' attempt giving away a contacts position when there are no available tonals indicated on that sonar source.

LuftWolf · 03-02-07, 10:03 AM

Yes, it's absolutely all my fault, including the updates that have to be done to the NWP for the new version of FC, and the incompatibilities between SCX and the NCP version of SC.

It's all my fault... I need to fix it all right away. LOL :rotfl: :rotfl: :rotfl:

Cheers,
David

Edit: That's not directed at you Bellman, it's just a general statement.

Bellman · 03-02-07, 10:04 AM

LW: Accepted - I said known issue. The question is in tuning-up sonar sensitivities, as reported, has the impact of this 'cheat' increased ?

LuftWolf · 03-02-07, 10:06 AM

Beats me... I'm at the point with this sim where I just accept the problems and focus on the things I have control over.

At some point, someone else has to gain some kind of competancy with the basic workings of this sim.

Cheers,
David

Edit: Nevermind that last comment, plenty of people do, but few of them have the lack of sense to post to the message board every day and make a mod for public use. :p

03-02-07, 08:28 AM	#80
Molon Labe Silent Hunter Join Date: Jun 2004 Location: Along the Watchtower Posts: 3,810 Downloads: 27 Uploads: 5	This is actually a very old issue, and it's sort of a LW/Ami issue, but not really. Sometimes, BB traces will appear that just aren't markable. It has to do with the thresholds set in the sim. LW/Ami increased the BB sensititivy of the spherical array. Is it turned out, this also increased the gap between the visual threshold and the markable threshold, which means that the bug occurs more with LW/Ami than it does with stock DW. __________________

03-02-07, 08:58 AM	#82
Molon Labe Silent Hunter Join Date: Jun 2004 Location: Along the Watchtower Posts: 3,810 Downloads: 27 Uploads: 5	Yeah, what he said! We're going to need a new acronym: RTFRM __________________

03-02-07, 09:37 AM	#83
Bellman Sea Lord Join Date: Feb 2004 Posts: 1,945 Downloads: 220 Uploads: 0	Well here's another one - we know about in stock but I leave others to interpret whether the feature has intensified in LwAmi. I would label it Psychic NB Classification. Facts - my SW 6 kts 492 ft other side layer and 14.4 nm from Collins at 3 knts and 147 ft. SA BB has no indications except a very infrequent spasmodic SNR 1 which would mostly be missed. NB 'Search' has no indication nor does a slow scan reveal any tonals BUT (as we know) the 'Ship classification window' attempts an incorrect classification which is adequate for attack purposes ! The TA had both BB and NB tonals so as has been claimed previously that for some reason the software is porting extra info. from the TA to the SA. OK we know, we know, but come on a Collins at 3 knts at 12.4 NM on SA ?? And what if this feature is not TA dependent ! Now I can live with that just but when I take the MH60 for testing I still get the very prescient 'Pschic classifications' reported above, mainly with the dipping sonar.:hmm: __________________ Liberty, Equality, Fraternity

03-02-07, 09:56 AM	#85
Molon Labe Silent Hunter Join Date: Jun 2004 Location: Along the Watchtower Posts: 3,810 Downloads: 27 Uploads: 5	Definitely a stock issue. Don't forget about the sonobuoy filters seeing one more dot than is displayed on the screen. __________________

03-02-07, 10:02 AM	#86
LuftWolf Ocean Warrior Join Date: May 2005 Location: Free New York Posts: 3,167 Downloads: 2 Uploads: 0	I love it, I release a new version of the mod, and everyone forgets what they've been experiencing for two years. Forget "psychic classifications", I've got the Memory Erasing Mod here! Cheers, David __________________ LW

03-02-07, 07:16 AM	#77
Dr.Sid The Old Man Join Date: May 2005 Location: Czech Republic Posts: 1,458 Downloads: 6 Uploads: 0	I've tried the save and I see both contacts perfectly on NB. The sphere contact is quite dim .. I believe you could miss it if you don't have screen properly set. But the TA contact is nice and bright. http://roger.questions.cz/other/dump00053459.jpg http://roger.questions.cz/other/dump00046891.jpg Edit: OIC .. you can't mark the sphere on BB .. that's perfectly OK .. it's just too weak yet. Such situations happens in stock too, but at different ranges/sound levels. Mark it on NB and be happy.

03-02-07, 07:45 AM	#79
Dr.Sid The Old Man Join Date: May 2005 Location: Czech Republic Posts: 1,458 Downloads: 6 Uploads: 0	Yes .. it is lame .. but it is not LWAMI issue.

03-02-07, 09:44 AM	#84
Dr.Sid The Old Man Join Date: May 2005 Location: Czech Republic Posts: 1,458 Downloads: 6 Uploads: 0	Somehow I don't understand what is the problem.

03-02-07, 10:03 AM	#88
LuftWolf Ocean Warrior Join Date: May 2005 Location: Free New York Posts: 3,167 Downloads: 2 Uploads: 0	Yes, it's absolutely all my fault, including the updates that have to be done to the NWP for the new version of FC, and the incompatibilities between SCX and the NCP version of SC. It's all my fault... I need to fix it all right away. LOL :rotfl: :rotfl: :rotfl: Cheers, David Edit: That's not directed at you Bellman, it's just a general statement. __________________ LW Last edited by LuftWolf; 03-02-07 at 10:26 AM.

03-02-07, 10:04 AM	#89
Bellman Sea Lord Join Date: Feb 2004 Posts: 1,945 Downloads: 220 Uploads: 0	LW: Accepted - I said known issue. The question is in tuning-up sonar sensitivities, as reported, has the impact of this 'cheat' increased ? __________________ Liberty, Equality, Fraternity

03-02-07, 10:06 AM	#90
LuftWolf Ocean Warrior Join Date: May 2005 Location: Free New York Posts: 3,167 Downloads: 2 Uploads: 0	Beats me... I'm at the point with this sim where I just accept the problems and focus on the things I have control over. At some point, someone else has to gain some kind of competancy with the basic workings of this sim. Cheers, David Edit: Nevermind that last comment, plenty of people do, but few of them have the lack of sense to post to the message board every day and make a mod for public use. :p __________________ LW