Thanks Mitch, this does make sense to me. The problem seems to be the shift of the time consumption, whether being before or after the Make2D. Time consumption is of course subjective, because while I wait for the program to do something, I can do other things, almost like when rendering, where I do expect that sometime is devoted to calculations done by CPU/GPU. Probably putting an option (which would leave the user to choose/wait or not depending on the scene/model complexity) could be useful, in my opinion. I never fully understood the reason why some operations could not have a time prediction, so that the user can choose. For example…during a highly demanding command, the user could be informed of a rough estimated time. Furthermore, just as a concept, if Make2D does a virtual calculation, could it not be possible to store a part of this calculation, so that the Make2D would be faster when projecting the virtual intersections? Finally, in the past I was thinking that programs could perform series of tasks, when not actively in use by the operator (in the night for example), having a sort of selection of computations to perform, saving time during the actual active use.