Turning on indexing kills the animate speed

Good morning, I have found that when I turn on indexing then run an animate operation in the latest build 4.1.3 animation speed slows way down to an unusable level. Turning off indexing seems to fix the issue. Thank you for all of your hard work.

indexed animations will always be substantially slower since they have to compute 3D geometry intersections. whereas non indexed are just 2D map deformations. this hasn’t changed since indexed animations were introduced.

hmm, ok thank you. I still think there my be an issue as it is almost real time slow also for some reason my animations are screwed up.

IDK if my setup looks right.

files --> export will produce a .kmz file that you can email to me for analysis [ sa at grid dot space ]

Will do, Thank you so much.

I can confirm this relative shift of part v. stock.
It was just a quick try in the last couple of days and I didn’t export anything.

1 Like

I’m going to have to construct test cases to make this easier to debug.

fixed. will push to production shortly.

1 Like

Thank you so much Stewart you are such a hard worker.

Issue still seems to happen in 4.1.4

The offset stock issue seems to be resolved but the very slow animate speed seems to still happen.

Until I can come up with miraculous new math or a library for subtractive solid geometry in real time, the indexed animation issue will remain. I may find marginal improvements, but not 10x any time soon

No problem, thank you. I wonder if it is because I am trying a pretty complex part. I also noted that even when the animation is choking out I have plenty of system resources left. IDK

there is no meaningful way to do arbitrary high performance parallel computation in the browser sandbox. things that can be mapped to WebGPU maybe. and there are some complicated WASM approaches. but all of those are intensive development efforts beyond my current free time. I should note that the current approach does use a WASM (c++ engine) library for solid geometry. it runs about 50% of theoretical C speeds, but does not offer threading. thus you will see idle CPUs.

Thank you so much for the free time that you do have. Still my favorite CAM software. I do wish I could be more helpful in writing software but that is not my calling. I have used kiri:moto a whole lot and am trying to learn indexing at this time. If I can do anything to improve the indexing please do let me know. I may make another thread for 10 for other questions though, hopefully you do not mind.

1 Like