Leader bug and WitPDecoder (Full Version)

All Forums >> [Current Games From Matrix.] >> [World War II] >> War In The Pacific - Struggle Against Japan 1941 - 1945 >> Tech Support



Message

Cpt Sherwood -> Leader bug and WitPDecoder (6/2/2007 3:21:22 AM)

Now that Woos has given us the excellent WitPDecoder we can see things that we couldn't before. I noticed that when I wanted to change leaders and used WitPDecoder to help me, I was given leaders to select that were all ready in command of another unit. Here is one picture. LTC T. Kelly is commanding the AO Brazos. I asked to change the leader and as you can see, the first three on the list are commanding subs somewhere in the Pacific. I know it also happens with war ships. I have not really looked at gound commanders yet, but I will be. If you do not use WitPDecoder to anayize your leaders and game, you are taking a risk of problems.



[image]local://upfiles/18938/E77D8990969844598B946EE33F6A1D31.jpg[/image]



jwilkerson -> RE: Leader bug and WitPDecoder (6/2/2007 5:27:32 AM)

Yup, there are a fair number of "duplicates" (leaders used in more than one unit) in the database and until these are corrected they will cause problems. The system was designed to handle only one use of a leader at a time, but the editor has no check to enforce this.




Cpt Sherwood -> RE: Leader bug and WitPDecoder (6/2/2007 5:38:37 AM)

But I think you are missing the point. I am trying to select a new commander and some of the choices given are commanders that are commanding another ship. Why is the program letting me chose a leader that is all ready commanding a ship? Most interestingly, I have made most of my leader changes in the subs. Now I find that the first three commanders I am presented with are currently commanding subs.



LarryP -> RE: Leader bug and WitPDecoder (6/2/2007 6:12:52 AM)

Where is this WitPDecoder located?



Cpt Sherwood -> RE: Leader bug and WitPDecoder (6/2/2007 6:19:50 AM)

You will need to read this thread. WitPDecoder thread



michaelm75au -> RE: Leader bug and WitPDecoder (6/2/2007 6:58:25 AM)

Out of curosity, what version of WITP are you using.



Cpt Sherwood -> RE: Leader bug and WitPDecoder (6/2/2007 7:18:41 AM)

This would be version 1.804. The senario is BigBs 192.



qgaliana -> RE: Leader bug and WitPDecoder (6/4/2007 7:54:47 PM)

One problem I've noticed seems to be when I create a TF from an existing TF and move the flagship out. I (sometimes, not sure if always, may depend on being docked or not) wind up with the same commander in charge of both TFs.

Once the leader winds up in 2 places, it seems to be difficult for the program to track him correctly. In particular, it looks like when you disband the TF or assign a new commander, the old leader gets flagged as available and the capability isn't there to check to see if they are still assigned elsewhere.

