Meant to say, I think this is really apparent when you add a TextComponent as a child entity to the camera: The text on the left is a TextComponent, the text on the right is an extruded 3D mesh.

Seeing the same thing, I think the math calculating the dynamic size doesn't work correctly on iOS/macOS/tvOS. Also, the documentation could explicitly state that the size of the attributed string is ignored, since that seems to be the current behavior. Having so many knobs to tweak, some of which are ignored, makes it confusing why the text isn't appearing when you first use the API.

This is all still not working, or at least has occlusion issues and transparency issues making it unusable as of iOS/macOS 26. Can LowLevelTexture be used somehow to circumvent these issues? Seems like it should be a basic thing to just load a texture onto a plane so one has sprites.

I'm seeing this as well on the macOS 13 beta. It's making it so I can't style the selection color of a NavigationList sidebar.

Can anyone show an example of how this works? The WWDC sessions doesn't show the code, and I can't get the Variation Attributes I'm adding to a system font to do anything.

I've thought this is weird too. The documentation for the origin is pretty cryptic, but the way it shrinks/scales definitely doesn't seem right. Also, just a heads up, the GKVoronoiNoiseSource seed doesn't do anything and is broken.