Matrix Games Forums

PBEM version 1.00.01
I am Japan.
Allies attack in their turn. No report of what happened.

I am having similar issues where only the combatants don’t show up. But that’s for naval and during my IJN action.

This is PBEM? It's always you two causing trouble

Right when you see those kind of errors post a log up. That way I can start tracing and try to remember what happened.

Error game logs are here
C:\Users\"your user ID"\AppData\LocalLow\Kraken Studios\WarPlan Pacific\player.log

Alvaro...Here is what happened...

I saw the fleet...moved my carrier fleet next to it and clicked carrier attack...it did nothing...just what you see in that report.
I did this quite a few times...

Restarted the game and same issue.

Tried to ponder what it could be...took the CVs and moved them to port.

WAS able to attack with surface ships.

COULD it be that the ships being attacked were in night mode? Are CVs not able to attack ships in that mode?
I had the same issue by Fiji...surface could attack...CVs could not, but as the other side.

If you have the save can you email it to me? I'll PM you my email.

I will keep monitoring...I did not save it.

I am sure can get it to happen again at some point.

Yes there are night mode problems currently I think. In two different games, carrier fleets STARTING adjacent to a night mode fleet could attack it. But carrier fleets moving into range, even one hex, could not.

I will start saving and saving logs when I see an error. I also did not save the game and I have 4 games going.

Well that gives me a start to go for.

I figured out the error. If you scroll down for a long battle, the scrolled amount is kept in other battles. That means for shorter battles with no scroll bar, the report is cut off.

Thanks. Still doesn't account for the duplicate ones in the same spot.

Looking into this. I can't replicate it. I need to know more details on how it happens.

I have an error log, it is attached.

I believe this had to do with the CV and transport as the defender issue being fixed in the upcoming patch.