After some brief experiments, the only way to tidy this up seemed to be to remove the leader in question from every assignment. Then when you assign them somewhere they seem to finally get correctly tagged as 'busy' and stop showing up in the list of available leaders. (NB - I talk about tags and flags, but I don't know what's going on under the hood, could just as easily be a complicated pointer tree linking everything. I'm just metaphorically describing the observed behaviour).

And yes, couldn't track this until witpdecoder, after which I found some of my more choice commanders in charge of 3-4 subs.



cverbrug -> RE: Leader bug and WitPDecoder (6/6/2007 11:36:38 AM)

Hi all,


Now we are talking of leader problem. I am playing a pbem game and i lost my naval HQ leaders from P-Z. I have no idea why and how (gues it is related to installing a patch on an already existing pbem game). None of the leaders with a name starting with P-Z is there anymore. Even the units having one of those leaders assigned showed 'staff officer'. It only occured with the naval HQ leaders. The others are fine.
Even Yamamoto is gone.

Has anyone ever observed the same?

chris



rtrapasso -> RE: Leader bug and WitPDecoder (6/12/2007 1:56:00 PM)


quote:

ORIGINAL: Cpt Sherwood

Now that Woos has given us the excellent WitPDecoder we can see things that we couldn't before. I noticed that when I wanted to change leaders and used WitPDecoder to help me, I was given leaders to select that were all ready in command of another unit. Here is one picture. LTC T. Kelly is commanding the AO Brazos. I asked to change the leader and as you can see, the first three on the list are commanding subs somewhere in the Pacific. I know it also happens with war ships. I have not really looked at gound commanders yet, but I will be. If you do not use WitPDecoder to anayize your leaders and game, you are taking a risk of problems.




i thought WITP was DESIGNED with producing "clones" - and i am not sure if this is a bug. i will consult with higher-ups...



rtrapasso -> RE: Leader bug and WitPDecoder (6/12/2007 7:54:05 PM)

OK - i am told we need to look into it - but you need to provide a SAVE file (nonfinalized) that happens immediately before the bug. If you have one, let me know and then we can proceed.



Cpt Sherwood -> RE: Leader bug and WitPDecoder (6/13/2007 2:32:19 AM)

I have all the save files you will need, it is always present now. I need your email address and I'll send one to you with a write up.



Cpt Sherwood -> RE: Leader bug and WitPDecoder (6/14/2007 1:28:27 PM)

Harsher message than I should have sent, sorry.



rtrapasso -> RE: Leader bug and WitPDecoder (6/14/2007 2:50:41 PM)

Capt Sherwood -

Sorry - i didn't see your post sooner - i check the support forum once or twice a day... somehow i missed your prior post...

send save to rtrapasso @gmail.com (no space in address - blank put in to foil spambots)

Give details of where the leader(s) vanish - and as mentioned in previous pm, i will need passwords (if PBEM).

Cheers,
Bob T.



rtrapasso -> RE: Leader bug and WitPDecoder (6/14/2007 8:55:40 PM)

bump



Cpt Sherwood -> RE: Leader bug and WitPDecoder (6/14/2007 9:00:16 PM)

You will have to wait until I gete home from work. At least 6 more hours



rtrapasso -> RE: Leader bug and WitPDecoder (6/14/2007 9:02:18 PM)

OK - just wanted to make sure it didn't get buried... [8D]



Yamato hugger -> RE: Leader bug and WitPDecoder (6/14/2007 11:33:22 PM)

From the sounds of it (my un-educated impression) its going to take a data-base change to fix this. Keep in mind, I dont see the code or the files, so Im as in the dark on this as the rest of you, but sounds like a flag needs to be put in the leader file and when he is used / dead, the flag needs to be tripped and every place in the code that it assigns a new leader it needs to check this flag. At least thats what it sounds like to me.



Cpt Sherwood -> RE: Leader bug and WitPDecoder (6/15/2007 2:27:29 AM)

I believe you are on to something Yamato hugger. One thing to note is that most of the commanders I have changed by a large margin have been sub commanders. I think it is interesting that most of the leaders available to choose are commanding subs. I will be off doing more testing to see what I find.



rtrapasso -> RE: Leader bug and WitPDecoder (6/15/2007 6:12:55 AM)

OK - i can get the results you speak of, but i am wondering if when the turn is run that the cloned leaders are cleaned up...

Anyway, i have forwarded it to the programmers.



Cap Mandrake -> RE: Leader bug and WitPDecoder (6/22/2007 6:59:07 PM)

It is a secret US Army Medical Corps experiment.



rtrapasso -> RE: Leader bug and WitPDecoder (6/22/2007 7:07:04 PM)

quote:

ORIGINAL: Cap Mandrake

It is a secret US Army Medical Corps experiment.


So secret, it has only been revealed in your AAR... [;)]



saj42 -> RE: Leader bug and WitPDecoder (6/22/2007 10:04:58 PM)

I have the same issue. I changed some Sub commanders and Soviet LCU leaders. Now I've got Woos' Utility I see lots of duplicated leaders.
See below....(pls excuse quality)

[image]local://upfiles/16324/E361311124E84C0DB5077B03190B04B7.gif[/image]

EDIT:
BigB scen 192 (v1.31) date July 42



rtrapasso -> RE: Leader bug and WitPDecoder (6/23/2007 12:10:39 AM)

Already in the hands of the debuggers... [8D]



Woos -> RE: Leader bug and WitPDecoder (6/24/2007 3:59:39 PM)

@tallyho

Note that the "leader leads more than one leadable unit" inconsistency is not per se a problem. It even allows you to make more use of your better leaders ;-) witpDecoder mainly displays it because it is the precursor to the "no leader" inconsistency but that is shown seperately by witpDecoder. So I wouldn't get too much gray hair (or whatever a fitting English idiom is) over the long list of duplicate assigments.



saj42 -> RE: Leader bug and WitPDecoder (6/24/2007 5:08:24 PM)

'get grey hair' is correct idiom [;)]

I'm not worrying. If the game lets me do it then i will live with it, but not exploit it deliberately.
If I have a worry it's will my 2 clones disappear when the real Kelly T (US Navy) dies [:(]
Hmmm now I think about it which Kelly T is the real one anyway [:D]



Cpt Sherwood -> RE: Leader bug and WitPDecoder (7/16/2007 3:45:25 AM)

rtrapasso, I wondering if anything has come of this? It is not a real game stopper, but I am sure it will lead to problems down the road when one of the units is sunk, or destroyed.



rtrapasso -> RE: Leader bug and WitPDecoder (7/16/2007 7:34:37 AM)

i am pretty sure it will be fixed soon... [8D]



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
2.21875