problems big problems LW !!! - Page 2

Kapitan · 10-31-05, 09:49 AM

see soul chasers post in dangerous waters mods

darksythe · 10-31-05, 10:07 AM

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

Amizaur · 10-31-05, 01:41 PM

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 · 11-03-05, 01:21 PM

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 · 11-03-05, 01:44 PM

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...

Kapitan · 11-03-05, 04:57 PM

nope all sorted thanks mainly to LW and soul chaser

LuftWolf · 11-03-05, 06:53 PM

Thanks for the "moral support" Jamie.

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

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

JoGary(sco) · 11-03-05, 08:00 PM

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 · 11-03-05, 08:48 PM

Quote:

Originally Posted by 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.

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) · 11-04-05, 12:31 PM

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

10-31-05, 09:49 AM	#16
Kapitan Sub Test Pilot Join Date: Mar 2005 Location: UK + Canada Posts: 7,132 Downloads: 77 Uploads: 7	see soul chasers post in dangerous waters mods __________________ DONT FORGET if you like a post to nominate it by using the blue diamond Find out about Museum Ships here: https://www.museumships.us/ Flickr for all my pictures: https://www.flickr.com/photos/131313936@N03/ Navy general board articles: https://www.navygeneralboard.com/author/aegis/

10-31-05, 10:07 AM	#17
darksythe Lieutenant Join Date: Sep 2005 Posts: 269 Downloads: 4 Uploads: 0	Im not the type to say told yah so.... so i wont __________________ For those who try and fail. Try Again. For those who try and succeed......... How dare you!

11-03-05, 04:57 PM	#21
Kapitan Sub Test Pilot Join Date: Mar 2005 Location: UK + Canada Posts: 7,132 Downloads: 77 Uploads: 7	nope all sorted thanks mainly to LW and soul chaser __________________ DONT FORGET if you like a post to nominate it by using the blue diamond Find out about Museum Ships here: https://www.museumships.us/ Flickr for all my pictures: https://www.flickr.com/photos/131313936@N03/ Navy general board articles: https://www.navygeneralboard.com/author/aegis/

11-03-05, 06:53 PM	#22
LuftWolf Ocean Warrior Join Date: May 2005 Location: Free New York Posts: 3,167 Downloads: 2 Uploads: 0	Thanks for the "moral support" Jamie. I thought Boomer's last topic title was pretty positive... until I read the post... I'm glad you got it all taken care of, Kapitain. __________________ LW

11-03-05, 08:00 PM	#23
JoGary(sco) A-ganger Join Date: May 2005 Location: Loch lomand, Scotland Posts: 71 Downloads: 10 Uploads: 0	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. __________________ Joseph,Gary Winters jgw28@blueyonder.co.uk ICQ : 259-346-534 http://seawolves.org

10-31-05, 01:41 PM	#18
Amizaur Sonar Guy Join Date: Nov 2002 Location: Poland Posts: 398 Downloads: 0 Uploads: 0	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.

11-03-05, 01:21 PM	#19
MaHuJa Sonar Guy Join Date: Jan 2002 Location: 59.96156N 11.02255E Posts: 385 Downloads: 3 Uploads: 0	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?

11-03-05, 01:44 PM	#20
Jamie Sonalysts Inc. Join Date: Jul 2002 Location: Middletown, CT (USA) Posts: 204 Downloads: 0 Uploads: 0	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...

11-04-05, 12:31 PM	#25
JoGary(sco) A-ganger Join Date: May 2005 Location: Loch lomand, Scotland Posts: 71 Downloads: 10 Uploads: 0	no, was sub i was in but it does seem we are talking about diferent things :hmm: __________________ Joseph,Gary Winters jgw28@blueyonder.co.uk ICQ : 259-346-534 http://seawolves.org