ding dong just remember what i forgot :huh:

sound and speed fix knew i forgot some thing

@LW:
-No database errors.
-The particular game with the 2.01 problem never started, until we solved the issue (I wouldnt want to play a game with non synched DBs)

@JoGarry:
I m also fighting this misallignment you are mentioning. I havent paid attention if it is occurin in the modded game only.
In addition I recently have problems assigning a tracker at all, like I described in the 1st post.

:hmm:

Well, I've just heard that the mod is being evaluated by professionals (who shall remain nameless as they choose), so I have every confidence that they will find any problems. :up:

Thanks guys! ;) :D

PS if there are any problems with 2.02/3, then we can easily go back to 2.01, which was out for weeks without any reported issues.

PPS As a closing thought, anything that is wrong with 2.02/3 is simply because of random corruption introduced somewhere in the process of building the distribution, and not due to anything we changed directly, so if there is a fault found, it should be simply a matter of rebuilding a new distribution from the 2.01 version with the same changes as 2.02/3.

I hope you're not talking about me. I'm not a professional by any means, and we'll be mostly evaluating gameplay implications for the Seawolves. Our tech evalutation won't go much further than "easy to install and remove and it reliable" or "causes more problems than its worth." Of course, considering how smoothly 2.01 ran, I have a hard time accepting that there is a significant reliability problem with the mod. I'm sure it'll all get sorted out soon.

Played some more games (in fact I played the whole night lol)

You changed stuff on the SA so maybe this is related:
Next to the issue I mentioned above (not being able to assign a tracker) I now had 2 games where the SA showed a signal on BB before the TA did! Funny enough those signals were not visible in NB. It was a SW vs Sw vs 688 game. I had both subs on SA for like 20 minutes but not on TA. Even though they were visible I couldnt assign a tracker. I came closer and closer until (SW) was really very close (<1nm) but still not possible to assign a tracker on BB SA. I did a snap and killed him. <s> mc_scow_sailor.
Something is broken I believe. Or it is my LWAMI install. But what could possibly go wrong? There are no DB errors.

I pressed print screen several times, but when I just checked the folder there were none. :(

Dang, just saw its HOME not print screen...

I tried to reproduce in singleplayer and although it was slightly different in MP I got my main prob on tape.
I will upload it in a sec.

Here it is
CLICK
Its DivX so its not getting to big (16mb).
You might have to increase the size and brightness cause its rather dark.

Oh and please ignore me clicking on Tracker Assign in NB without selecting a frequency, stupid me...

Jo, did you try a fresh install?

Guys, if you get database warnings entering the game room, just DON'T start a game untill you find the reason and resolve it :)
From the start I though you get no warnings and still strange things happened - if there were warnings then databases WERE different and then absolutely no wonder that strange things happened :D

The ONLY question then is why databases are different (IF they were installed correctly).

Luftwolf, is it possible that SOMEHOW people have different versions of 2.03 ? Like mod sent to Bill and later replaced by another one ?
Maybe everyone should delete what they have and download it again, to be sure what they have ?

Well, I did increase the sensitivity of the SA... perhaps too much for the interface to handle, that's why you can't assign a tracker.

I'm concerned foremost about the random corruption problems, because that means something is "wrong."

In terms of the gameplay issues, yes, these probably need to be looked at, but at least it is simply a matter of what has been entered into the database.

Have you guys seen anymore of the random issues?

In terms of the performance of the SA vs. the TA.

The sphere array BB is designed to be much clearer than than the TA BB. Strong low frequency TA NB contacts won't have much of a distinct trace on the TA. The SA on the other hand, will display bright BB contacts on the long term, before there are distinct traces on the NB.

However, the TA should ALWAYS have a low frequency NB trace before it is picked up on SA BB. However, the difficulty is this: the TA NB contacts can be much harded to spot when using the interface, especially if the contrast on your monitor is not set correctly and you are scanning too quickly. However, a BB trace on the long term display is very hard to miss.

I've tested the sonars under a number of different conditions, with quiet contacts and with loud contacts, and the contacts always showed up first on the TA NB. However, I had the advantage of knowing where they are... so it made it easier to see the faintest trace on the NB display. For example, a Collins at 5kts will be picked up by the TB-29 at about 10nm and the SW SA will pick it up on the long term NB at about 5nm. However, the difference in the ability of the operator to distinguish these signals is very different (easier for SA BB).

In terms of the tracker issue, yes I did notice that some contacts on the BB can be seen on long term before you can assign a tracker, however, I've had this problem with stock DW as well, so I didn't think it had anything to do with the sensitivity. Personally, I'm not so worried about this issue, as long as at SOMETIME you can assign a tracker.

Like I said, these changes were fairly major, perhaps too major, and gameplay testing will decide their fate, this is a normal process... however, the issues with random corruption keep me up at night worrying about what has happened, and are NOT part of the normal process, so I am most interested right now in these problems, if they keep occuring.

Please keep the feedback coming! :up:

In the vid you can see that the signal is on SA BB long time before it is on TA BB.

I couldn't watch the video for some reason.

It should show up on the TA NARROWBand before it shows up on the SA BroadBand... and if you don't have your contrast set right, you won't see it on the NB.

The BB performance of the TA is not so great, in the mod, and according to my information, in real life as well. Many quiet targets won't show a BB trace on the TA, depending on the acoustic conditions, and this hasn't been changed in our mod (the TA sensitivties were already set pretty good...).

The video is divx, if you want I can use another codec, but it will increase the MB.