Patch 06 - Public Beta - Build 1108r9 updated 21 January 2012 (2nd part)

[bk19@mweb.co.za]

ORIGINAL: michaelm

Checking with the editor, it is a blank device in the scenario. Nothing to do with code.

Suggest adding it to the Land OOB forum.

ORIGINAL: btbw

http://img600.imageshack.us/img600/7379 ... ot221a.jpg
Scenario 6


http://www.mediafire.com/?krwc1dbaqyyl62x

oops.... maybe I should have read everything first before I commented.....

[koniu]

My windows installation is so old that when i am try to launch latest r9 official patch, installer crashes and windows stop responding.

I know i need to reinstall windows but for next days i will have no time to do that.
I have already r9 beta installed.

I have question.

Do r9 beta=r9 official, and if yes, can i use it in PBEM if my opponent will have official patch or we both need stay with beta until i fix my system?

[michaelm75au]

ORIGINAL: inqistor

I vaguely recall some similar issue being reported earlier, but can not find it. Latest beta.


Sorting Ground Reinforcements by arrival date, when restriction level is applied shows realy strange results.
But when no filter is applied it works as it should.

It behaves the same for both sides.

The filter is only acting as a filter for what is being shown from the full list. Whereas the date sort is actually sorting the full list.

The filter needs to be moved so that it filters the full list (that is the 'full' list is only the LCUs that satisfy the filter). Then the sort will work properly.

This also applies to the Ground Withdraw list sorted by date, but so much as most units are already on the map.

[littleike]

Last official patch.

As soon as i start scenario 9 the program create in the save directory an update report with many rows like this:

TOE difference in unit 5th Ind.(3068)
--> slot 4 has (0), to become Type 1 Halftack(788)
TOE difference in unit 40th(3271)
--> slot 3 has 37mm Type 94 AT Gun(734), to become 37mm Type 01 AT Gun(735)
TOE difference in unit 20th(3326)
--> slot 0 has IJA Engineer Squad(711), to become IJA Engineer Squad(267)

...........and so on.


What does it mean? Are they errors?

Many thanks

[michaelm75au]

There are possible data issues with the scenario. They might not be errors, but things that could be wrong.
From a player perspective, I don't think you need to worry. The scenario dev would have sorted out any real errors.

The update file is of more use when you do an in-game update of the scenario data in case it has been changed.

[koniu]

Do message about Burma road status in Rangoon city window is removed?
I just upgraded to r9 and massage disrepair.
I playing as japan and in last turn road was open and now there is no message.

[BigDuke66]

Not sure what this is but I looked into the "aoperationsreport_420214.txt" and found this:
***
Previous report of sinking of CL Kiso incorrect. Ship sighted and engaged at 106, 63
***
In-game that ship is now(turn 74/18th February) listed as sunk on 14th February but the tracker lists it as been sunk on 31st January.
Digging into the Combat report I found that it was bombed on 29th January at 155,94 taking 1 bomb hit and being on fire.
I loaded the autosave from 13th February and there the game also list it as being sunk on 31st January with the exact same data as what the tracker lists.

So the message in the OpsReport just changed the date(from 31st January to 14th February) and the location(from 147, 100 near Wake Island to 105,60 near Kochi) but that the sinking was wrongly reported seems to be ignored also the device(1000lb GP Bomb) is still the same.

Only explanation to me is that the SS Trout sighted the CL Kiso on 14th February:
***
Submarine attack near Kochi at 106,63

Japanese Ships
CL Kiso

Allied Ships
SS Trout



CL Kiso is sighted by SS Trout
SS Trout launches 4 torpedoes at CL Kiso
***
So what happened, did the Captain of the Trout reported the CL Kiso as sunk(again)?

[Don Bowen]

ORIGINAL: BigDuke66
Previous report of sinking of CL Kiso incorrect.

Yup. One of your subordinates fed you an incorrect action report. Such reports do happen. In time they are corrected, one method or another.

[BigDuke66]

Sure and that's OK but what I don't get is why it's still being listed as sunk.
Does the paperwork take so long or is something "jammed"?

[michaelm75au]

ORIGINAL: koniu

Do message about Burma road status in Rangoon city window is removed?
I just upgraded to r9 and massage disrepair.
I playing as japan and in last turn road was open and now there is no message.

The road being open would only apply to the Allied player. And no it hasn't been removed in r9.

[koniu]

ORIGINAL: michaelm

ORIGINAL: koniu

Do message about Burma road status in Rangoon city window is removed?
I just upgraded to r9 and massage disrepair.
I playing as japan and in last turn road was open and now there is no message.

The road being open would only apply to the Allied player. And no it hasn't been removed in r9.

So why i saw that massage at lest for 3 turns in Rangoon if i am Japanese player.
And if massage is gone is that mean that road is closed?

Also if i load new game as allies there is no massage about road. But i only check it on turn "0" so probably i will see it in next turn?

[michaelm75au]

I mean that the impact of the 'road' is only for the Allied player.

Looking at the code:
If the end of the 'road' (Yunan) is occupied by Japanese, then the road is closed and not reported.
Otherwise it is only reported if it can trace a supply route to the 'end of the road'. And supply can be delivered to the base.

On turn 0, no supply has been delivered so the 'road' isn't open.

