It a very simple feature, posted in 2020, and still not available. We are paying adobe to get ignored. Figma is much better.

I intuitively used it before finded it didn't work. Please add this feature.

as a user, i would like the ability to add nested interaction to components, including allowing 3d transformation between states

Please , without this functionality this feature remains unfinished and pointless

Seriously, I don't understand why this feature was implemented without component states in mind in the first place? I want to have this 3D transform on hover or click/tap, something that is so common in an app or on websites.

Wanted to use it for the 1st time on a webpage design with 5 cards that need to flip on press/tab... So I guess I have to copy my artboard for each card to make this work?!

Most definitely that would be an amazing feature to have. Creating, let's say, flip card that is animated between two artboards is great, but it requires some visual feedback hint. That would be the hover state. In that case, when user hovers the mouse over the element it could let's say move by 5pts on Y axis (slightly tilt in space) indicating that there is something on the other side and when clicked, the element will flip 180 degrees. Not having to animate that between the two artboards would save so much time and work.

Allowing 3D transform inside a component or group will make more movement in graphics and even in prototype animation like flipping when mouse is hover and etc.

YES PLEASE. The 3D transform tools would be so helpful for hover states. I've been trying to find a decent solution to scale a component on hover, but unfortunately there is no solution besides manually resizing everything including fonts.

The following link shows an excellent example of why we need 3D Transformations to be State enabled: https://designwoop.com/css-3d-animation

This feature is a great example of MVP. As thrilling as the 3D transforms are, they reside well within the "minimum" of Minimum Viable Product.

I would be shocked to find that anyone who tried to use 3D transformations in this first iteration didn't attempt to make the transformation a State in 5 minutes or less.

I'm a UX designer, so I fully recognize when a design/dev team anticipates extended use of a feature but the demands of any given release cycle dictate that it ‘go out without’ until a proven need is determined. This is an excellent practice in most circumstances. But when a use case is as obvious as this one, it's hard to justify putting out 3D transformations as a feature that is entirely divorced from the existing States functionality.

Unfortunately, one would predict that the net result will be hundreds or thousands of Adobe XD users who will become very excited and then almost instantly very disappointed within a matter of.

Note:
This request is also mentioned in another request.

https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/41825794-3d-transform-as-a-component-state

Let's get these together to pool the votes.

This is covered in another request. Let's get them together to pool votes.
https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/41694019-allow-3d-transformations-in-states

Yes, please. Being able to set different 3d transform values in a hover state vs the default state for something like a button would be awesome.

Please, support the 3D transformation as a component status. Thus, we can animate a single component within a single artboard.