Units displayed incorrectly after transport

[Courtenay]

Sometimes when a unit is moved by naval transport, it seems to be in its original location. Every time this has happened to me, if I continue the game the unit eventually shows up in the right location, but in the meantime it can be pretty confusing. I present the following picture as an example:

Here, kitty, kitty, kitty....

Where is the Kittyhawk? It started the impulse in Cardiff. The CW loaded it onto a TRS and transported it to Cape St. Vincent. As you can see, the flyout says that that is where it is, as it should be. However, the Unit Review form shows it still in Cardiff, and if one looks at Cardiff, one sees the unit is displayed as still being there. It is not selectable, so it is not really still there, but something went wrong.

This is a very low priority bug, but at some point it would be nice if it were dealt with.

The next file is the position at the start of the naval phase, so that the unit's move can be duplicated, followed by a post of the save game after the move.

[Courtenay]

Position at start of the naval move, with Kittyhawk and TRS in Cardiff.

[Courtenay]

And here is a saved game from after the Kittyhawk was moved:

[Courtenay]

The bug is worse than I thought. When I move on to the next phase, I find that the Kittyhawk is still in Cardiff, not off Gibraltar, like I assumed it was.

[Courtenay]

Here is another example of the same bug. I thought I transported the Canadian INF to Cape St Vincent, but the unit shows up in both Halifax and Cape St. Vincent. Same naval movement phase, same start of naval movement phase. I do not remember seeing this bug before, but it is now happening on a fairly high percentage of my naval transports. It is a very nasty bug, because it looks like the unit was transported properly, but it actually stays behind. Since I am of the opinion that the most important units the western Allies have are their TRSs, this is critical. I have had to go back and redo the whole Allied turn because I found no less than three of my transports had failed to transport the units they said they had, and now I am finding that errors are occurring in my redo.

[Courtenay]

And here is the saved game from after the Canadian INF was allegedly transported.

[Centuur]

It's already on the list for fixing with the other naval bugs.

[AxelNL]

Is this problem already seen somewhere else? This is the game where I used the debugtool to move peacekeepers out of persia. I hope this is a real bug, because the other explanation is that the debugtool is the cause of this.
This needs carefull analysis.
If it is a bug it probably needs quicker fixing than waiting for the naval release.

[Courtenay]

That is an excellent question. It may be that your moving the division affected things. I may have had the bug before, but if so, I did not notice it. Now I would say it is affecting about 20-25% of my naval transport attempts. I can't imagine why moving one unit would affect things, but computers are strange. I have had naval transport attempts fail in the past, but I just assumed that was me mismousing. Now it is definitely a bug, and a very frustrating one at that.

[AxelNL]

ORIGINAL: Courtenay

That is an excellent question. It may be that your moving the division affected things. I may have had the bug before, but if so, I did not notice it. Now I would say it is affecting about 20-25% of my naval transport attempts. I can't imagine why moving one unit would affect things, but computers are strange. I have had naval transport attempts fail in the past, but I just assumed that was me mismousing. Now it is definitely a bug, and a very frustrating one at that.

Naval transports go wrong when mismousing. Cancelling during the loading, or switching or misclicking can have really strange results. Also splitting of naval units with TRS after sub interception attempts can go wrong. I have had a situation where a land unit was in a sea area without its TRS and still could invade. If I didn't invade it jumped back to its TRS in a later phase.

All to be targetted after the coming production fix. But I will vote yours to be fixed earlier.

[AxelNL]

ORIGINAL: Courtenay

Position at start of the naval move, with Kittyhawk and TRS in Cardiff.

Loaded your game. When I do not mismouse there is no problem.
However, when I purposefully mismouse I can get it to crash. I clicked multiple times on both Aircraft in the loading form, as if I was undecided. I rightclicked on Kitty telling it to fly by night and loaded it. After that the Fly-out box showed only 2 units and an empty space. When picking up the TRS the game crashed so awfully MacExcept gave up and Microsoft wanted to be told about it. So don't do this at home, only for amusement purposes.

