RHS Lvl 7, Scen 70 RHSCVO 7.76 problem

[Fletcher]

Hi
I am playing a PBEM RHS Lvl 7, Scen 70 (CVO)last upgrade (7.76).
After the first historical turn, when I create a new IJN TFs at Tokyo I have no problems, but when I create a second then the first one dissapears and so on.
The ships dissapears from the ship list too !.
Thanks in advance for any help about.
Cheers !

[m10bob]

THAT would suck!

[el cid again]

This isn't happening at source. While it might be corrupted RHS data files, it is hard to imagine how? It is more likely a problem with the WITP installation itself - or possibly a bigger problem on the station.

The solution is to "put a box around the problem." Determine if it occurs in other scenarios of RHS, in other mods (CHS), or in stock? If yes - it is not the data files of that scenario - it is fundamental to the WITP program installation or to the workstation. Determine if it happens on another computer? If not, that tends to point at the installation or the machine.

If you can show that there are no issues with the workstation or the WITP installation (they run stock properly say)

then IF you can show it only happens in this one scenario - reinstall the scenario files

OR IF you can show it only happens in RHS - try a new download (and a newer version is releasing momentarily - x.761 - with data bugs removed at least - but not this one - because we don't see it)

If you can not make stock work - reinstall WITP on a clean foundation

It that does not work, you have a fundamental workstation issue - probably operating system or hostile software

[Fletcher]

ORIGINAL: el cid again

This isn't happening at source. While it might be corrupted RHS data files, it is hard to imagine how? It is more likely a problem with the WITP installation itself - or possibly a bigger problem on the station.

The solution is to "put a box around the problem." Determine if it occurs in other scenarios of RHS, in other mods (CHS), or in stock? If yes - it is not the data files of that scenario - it is fundamental to the WITP program installation or to the workstation. Determine if it happens on another computer? If not, that tends to point at the installation or the machine.

If you can show that there are no issues with the workstation or the WITP installation (they run stock properly say)

then IF you can show it only happens in this one scenario - reinstall the scenario files

OR IF you can show it only happens in RHS - try a new download (and a newer version is releasing momentarily - x.761 - with data bugs removed at least - but not this one - because we don't see it)

If you can not make stock work - reinstall WITP on a clean foundation

It that does not work, you have a fundamental workstation issue - probably operating system or hostile software

I followed all your instructions about this problem, but the problem persist...no only in my workstation, then in another PCs.. I tried to reinstall RHS from the beginning, in all computers, but the problem persist... When I am creating the 11th (no problem with first to tenth TF newly created) at Tokyo, then the 10th disapears and so on (the ships from the disappearing TF dissapears too from the ship list !!)...I have not problem with stock or CHS in the sames PC. It must be another problem not from PC or RHS install. I need help, thanks in advance !

Cheers

IMPORTANT: This problem only in a PBEM play, not in a single play or face to face !

[witpqs]

Maybe see if the moderators can duplicate the problem? This should be a high priority fix if they can.

[Fletcher]

the only way to see the problem is beginning a PBEM game, after put into your password then try it...you can see probably at Tokyo when you create more than ten task forces, the previous after 10th dissapears and the ships from the map and the ship from the ship list too (the another nine task forces and the new -the eleventh- not dissapears, but if you will create a new one, then the previous will dissapear with the ships !).
Thanks !

[el cid again]

Well - this is not what you seemed to be saying up front. This is a known - and we thought fixed - problem. It derives from the location file - the values assigned to task forces.

I do not see the problem at source because I am not trying to create more than ten task forces at Tokyo - a bad idea IMHO - but I hate to prevent players from shooting themselves in the foot! [You can hardly do this in a sense a real navy person would like - with proper escorts] Now I know what you are doing - I can see if it can be duplicated. If it can, I can then mess with task force assignments (something I HATE to do because there are something like a thousand ships - and the editors won't move them - and I support 14 or 21 scenarios! - depending on wether I change Level 6] - every field that is wrong must be changed that many times. So I hope this is not an issue - and if it is I might just give notice and say "don't do 11 TFs at Tokyo" - but it may well be this problem is bigger than that.

[el cid again]

Looks like slots 3501 to 3541 are used in stock, CHS and RHS - inclusive - no holes - in CVO and BBO sets.

In EOS 3509, 3511 and 3519 are empty.

In all three, 3542 is empty - and slots are intermittantly used above that.

Since you are playing CVO, and since it is the SAME as stock and CHS in regard TF slots 3501 to 3541 - this is not related to the TF slot issue reported and corrected at some point.

The problem arose because RHS had TFs that didn't start the game. This would cause "knocking out" of task forces like you describe - but it is not the same problem.

I have to see if I can cause the symptom to occur? If so - I might be able to figure it out. This is what I do - if we can pinpoint an issue I "put a box around it" and try things until it goes away - or we refer it to programmers for hard code changes.

[Fletcher]

El cid again, excuse me again, but I tried all... a new install, another PC but the problem persist !... but ONLY in PBEM mode, I had no problem with face to face or human vs AI, only in PBEM !!.
I have two other folders with stock and CHS and I had not any problem like this ever !
Cheers and thanks in advance !

[el cid again]

I have checked - there is a limit on TFs which may form - but it is no where near 10. It is probably close to 250 - maybe 248 or 254 - all values you see in WITP coding of various things. And that is for EACH side.

I am not seeing this problem.

Try a clean install in its own folder - run stock - do the same thing: DOES this happen then?

Reinstall CHS on top of that - do the same thing. DOES this happen then?

Reinstall RHS on top of that - do the same thing. DOES this happen then.

That way we will know if it is structural - inherited - or new to RHS.

I did check the TF structure - in CVO RHS uses the same structure as stock and CHS - and I do not see the problem. SOMETHING is probably different in your install from mine. Otherwise we all have this problem - always did - and we never noticed because most of us do not create so many TFs at one time.

[Fletcher]

Thanks for your quick answer... I will try to follow all your instructions about to close to the problem.. When i test all options I will post about it.
I am trying at all cost to solve this problem, I am enthusiastic RHS fanboy, and I will like to play this amazing mod.
Best wishes

[el cid again]

Fletch reports this is ONLY a PBEM issue - and I do not test in PBEM mode. So I will do that.

[el cid again]

If there is even one problem with ANY cam file for any RHS scenario - I will recreate them all. This is not hard to do. At one time we had evidence of CAM file corruption. I used older files. This time I will start with stock and modify them. But I do not yet know if there is a problem? I have never seen this problem.

[el cid again]

I have been able to duplicate the problem. It appears to be a nice solid problem. It further appears not to exist in stock. This is a good sign. It should be possible to determine the file and recreate one that works. If we are lucky this is a cam file issue. If we are lucky it only affects CVO.

[Fletcher]

Good news ! .. But try with Scen 73, I remember that I had the same problem with it !. Thanks for news!

[el cid again]

OK - now I recreated all the cam files - I am able to show they are NOT the problem.
It is not a bad thing to get closer to stock in a file though - so I am content.

I went back and tested more scenarios and found it is present in the five strictly historical ones - but not EOS or AIO.
I found it was always TF 83 that duplicated.

And lo - in those five (ONLY) TF 83 is 9999 ed out.

Take it out - problem is gone.

This will be part of x.77 update.

If you want to fix your own file - delete record 3583 of the location file in any scenario CVO, RAO, BBO, RPO or PPO at any level.

[Fletcher]

That´s great !... I will wait the 7.77 update. Thanks a lot for your time, your knowledge and your patiente.

[el cid again]

The fix for this issue is contained in x.77 files. Note it never was an issue in EOS or AIO.