IsoMesh | related tools for Unity for converting meshes | Service Mesh library

The solution it multi-layered.

Your Icosahedron:

You were half-way there with rotating your icosahedron and its vertices. Rather than applying the rotation to all the vertices (which would actually cause some pretty extreme rotation), apply the rotation to the mesh only. But that doesn't update the vertices, right? Right. More on that in a moment.

Your Circles:

You have the right idea of placing them at each vertex, but as WestLangley said, you can't use lookAt for objects with rotated/translated parents, so you'll need to add them directly to the scene. Also, if you can't get the new positions of the vertices for the rotated icosahedron, the circles will simply remain in place. So let's get those updated vertices.

Getting Updated Vertex Positions:

Like I said above, rotating the mesh updates its transformation matrix, not the vertices. But we can USE that updated transformation matrix to get the updated matrix positions for the circles. Object3D.localToWorld allows us to transform a local THREE.Vector3 (like your icosahedron's vertices) into world coordinates. (Also note that I did a clone of each vertex, because localToWorld overwrites the given THREE.Vector3).

Takeaways:

I've tried to isolate the parts relative to your question into the JavaScript portion of the snippet below.

• Try not to update geometry unless you have to.
• Only use lookAt with objects in the world coordinate system
• Use localToWorld and worldToLocal to transform vectors between coordinate systems.