problems big problems LW !!!

[Kapitan]

playing MP in multi station last night and this guy kept designating contacts in all he designated S24 about 1,800 times before my dad pulled the plug

now i dont know wether the sonar packed up and locked or something but how do i stop it ?

i was the sonar oparator on the USS Seawolf so realy no contacts should be designated.

the poss contact displays for me on the nav screen yet i had a solid pink line with solid yellow outter edge and i couldnt see any other contact with in 10 miles, we do know it is the mod thats doing this as when we play un modded there is no problem.

also soul chaser has had the same issues next time we going to get screen shots

[darksythe]

playing MP in multi station last night and this guy kept designating contacts in all he designated S24 about 1,800 times before my dad pulled the plug

now i dont know wether the sonar packed up and locked or something but how do i stop it ?

i was the sonar oparator on the USS Seawolf so realy no contacts should be designated.

the poss contact displays for me on the nav screen yet i had a solid pink line with solid yellow outter edge and i couldnt see any other contact with in 10 miles, we do know it is the mod thats doing this as when we play un modded there is no problem.

also soul chaser has had the same issues next time we going to get screen shots

I have had this same problem before also however lwets not go off and blame it on the modders because when i experienced it was during a MS dive on my home pcs when on my laptop i had designated a contact but had also done something on the other pc at the same time.(dont remember what exactly) but i believe that the sound engine might have gotten confused trying to do 2 things at the same time so it ran home and said forget it.

Should be noted that when it happened to me it was on stock DW.

Also to be noted is that nothing can be done to the engine itself so why blame LWAMI?

[Kapitan]

well il have to get a screen shot to show you but its defenatly the mod ive been playing DW since it first came out same as many and untill now nothing like this has ever happend hence why i blame the mod

[darksythe]

I will repeat agin it is not the mod!! you have been playing DW yes. Multiplayer no. you just started MP the other day. Multistation is where this problem occurs. Which is a Multiplayer thing. I have just told you that i have had this problem before ON STOCK DW the exact problem you explain above. I believe this is a problem maybe with the Sound engine and Multi station. Not LWAMI

[darksythe]

in any event this post belongs in the Mod workshop.

[Kapitan]

huh oh excuse me sorry lol to early in the morning not functionnnnnnnnnnn zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

[Orm]

I will repeat agin it is not the mod!! you have been playing DW yes. Multiplayer no. you just started MP the other day. Multistation is where this problem occurs. Which is a Multiplayer thing. I have just told you that i have had this problem before ON STOCK DW the exact problem you explain above. I believe this is a problem maybe with the Sound engine and Multi station. Not LWAMI


Funny, but this guy sound likes someone else. :hmm:

[darksythe]

I will repeat agin it is not the mod!! you have been playing DW yes. Multiplayer no. you just started MP the other day. Multistation is where this problem occurs. Which is a Multiplayer thing. I have just told you that i have had this problem before ON STOCK DW the exact problem you explain above. I believe this is a problem maybe with the Sound engine and Multi station. Not LWAMI


Funny, but this guy sound likes someone else. :hmm:

ok ok youve got me my names not really DarkSythe its DumbStupid :88) lol who do i sound like though?

[Soulchaser]

darkscythe , i ply DW in multiplayer and multistation since the very beginning and NEVER exerienced that problem before, for me it looks like the mod. period.

[darksythe]

Well i dont believe it is but since no one wants to listen to darksythe ill just let Lw and AMI tell you the same thing i am good luck!

Side Note:
[
<?DAILY_ROUTINE>
<stress_reliver>
:damn: :damn: :damn: :damn:
</stress_reliever>
]
</?DAILY_ROUTINE>

[OneShot]

I posted on the other thread as well, but let me repeat it here too - I had this happen to me on the STOCK DW as well. This is certainly not a MOD related bug, but more due to the way the game engine handles MultiStation work. If you think this might be due to a change in the Database or Doctrine, please be so kind and explain how that could make the Game engine behave like this.

[LuftWolf]

playing MP in multi station last night and this guy kept designating contacts in all he designated S24 about 1,800 times before my dad pulled the plug

now i dont know wether the sonar packed up and locked or something but how do i stop it ?

i was the sonar oparator on the USS Seawolf so realy no contacts should be designated.

the poss contact displays for me on the nav screen yet i had a solid pink line with solid yellow outter edge and i couldnt see any other contact with in 10 miles, we do know it is the mod thats doing this as when we play un modded there is no problem.


darkscythe , i ply DW in multiplayer and multistation since the very beginning and NEVER exerienced that problem before, for me it looks like the mod. period.

There is ABSOLUTELY NOTHING we could have done, by altering database and doctrine files, that could cause this issue. Its resides solely in the interface.

I will answer the other problems in the thread in the mod forum.

Thanks for raising these issues however. :up:

If you want my opinion, it sounds like something on Kapitains computer that is causing the issue.

Kapitain, do you have any interface mods installed?

[LuftWolf]

