by ArtF » Wed Dec 31, 2014 12:41 pm
Hi All:
For those that dont subscribe to my channel on youtube, here is a video of testing in the new Simulation code to be released in the next version.
https://www.youtube.com/watch?v=q81uS9uasug
Simulations are handy, they show the effect of various tools on output, but weve never really needed them as most of my output has been primarily in 2.5D and imagination has typically been enough. But simulations are a keystone for toolpath planning code, and in the new year Ill be
releasing code for engraving of photo lithophanes, Celtic knot engraving and more in the 3d area, untill finally the ability to load STL's of any kind and machine them. Its a puzzling thing, simulator code, its hard to do because it has to be fast and yet its a slow process. Few examples exist of exactly how to do it and those that have done it tend to guard their code. I believe I now know why.

I think Ive found a balance between speed and accuracy that will serve us well next year with this real-time distortable meshing code
. Ive already found through simulation a bug in the current tab code that causes a ramped tab.. so even prior to its release the simulator has proved very usefull. I hope , uong its release, you find it handy as well.
Hope your XMas has been a good one, enjoy your New Years Eve.
Art
Hi All:
For those that dont subscribe to my channel on youtube, here is a video of testing in the new Simulation code to be released in the next version.
https://www.youtube.com/watch?v=q81uS9uasug
Simulations are handy, they show the effect of various tools on output, but weve never really needed them as most of my output has been primarily in 2.5D and imagination has typically been enough. But simulations are a keystone for toolpath planning code, and in the new year Ill be
releasing code for engraving of photo lithophanes, Celtic knot engraving and more in the 3d area, untill finally the ability to load STL's of any kind and machine them. Its a puzzling thing, simulator code, its hard to do because it has to be fast and yet its a slow process. Few examples exist of exactly how to do it and those that have done it tend to guard their code. I believe I now know why. :) I think Ive found a balance between speed and accuracy that will serve us well next year with this real-time distortable meshing code
. Ive already found through simulation a bug in the current tab code that causes a ramped tab.. so even prior to its release the simulator has proved very usefull. I hope , uong its release, you find it handy as well.
Hope your XMas has been a good one, enjoy your New Years Eve. :-)
Art