the mxs version works in world space the sdk routine it uses works in local object space here’s the function… and yes it is relatively slow

I did implement the VertexBuffer method

just adding gw->startMarkers(); and gw->endMarkers(); improved things x8 thanks for the heads up Io though the documentation is non-exist…

I do most dev in 2010 as it’s the last max that allow unloading dll, whats a marker buffer ? ok seen it in epoly object. will check it out

that’s the trouble with bitmaps nothing is easy and always more work than you expect and boy do they eat memory !!!

looking in the sdk the DIB function is called like this texHandle = thmaker.MakeHandle(GetVPDisplayDIB(t,thmaker,texHandleValid)); return texHandl…

word of caution, don’t run this code if max is not running… unless of course you like “white out” max or add a check to see if max is running first t…

gets even more bonkers $.transform = (matrix3 [1,0,0] [0,-2,0] [0,0,1] [0,0,0]) $.scale -> [-1,-2,-1] $.transform.scalepart -> [1,2,1] $.sca…

not even the first value, if any are negative all are $.transform = (matrix3 [1,0,0] [0,-1,0] [0,0,1] [0,0,0]) $.scale -> [-1,-1,-1]

interestingly missing from the default meshop.turnEdges function could return the “other” edge (and hence the other face) so here’s the correction… d…

looking at the text prim they cache their hierarchy so not to call OrganizeCurves if they don’t have to so it maybe best to rewrite the above code to …

it does some kind of on the fly analysis (organisecurves function)… if a curve is entirely enclosed by another curve it’s considered it’s child.

discovered something new to me today… shapes have an internal hierarchy (which I don’t think is exposed to mxs… so here it is // GetChildCurves <s…