I have sent another version of the mod to Bill that installs the mod directly to your DW folders, just as in LWAMI 2.00.

It should be posted soon.

[Kapitan]

i did have at first but i got rid of them

i compleately cleaned the dw re installed and out the mod in works almost fine but some times the con sonar contact s14 bearing 212 or some thing comes up (example)

[LuftWolf]

i compleately cleaned the dw re installed and out the mod in works almost fine but some times the con sonar contact s14 bearing 212 or some thing comes up (example)

There really is nothing we could do to make that happen... that kind of issue is strictly in the interface.

Could you be more specific as to when that happens?

[Kapitan]

see soul chasers post in dangerous waters mods

[darksythe]

Im not the type to say told yah so....
so i wont :-j

[Amizaur]

Maybe something indeed happens while files are copied. Like read-only files, or something I didn't anticipated. You could have just check it. Before installing mod, remember/write somwhere filesizes and more impoortant dates of all database files. Apply install or uninstall and check what happened in the folder. Are all files with new date ? Or maybe some are unchanged ? And so on. I would ask you to try find the reason yourself if you can, sometimes when error is reported I look and at once understand what gone wrong, what was wrong. But sometimes I can't -everything seems to be absolutely all right and this may be computer specyfic thing (or at least - NOT specyfic for MY coputer). It's hard to tell on a distance what's happening on other's computer

So if you can, try to find the source of problems yourself. Look into bat files, you see what they should do. Run them and check if they have done what they should. Are files really overwritten ?
Personally if I report a bug to SCS, I try to find it's source/reason if I can, and if I can even find possible solution.
About files that are left from the mod and not overwritten. Well we'll add delete command I think and then everything would be clear. The remaining mod files were not deleted, because they don't interfere with anything, they really should not hurt agt all. And second - while testing we have in database/doctrine folders many different non-game files like DWEdit, doctrine checker, and also many versions of different doctrines and backup files. So I prefered that only files that matters were overwritten. But OK, if you suspect that this may be source of problems, I'll ad delete to the bats. But please, if you can, try to determine yourself what's happening, are files really overwritten as they should ect.
Also if you experience incompatibility problems after manual installing 2.02 mod, try to rever to 2.01 and check if then everything is OK ? If yes, then we'll search for error in 2.02. Bats were not changed. Also, there is no need to reinstall the game, if you have originall database and doctrine folders stored. The mod is confined to database and doctrine folders only, no other changes.

P.S. Yep, returning to 2.01 to see if all goes smoothly there is good idea. If problems with 2.02 are so serious you can't play, return to 2.01 please and give us day or two, we'll try to determine source of problems with 2.02.

P.S.2. I see 2.03 is coming, so please return to 2.01 untill that.

[MaHuJa]

This is indeed a problem with DW, and not with LWAMI. I experienced it long before LWAMI 1.0 came out.

Whenever this happens, the sonar operator should drop the tracker as soon as possible. (Dragging the letter off the contact). This should stop more of them from appearing.


On a related note, although it's been a while since it happened to me, I think I was the sonar guy on a multistationed sub when it happened, and that the other guys didn't get the problem. Is this true (for *all* the other cases too)?
Can anyone say with any (please specify) degree of certainty that this happened while they were *not* sonar?

For that matter, has this problem been seen outside the US subs?

[Jamie]

I've seen this problem as well, but have had a tough time reproducing it on my end. If anyone can find a set of steps to reproduce it, please post here so one of the BETA testers can put it into our bug tracking system...

Kapitain, is it really a "problem, big problem"?
You guys and your topic titles... :roll:

[Kapitan]

nope all sorted thanks mainly to LW and soul chaser

[LuftWolf]

Thanks for the "moral support" Jamie. :D ;)

I thought Boomer's last topic title was pretty positive... until I read the post... :lol: :lol: :lol:


I'm glad you got it all taken care of, Kapitain. :up:

[JoGary(sco)]

yes. had it happen to if it same problem i think it is. What i experienced was a ambigus contact on sonar i had given a tracker to and then dropped on nav map kept getting remarked and new tracker added even though sonar auto crew was off. Every time i tried dropping it it reapeared. Dont think i have had it happen for a while though. And it was not in a Multi Sation game.

[MaHuJa]

yes. had it happen to if it same problem i think it is. What i experienced was a ambigus contact on sonar i had given a tracker to and then dropped on nav map kept getting remarked and new tracker added even though sonar auto crew was off. Every time i tried dropping it it reapeared. Dont think i have had it happen for a while though. And it was not in a Multi Sation game.

Sounds like you were in the ffg, where dropping a TA contact without unassigning the tracker will have it track the other side. That is desired behaviour. (Did the manual mention how to stop the tracker?)

We're talking about a single contact, e.g. s24, appear almost on top of an older (by a second or so) s24. At least I am, and I suspect at least some others too.

[JoGary(sco)]

no, was sub i was in but it does seem we are talking about diferent things :hmm: