Code length, processing speed

[Ignacio Azpiazu]

Does it makes any (positive? negative?) difference strictly in terms of 2D redraw time to draw with LINE2 and say ARC2 as opposite to RECT2s and say POLY2s? Is processing speed, even if minimal, a factor to consider?

Whenever I have the choice I favor whichever I can code faster, but I don't know if redraw time should also be a factor. The same in 3D when I have the choice of say a MASS or lots of POLYs or PLANEs.

I am working on a couple of chairs and auditorium seats etc. that can end up repeated thousands of times in a view, so I'm wondering.

[Anonymous]

Hi Ignacio,

For 3D, the only thing to take in consideration is the number of pgons.
After a 3D view (rendering), ask for a complete repport, this will indicate the number of pgons, then make a comparison according to your choices.

I didn't check for 2D, but i think a rect2 is faster than four lines. (when repeated 1000 or more time).

[Anonymous]

One thing I do to speed things up is give the user the ability to change the resol. That way they can have it fairly low most of the time.

[Anonymous]

Julia wrote:
One thing I do to speed things up is give the user the ability to change the resol. That way they can have it fairly low most of the time.

Julia is right, better to start by this point. This can save a lot of time for 3D calculations.
Another setting is the use of the "shadow on/off" command, specially for small details.

For eg. take a cylinder.
resol 36 & shadow on, --> 98 polygones
resol 36 & shadow off, --> 38 polygones

resol 18 & shadow on, --> 53 polygones
resol 18 & shadow off, --> 20 polygones

For a simple tore, section resol 36 and path resol 36, --> more than 2000 pgons!
And twice more in case of triangulation.

These small settings can be important at the end.
Note also that closed bodies regenerate faster in 3D than open ones.