Hubert - difference between v1.16.03 and v1.17.00 (assault transports)

[mroyer]

Hubert (and Bill),

I know you gave me the early beta of v1.17.00 for a very specific purpose, but I couldn't resist trying it more broadly.
Generally, it is working very well and has some nice updates.

However, I notice one very significant "issue" (not sure if it's intended or a bug or what), at least for my mod-campaign.

In my campaign, Bellum Galaxia, The Terran Empire uses Titania and Oberon Stations (Moons of Uranus) as launching points for an interstellar invasion fleet. In v1.16.03 the ground elements (which have just appeared through unit.txt scripting) can board long-range assault transports (see the figure). But following the same, exact sequence (down to the click) in v1.17.00 the long-range assault transports are greyed out.

Is this intentional? If so, is there something I need to do in my campaign to again enable them?

Thanks for any thoughts and help,
-Mark R.

[mroyer]

I also notice the forced march is greyed out in v1.17.00.
Perhaps it's related to the 'just-arrived' status of the forces?

-Mark R.

[mroyer]

More info that might explain it.
In v1.17.00 if I move forward to the next Terran Empire turn, the assault transports become available (un-greyed out).
Is that intended, that newly arrived units can't immediately go on an amphibious assault (to put it in WW2 terms)?

I think that is okay for my campaign - it'll just delay the Terran mission by a turn which actually might be good. Gives Beta Hydri an additional turn to prepare. I'll have to try it.

-Mark R.

[Hubert Cater]

Hi Mark,

I believe that is the answer, a unit simply needs action points to do much if not all of the actions that are greyed out in the right side image.

Hope that helps!
Hubert

[mroyer]

I believe that is the answer, a unit simply needs action points to do much if not all of the actions that are greyed out in the right side image.

Okay, I think that's good - probably better than being immediately available.

At first I thought it might be a symptom of some as-yet undiscovered bug with v1.17.00 so I wanted to get it reported.

Thanks Hubert,
-Mark R.