<Charlie_root> wrote: ↑
Sat Jul 18, 2020 4:11 am
etrombly wrote: ↑
Fri Jul 17, 2020 10:32 pm
The majority of the heavy lifting is done in C++
well let's just say that's a huge dissapointment ... I mean I always assumed it was slow because of python ... is CAM processing generally that slow ? like, even in non-floss software ? That can't be true
I mean howcome Slic3r can just eat through a huge complex model at 0.2mm layer height basically instantly ?
what if we ditch G2 interpolation and just use linear piecewise ? would that speed it up ?
In reply to a model I posted which was having problems, etrombly has just made a couple of very simple changes which get rid of unneccessary loops. I suspect a lot of optimisation can be done. The 3D code is still pretty new.
https://forum.freecadweb.org/viewtopic. ... ad#p417068
Russ has done an amazing job adding a huge amount of functionality, the number of parameters makes 3D very flexible already and etrombly had been fixing bugs quicker than I can post them.
If the main task can be split into "shovel loads" as Russ suggested, maybe those can be run in parallel.
I'm equally suspicious of using a clunky, single thread, interpreted language like python for this kind of work. Maybe more can be moved to c++ with time.