Triangle (DX9 Indexed) Broken?

Is it possible that Triangle (DX9 Indexed) is broken?

Unexpected behaviour: Sometimes on corner of a rendered triangle is situated far away (direction 1,1,1?), or the corners are otherwise at a wrong place rather far away (~20 units). This seems to be influenced by the Alpha value of the Color (Vertex) pin! Happens with beta 16 and 17.

Reproduce: open e.g. the helppatch for the triangle. Move the alpha value to a value other than the default 0.75: For <=0.74 the position of the triangles jumps slightly, for 0.76<=alpha<=0.99 the triangles are heavily distorted (find out by attaching a camera. for alpha==1.0 sometimes also something strange happens…

It seems to be indicated in the forums that this node is obsolete. If so, why is it still in the nodelist, and what is the best alternative to render masses of single (non-equilateral) triangles? The Pillow_N module seems to be suitable, but only for equilateral ones…

Is it possible that Triangle (DX9 Indexed) is broken?

i share your doubts.

i think this node is available since beta5 or sth like this.
in any case before it was possible to make use of shaders.
i remember @kiilo and me challenging on vvvv in IRC who makes the first 3d importer-patch for vvvv.

so since VertexBuffer (EX9.Geometry Join) this node is kind of obsolete now.

so the most efficient/elegant method to make triangles now is constructing them from ground up, normals an all, via the VertexBuffer?