Bug "estimated" time of building bridge

[DIVM]

Hi,

I wasn't sure where to post this, so I'm guessing here at Tech Support? Please do let me know or move the post if it should be under a different thread.

While replaying the Tutorial "Engineering Operations", I realized that when chaining a "build brigde" order behind a "move" order will have a small bug:

Screenshot (4376).png (1.17 MiB) Viewed 270 times

Firstly at 7:15, I send it an order to Move down and the arrival order as "build a bridge", it will give a time (8:04) of finishing building the bridge. This will be the correct time.

Screenshot (4377).png (1.06 MiB) Viewed 270 times

Once it arrives (during the turn resolution at 7:43), the estimated finish time for the bridge as changed in the Unit log, Engineering tab and on the map to 8:16.

Screenshot (4378).png (1.09 MiB) Viewed 270 times

However, we can see that the build was still finished building at the original time of 8:04.

Not sure what's the issue. Is it adding an extra command delay between the two orders by mistake when it arrives when calculating the time? Anyway, hope it helps to fix it, I was experimenting on how to deal with chaining commands with engineering operations and caught that weird behavior.

Cheers.

[MaximKI]

Do you have a save file you can share with us that reproduces the issue?

[WildCatNL]

Thanks for the extensive description. Filed bug report for the team to investigate and fix.

[DIVM]

Do you have a save file you can share with us that reproduces the issue?

Tutorial - Engineer Operations 251125_1054 @ 02_pct__0715_hrs.7z

(430.66 KiB) Downloaded 10 times

I attached it here. Let me know if that works. This is during the turn resolution of 7:15. After two turns 02_AVLB will be in the southwest hex, and you should see how the time estimated finishing time changes to 8:16. If you keep going, the bridge will actually be finished at 8:04.

I tried to replicate the same issue when "removing bridge" (chaining orders instead of awaiting for the unit to be iddle after crossing the bridge); but that worked well.

[WildCatNL]

Thanks again. We've identified the problem. The fix, however, needs quite a bit of testing, may take a while.