[AxelNL]

ORIGINAL: Courtenay

And here is a saved game from after the Kittyhawk was moved:

Yep - loads as described. Good evidence.

I am pretty sure it is the problem I have mentioned before in the tech forum. When using the Loading form be very audacious in what you do, otherwise you have chance this will happen. I don't think my debugtool intervention has something to do with this.

If you still have problems even when being audacious this needs quicker fixing that waiting for the naval release.

[AxelNL]

ORIGINAL: Courtenay

And here is the saved game from after the Canadian INF was allegedly transported.

Yep - same problem. You can tell by the Fly-out box on Halifax showing only 4 of the 5 units, but reserving an empty space for the inf corps.

As you could only have selected the Corps in the loading form, I can only conclude it would have been very difficult to mismouse here. This means that the appearance of this bug has become worse lately. As transporting is so vital in this game this becomes in my eyes a bug which needs to be higher on the list to fix.

[Courtenay]

A unit that is failing 100% of the time is far more useful for debugging than an intermittent failure, so I will post one more file.

Every time I tried to move the MAR ENG XX in San Diego, it failed. I selected the Nashville using either the flyout or the naval review details form, right clicked on it, loaded the ENG, and sailed into Hawaii. The ENG would be displayed in Hawaii, but the Unit review form indicated that it was still in Hawaii.

I was about to give up in frustration, when I tried selecting the Nashville using the select units form. I did the same steps, and this worked.

In the attached saved game, try moving the MAR ENG in San Diego to Hawaii on the Nashville by various methods, and use the Unit Review form to see where it ends up. To repeat, when I selected the Nashville using the flyout or the Naval Details form, the ENG was not transported, although it appeared to be. Selecting the Nashville using the select unit form (cntl-click) worked.

This bug has caused me to waste a lot of time on my latest move. (I have had to redo the Allied naval move completely, and had to restart it several times.)

[AxelNL]

Excellent!

[Centuur]

ORIGINAL: AxelNL

ORIGINAL: Courtenay

That is an excellent question. It may be that your moving the division affected things. I may have had the bug before, but if so, I did not notice it. Now I would say it is affecting about 20-25% of my naval transport attempts. I can't imagine why moving one unit would affect things, but computers are strange. I have had naval transport attempts fail in the past, but I just assumed that was me mismousing. Now it is definitely a bug, and a very frustrating one at that.

Naval transports go wrong when mismousing. Cancelling during the loading, or switching or misclicking can have really strange results. Also splitting of naval units with TRS after sub interception attempts can go wrong. I have had a situation where a land unit was in a sea area without its TRS and still could invade. If I didn't invade it jumped back to its TRS in a later phase.

All to be targetted after the coming production fix. But I will vote yours to be fixed earlier.

That's why I said it was a known bug...

[AxelNL]

ORIGINAL: Centuur

ORIGINAL: AxelNL

ORIGINAL: Courtenay

That is an excellent question. It may be that your moving the division affected things. I may have had the bug before, but if so, I did not notice it. Now I would say it is affecting about 20-25% of my naval transport attempts. I can't imagine why moving one unit would affect things, but computers are strange. I have had naval transport attempts fail in the past, but I just assumed that was me mismousing. Now it is definitely a bug, and a very frustrating one at that.

Naval transports go wrong when mismousing. Cancelling during the loading, or switching or misclicking can have really strange results. Also splitting of naval units with TRS after sub interception attempts can go wrong. I have had a situation where a land unit was in a sea area without its TRS and still could invade. If I didn't invade it jumped back to its TRS in a later phase.

All to be targetted after the coming production fix. But I will vote yours to be fixed earlier.

That's why I said it was a known bug...

I understand, however it looks like this bug has become more dominant, and could do with an higher prio. Or the mouse of Courtenay has started to malfunction - that could also be a distant explanation. This bug could always be mitigated by not doing anything else but the bare minimum in the loading form, the behaviour Courtenay reports is giving a different message.