You will have to wait until GW4 GW5 are updated to Wear4 see FAQ 12
The Sync to device feature enables your watch face to use the step goal defined by the user on their device’s health application. It is supported on watch devices running API Level 33 and higher (Wear 4 and later).
On Wear 3 devices, because Sync to device is not supported, the step goal is fixed to 6000. If you want to set a different step goal for Wear 3 devices, you must create a separate watch face version for Wear 3, disable Sync to device, and define the step goal directly.
It was not the same with WFS 1.3.13.
From 1.4.20, complication slot bound works somehow like mask element.
Complication Bounding Areas
Complication bounding areas are used to define the rendering area for a Complication. An outline of the bounding area is shown in the watch face editor. Any content outside of the bounding area is cropped.
The bounding area also determines the region where the user can select the complication from the watch face.
My request would be to have the same complication types from the Circle shape, to a rectangular shape.
Because as you can see from my picture, multiple complications will overlap with each other and make clicking on the desired areas and other shortcuts, much more difficult. Because of this issue, it covers the Heart Rate app shortcut that I’ve set, just to make sure the entire complication data fields do not go out of bounds.
Use the Large Box complication for a line progress bar.
I see your issue let me think on it for a bit.
I just remember one other person reported how slot bounds worked so I thought maybe this was to fix that persons report.
If you think it is a bug please report it.
Large Box allows you to put RANGED_VALUE and LONG_TEXT together. That’s great.
But what if I want to make sure that people can choose between SHORT_TEXT complications and RANGED_TEXT, together?
We get a Circle Complication shape and this is where the issue lies.
A circle as a shape mask is ineffective when you want to show data in a straight line, because some elements (Icons, Text, whatever else) will go out of bounds, as you squeeze the circle. This forces the developer to make the circle several times bigger to make sure that everything is shown correctly.
And with this issue, comes with the problem that it also increases the size of the complication area needlessly.
Looks like the LARGE_IMAGE complication type is not part of any of the new complication slots. Could it be added to the Large Box slot with upcoming WFS versions?
What needs to be considered:
LARGE_IMAGE → Large Box
RANGED_VALUE —> Small Box
SHORT_TEXT —> Large Box
LONG_TEXT —> Line