Bug: Helix last diameter/radius does not apply

make a helix (also around curve does not matter), enter radius then hit enter to confirm and enter or space to complete, all well. now call helix again, the radius value is still shown, but enter or space does not complete the command, for it to complete i have to reenter the value.

checked v8 and v7 with the same result

and another bug:

when you make a helix around a closed curve the preview shows me this result which looks good.

when you confirm and complete the command it adds an extra funny kink.

i completed it from top view, when you actually try to complete from the perspective it seems to add a kink either already in the preview so that seems odd anyway.

also tested on v7 and v8 with the same result.

edit: ok this part is probably valid for open curves either. the endresult looks different to the preview and actually worse.

Hello- I see this, thanks.
RH-79441 Helix - accept default radius on Enter

-Pascal

1 Like

thanks Pascal, could you have a look at the 2nd bug?

@encephalon when making a full loop, better is to use turns and not pitch, otherwise you can get what you are seeing.

that will not help when i have a bunch of lines which should have an equal pitch, then i would have to manually calculate the amount of turns.

also… the same issue occurs with open curves.

If you have closed curves and they should have an equal pitch, then that’s not going to be physically possible to get a consistent result

I don’t see that here, can you send a sample file that shows that?

that is clear, the approximation the preview shows is good enough but it does not stick to the preview and changes after applying.

i send you one a bit later, i am actually busy procrastinating too much but actually that you can experience on any curve if you look carefully enough, the effect is much weaker here though than on closed curves.

so, here a file and a screen shot for helix around curve preview issue. as you can see on the left the preview is much smoother, when you release the command it turns into a result that is more edgy. i would say the curvier that input geometry is the stronger you notice that effect, on a less curved geometry you might not even notice it.

settings used

test helix preview.3dm (53.7 KB)

The preview is interactive, and is therefore built with less precision than the final result, that’s why there will be a difference between the two. I don’t see any issues in the resulting curve you sent btw? A top projection image of a curve doesn’t tell much.

if the preview uses less points, how much performance minus would that be when we add a more exact preview? talking about a curve?

the top view is in this instance what i needed since it is for a top view representation, i am just pointing out that there is a difference in preview (fact aside that i like the preview version more) but having an exact preview on such a low performance task might just be manageable i assume.

there are more important issues of course… but there always will be. starting somewhere to make it proper is essential i would say.

I’ll ask the dev. to see if there is a performance hit if the preview would be as accurate, might not be an issue nowadays:
RH-79739 Helix Preview

1 Like