C#. I replaced the for loop with just this: Parallel.For(0, numMapVerts, i => …
With 40k verts using parallel.for I got ~23 seconds on 10k iterations, and ~37 seconds using the single threaded version. So that is pretty cool.
I’ll test all these potential optimizations when I get back home from work. I appreciate all the tips so far! PolyTools3D: Beautiful! Tried wi…
That is a good point. I can’t tell you much about the requirements of the tool, I was just helping a guy to speed it up, and basically converted each…
This is really great, thanks Jorge!
Thanks! I will test it when I get back from work. I noticed that the IPoint3 also implements IDisposable, so i’ll call that one too.
The mxs version did perform well on ~1k vertices, but it had problems with anything much higher than that. The .net function runs at 15 fps on my old …
Autodesk.Max.GlobalInterface.Instance.TheListener.EditStream.Printf() to print to the listener window or Debug.Writeline() if you want to write to…
Here is the messy c# version of Klvnk’s code:
Thanks. I ended up running the intended maxscript event code from my wpf control instead.
Thanks, but it’s not what im after. My gui is a wpf control, hence the elementhost control.
Look at So the code would be something like this, no? I dont have max around atm. nw = DotNetObject “System.Windows.Forms.NativeWindow” nw.AssingH…
The AttachThreadInput from that source was a cool way of doing it. I wonder if it cleans up well after quitting/restarting the sublime script.