Ok...
Most of the triangle shapes in fonts on a Mac are actually from the Unicode character set. Macs have an "interesting" way of handling characters, specifically, if a character is "missing" in one font (and depending if there has *never* been an allocation or edit of that character space), the Mac OS will attempt to identify the type of font (serif, sans-serif, script, etc.) and provide that missing character from a *substitute* font. This is why emojis and other types of characters are available in just about *every* font you can use. I can go into the Character viewer and apply this character: ⬛︎ to any font on the system.
The point is: you don't really know which font that character comes from except that it is one of the fonts that carry an extended support for the unicode character set. Wingdings does account for extended unicode support, but if the font you're injecting the square into is Times, then you don't know which font is used...
And that's the problem: the characters (shapes or otherwise) are created to be able to fit into a standard character set when applied (or typed). They have a character width, and *ascent* and *descent* heights. Character widths have nothing to do with the actual shapes of a character, they are a starting point and ending point for a cursor placement and the shape is put in there in some arrangement to make it look like it will fit in evenly into that visual space. Most "shapes* are *above* the baseline (the shape's center is somewhere in the "ascent" part of the character.)
My criticism of most of the shape characters in unicode is: very few of them have paid any particular attention to exactness. Square shapes throughout are all likely to be rectangles instead. Triangles will have the horizontal line shorter or longer than its sides. Shapes are not perfectly centered in their character spaces making shape centering more difficult in Motion (at least Motion provides a *perfect* bounding box around 3D text shapes.)
As a final comment on shapes in fonts: leading (the space under the character which is actually part of the "font"), and how much space was allocated at the ascent and descent sides will also be an issue. Most fonts allow just enough descent for descenders like lowercase 'g', etc... A precise font will have the shapes fully occupy the ascent and descent (which will also be equal distances from the baseline.) When a shape fully occupies the ascent/descent, in a 1080 project, a font of size 1080 will perfectly fit the canvas in Motion -- see where I'm going with that??
Some care was taken with this font:
https://fcpxtemplates.com/motion-shapes-font/
to make sure that the shapes are "pure", the sidebearings are equal, and the center points are on the character's baseline. Set the text alignment to Center and the center points of the shapes should be near perfect (I have since discovered a better way... but these shapes will do plus there a few easter eggs in the mix. [BTW, I no longer create any shapes in the A-Za-z character space as you will see with the Font name in the menu list when installed. Don't mind it too much, it doesn't hurt anything!)
All of that brings me finally to creating the tetrahedron...
Working with 3D Text for 3D modelling is not entirely like other things in Motion. The parameter values are all capable of extremes and sometimes you will need to "go there".
When working in 3D (modelling), you will want to generally make the shapes large enough to fill the canvas — at least large enough to be able to see details. 288 is way too small. Start around 750 or so.
If you're using Motion Shapes, the triangle is the number 3.
The first way to make a 3D pyramid is by eyeballing it. Set the Front Edge to bevel, the Back Edge to Square, then open up the Front Edge Size and RAMP the Depth way up to about 1000. Start increasing the Width until the shape looks equilateral.
I have some stuff I have to take care of for awhile, I'll come back with a method of being more precise afterwards...