Why is Lunga 58 hexes away from a point 2 hexes from Lunga?

[dgaad]

Attempting to bombard lunga with Dive Bombers, I select a ground attack mission as primary and set all dive bombers in hex to that mission (total of 4 carriers). When I do this, the range indicator goes to (2). However, the planes do not attack, there is no cancellation report, and finally on the next turn when looking at the carrier groups, Lunga is still the target but now the range indicator is (58).

Something is wrong.

Anyone else seen this or have problems hitting lunga with carrier air?

[wmtiz]

I have not seen this and I bombed the daylights out of Lunga with a two CV Task Force to soften up the ground forces before landing my invasion units. I launched my strikes from a point 3 hexes away from Lunga directly to the SE in order for the TBDs to be in range.

[Erik Rutins]

Dgaad,

Can you provide me with a zipped save showing the exact location and composition of this strike? Thanks.

Regards,

- Erik

[dgaad]

Erik : yes I saved that game in a special slot in anticipation of your request. Sending now, in zipped form.

[dgaad]

Erik : how and where do I send to you?

[Erik Rutins]

Please send the zipped save to erikr@matrixgames.com along with a brief description (like your first post) for reference. Thanks!

Regards,

- Erik

[dgaad]

Okay done.

[dgaad]

Okay I just loaded up the save I sent to Erik and confirm the following :

1. I have two carrier groups of two carriers each.

2. The carrier groups are in hex : 39,42.

3. Hex 39,42 is 2 hexes from Lunga (38,40).

4. All 8 dive bomber groups are set to ground attack Lunga.

5. All 8 dive bomber groups have a range indicator to Lunga of (58).


FLASH : 3942 minus 3840 is 102. Hex 1,2 is exactly 58 hexes away from the location of the carrier groups. That could be just a random coinkydink.

[dgaad]

Originally posted by dgaad
Okay I just loaded up the save I sent to Erik and confirm the following :

1. I have two carrier groups of two carriers each.

2. The carrier groups are in hex : 39,42.

3. Hex 39,42 is 2 hexes from Lunga (38,40).

4. All 8 dive bomber groups are set to ground attack Lunga.

5. All 8 dive bomber groups have a range indicator to Lunga of (58).


FLASH : 3942 minus 3840 is 102. Hex 1,2 is exactly 58 hexes away from the location of the carrier groups. That could be just a random coinkydink.

At this point if anyone has the ability to deploy carrier groups in this very same hex and set up a ground attack mission against Lunga from that hex, please do so, process the turn, and see what the range indicator says. And then tell us.

For EZ reference, the suspect hex is where the "al" is in the word Guadalcanal on the map, two hexes southeast of Lunga.

[sbattler]

Originally posted by dgaad



At this point if anyone has the ability to deploy carrier groups in this very same hex and set up a ground attack mission against Lunga from that hex, please do so, process the turn, and see what the range indicator says. And then tell us.

For EZ reference, the suspect hex is where the "al" is in the word Guadalcanal on the map, two hexes southeast of Lunga.

-----------------------------------------------------------------------------------

I set up the situation in scenario #1. Sent the Jap 3rd SNLF to Lunga. Got the US Carriers up to the "al." Ordered the ground attack and BINGO! The "range" to target reports 58 hexes. I've saved the file if it's needed just let me know.:

Hmm...

[sbattler]

Originally posted by dgaad



At this point if anyone has the ability to deploy carrier groups in this very same hex and set up a ground attack mission against Lunga from that hex, please do so, process the turn, and see what the range indicator says. And then tell us.

For EZ reference, the suspect hex is where the "al" is in the word Guadalcanal on the map, two hexes southeast of Lunga.

-----------------------------------------------------------------------------------

I set up the situation in scenario #1. Sent the Jap 3rd SNLF to Lunga. Got the US Carriers up to the "al." Ordered the ground attack and BINGO! The "range" to target reports 58 hexes. I've saved the file if it's needed just let me know.:

Hmm...

[dgaad]

Wow, thanks alot sbattler. Now there is further evidence that I am not insane.

[dgaad]

Further update :

Strangely, the carrier TFs I had in the hex had a DESTINATION hex of the hex they were in. As soon as I set a TF to have a destination 1 hex away from their current hext, the distance indicator corrected itself.

[dgaad]

More Updatage :

It seems that whenever the Carrier TFs are actually in their destination hex, the distance indicator reverts to an incorrect assessment (58). I can move my carrier TFs to any location within range of Lunga and still get this incorrect distance indication, but its not always 58, it seems to be a function of the actual distance from Lunga, but its always in the 50s.

Another anomaly, working with 2 carrier groups, if you have the situation where the Carrier TFs are already in the destination hex, and therefore have an anomalous distance indication, if you then set ONLY ONE of the TFs to a new location within range of Lunga, the distance indicators for ALL carrier air groups that have Lunga targetted are corrected.

[dgaad]

Okay I take back what I said earlier : the anomalous range is always 58.

from 39,43 the range to lunga is 58

from 40,44 the range is also 58.

Also, in the anomalous condition, the dive bomber groups do not execute an attack. I've been sailing back and forth for days with clear weather, moving the TF 1 or 2 hexes each day, no attack ever takes place.

[dgaad]

Final Update :

Instead of setting the bomber groups to ground attack Lunga, I set them to ground attack commander's discretion. The attacks have started to pour in. Hope this helps.

[dgaad]

Okay I am now noticing the range problem with other hexes when attempting to hit with carrier groups. I currently have a carrier group in the Lae hex, which has a secondary ground attack mission to Lae for all Dauntless airgroups, all airgroups but one is listing Lae as 33 hexes away.

Matrix, what is up with this bug and is it going to be fixed in the next patch?