[Don Bowen]

ORIGINAL: BigDuke66

Sure and that's OK but what I don't get is why it's still being listed as sunk.
Does the paperwork take so long or is something "jammed"?

There is a random time delay before correction (unless the ship is sighted first). If you don't like this, turn off fog of war.

[BigDuke66]

But the ship was sighted that's the point.
Listed first as sunk on 31st January, then it was sighted again on 14th February in a sub attack but without taking any hits, now its still listed as sunk but dated on 14th February and location changed to a point close to the sub attack.

[Don Bowen]

ORIGINAL: BigDuke66

But the ship was sighted that's the point.
Listed first as sunk on 31st January, then it was sighted again on 14th February in a sub attack but without taking any hits, now its still listed as sunk but dated on 14th February and location changed to a point close to the sub attack.

I really do not understand the confusion.

You received an incorrect sinking report (fog of war).
You later enaged the ship reported as sunk so you know the report was false.
When engaged it was again reported as sunk (may fog of war, maybe not).

[m10bob]

How many times was Enterprise reported sunk?

[BigDuke66]

ORIGINAL: Don Bowen

ORIGINAL: BigDuke66

But the ship was sighted that's the point.
Listed first as sunk on 31st January, then it was sighted again on 14th February in a sub attack but without taking any hits, now its still listed as sunk but dated on 14th February and location changed to a point close to the sub attack.

I really do not understand the confusion.

You received an incorrect sinking report (fog of war).
You later enaged the ship reported as sunk so you know the report was false.
When engaged it was again reported as sunk (may fog of war, maybe not).

Confusing is whether he really reported the ship as sunk or if the sunk ship list didn't update the info correctly, I mean in the combat report he didn't even score a hit on it and it wasn't listed as sunk either in that report so how can he report it as sunk?
If only he scored at least one hit it would be understandable but the way it is now seems strange.

Simple calculation:
Reported sunk + sighted later + attacked without scoring a hit = SHIP NOT SUNK
That's what I can get out of the reports I got and I don't get how the game can pull something different out of them without giving the player a clue where that info comes from.
Any even the silliest explanation in that combat report would have solved why the ship is still listed as sunk, simply because it was reported as sunk or at least as hit.
If I get one report of a pilot telling me he hit the CL with his 1000lb bomb and is sure it sank later = Ship sunk
If I get one report of a captain telling me he attacked that ship but without hitting it = Ship not sunk
I can either believe the pilot or the captain but can't "merge" the two reports to make something out of it that doesn't make any sense like it's now with changing date & location but not the sunk by reason or that it's sunk at all.

[Don Bowen]

It's just getting too complicated. It's bloody Fog of War, it's supposed to be wrong sometimes.

[denisonh]

It is an abstraction of what happened in RL.

In the pre information age, stubby pencil, world where hundreds of operational reports are transmitted through multiple HQs across the Pacific then are sorted through and analyzed by hand, the chances of getting accurate and timely information is not as good as you think.

As a guy who had to pour through literally millions (yes, millions) of operational reports while doing analysis of operations in Iraq, it was not always easy determining what actually happened in engagements at HQ level. Operational reports varied, with some being incomplete, some describing the same event in a different way (conflicting at times), some with the data being incorrect (remember geocoding one engagement based on the coordinates and it was in Iran), and a whole host of blanks/incompletes in the reports. Even today it isn't easy.

ORIGINAL: BigDuke66

ORIGINAL: Don Bowen

ORIGINAL: BigDuke66

But the ship was sighted that's the point.
Listed first as sunk on 31st January, then it was sighted again on 14th February in a sub attack but without taking any hits, now its still listed as sunk but dated on 14th February and location changed to a point close to the sub attack.

I really do not understand the confusion.

You received an incorrect sinking report (fog of war).
You later enaged the ship reported as sunk so you know the report was false.
When engaged it was again reported as sunk (may fog of war, maybe not).

Confusing is whether he really reported the ship as sunk or if the sunk ship list didn't update the info correctly, I mean in the combat report he didn't even score a hit on it and it wasn't listed as sunk either in that report so how can he report it as sunk?
If only he scored at least one hit it would be understandable but the way it is now seems strange.

Simple calculation:
Reported sunk + sighted later + attacked without scoring a hit = SHIP NOT SUNK
That's what I can get out of the reports I got and I don't get how the game can pull something different out of them without giving the player a clue where that info comes from.
Any even the silliest explanation in that combat report would have solved why the ship is still listed as sunk, simply because it was reported as sunk or at least as hit.
If I get one report of a pilot telling me he hit the CL with his 1000lb bomb and is sure it sank later = Ship sunk
If I get one report of a captain telling me he attacked that ship but without hitting it = Ship not sunk
I can either believe the pilot or the captain but can't "merge" the two reports to make something out of it that doesn't make any sense like it's now with changing date & location but not the sunk by reason or that it's sunk at all.

[Chris21wen]

On the TF creation screen there is a button that says 'Surpress ships not due upgradel'. This filter does not seem to do anything usefull? And yes I do have ships both due and set for upgrade but clicking the button removes all ships in port.

To my mind this filter is wrong anyway you should be surpressing ships due an upgrade thus hiding them from selection.

Right clicking on a ship during the select is no use either as this info does not appear on the ship data.