MauricevanLeeuwen
commented
11 years ago Your question is stated in quite vague terms. I suppose you don't refer to the speed of WebGL rendering your model, but to the speed with wich CoffeeSCad rebuilds your model after changing parameters.
I did some tests with OpenJSCad and found at that a lot of the time is spend in the boolean operations due to the model being canonicalized and tessellated. I see that CoffeeSCad reused this code (without mentioning the original author in the licence though? but I don't know a thing about licencing though..) so you will have the same speed issues there.
Even one union on a model with many polygons or vertices will take a substantial amount of time. I suspect doing the tesselation in c++ (or opengl 4.0 .. not supported by webbrowsers) will be quicker. But if we do it with javascript, it doesn't matter if you do it in the browser or locally. Both use the same javascript engine (V8 or SpiderMonkey) on the same machine.
For the workflow: You could split your model and code into parts, and only build and render the parts your working on. But this will not speed up the build times of your complete model, it will only make working on large models easier.
You can also try to not rebuild your complete model on every parameter change. Rather split your code into parts that are evaluated in consecutive order, and have parameters for each part. Then, on parameter change, you don't have to evaluate the code that belongs to earlier parts, but only for the parts that follow after parameter change. Then you might try to do the union operations, or other operations that trigger heavy computation, early in your code, and have parameters that do very simple transformations later in the code...
In pseudo code, imagine the speed you might gain when you only execute the code that is needed for the parameter change:
var doAll = function(param1, param2){
operation1(param1);
operation2(param2);
};
doAll( value1, value2 ); // initially
doAll( value1, value2 ); // on value2 changevar doFirst = function(param1){
operation1(param1);
};
var doSecond = function(param2){
operation2(param2);
};
doFirst( value1 );
doSecond (value2); //initially
doSecond (value2); // on value2 changeCan you maybe comment about what slows you down?
kaosat-dev
Daubsy
I am working on a complex model. When I make changes, it takes a very long time for the scene to update.
Will local development provide faster rendering speed? Are there any other development tools / workflows that can help with this?
Thanks!