....when trying to move points on a curve which is already part of a surface (created from surface network command).
It seems that the first construction line is obeyed but any subsequent ones are ignored.
If the curve does not belong to a surface then everything works fine.
Any thoughts?

Hi niko,

> ....when trying to move points on a curve

With which command, the Move command? Or by some other method like dragging the points without starting a command?

Also which view are you in when you notice this behavior, is it the 3D view? Do you see a different behavior in ortho views?

You may be running into some suppression of "on" object snap when in the 3D view which is described in this previous post:
http://moi3d.com/forum/index.php?webtag=MOI&msg=2889.1

I guess that may be getting applied to the Move command when it probably shouldn't, since move is not so much a planar-ized command like Rotate, although it does behave in a semi-planar way when you pick in the ortho views, which may be why it is getting categorized in that way.


Also when are you creating the construction lines, do you create them inside of the Move command? Knowing a few more details about exactly what steps you do may help me to understand.

- Michael

Probably the one that works is the one that is in the same plane as the initial point.

The Move command uses a kind of "virtual construction plane" when working in the ortho views - that means for the second pick an ortho view's construction plane is essentially moved to go through the first pick point.

That's so for example you can pick the base point anywhere in the 3D view (at any elevation), and then switch to the Top view and then when you move your mouse around, the second point does not "slam down" on to the real construction plane (which then would produce movement in elevation which may not even really be apparent when looking in the ortho view) but instead stays in a plane going through the base point.

The Move command sets some flags to get semi-planar behavior like that, and then that is probably triggering the "on" snap suppression as describe in that previous thread. That may need a small adjustment to avoid this.

- Michael

Sorry about the lack of details.
Yes it is inside the move command in the 3d view.

EDIT; I could not try to recreate the problem on a new network which tells me that the the problem had something to do with the curve and surface existing in a different layer.

Hi niko, I think it won't happen if the construction lines are created at the same elevation above the construction plane as the point you are trying to move.

I think I see what is going on and I should be able to tweak it for the final release to avoid it.

Thanks for reporting the problem,

- Michael

Disregard the previous post Michael it did happen again.
Yes, it does happen in the 3d view. It always seem to snap to the first construction line created inside the move cmnd. If I try to generate any(construction lines) other than the ones originating away from the base point then the rest are not obeyed.
Is there any fixed planned for this for V2 final, or is there something I can do to avoid it (I always like to work in the 3d view)?

Hi niko, I have made a fix for this for the v2 final release, thanks for reporting it.

- Michael

Thanks Michael.
By the way I have just noticed that the same thing happens inside the copy command.

Hi niko, yeah a few similar commands like Move, Copy, and object dragging were affected.

They are all fixed though with the same pointpicker fix.

The problem was caused by a change back 2 betas ago, to try and avoid some kind of erratic-seeming behavior in commands like Rotate, which was described here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=2889.1

When "on" snap kicked in on things like the x or y axis lines during Rotate inside the 3D view, it could be kind of confusing, so I added in something to suppress "on" object snaps that were at different plane elevations, for commands that restricted picks to be on a certain plane.

Move and Copy accidentally fell under that same category because they have some semi-planar behavior in them when their 2nd points are picked in the Top, Front, or Right views.

The fix is that the "on" snap suppression will only kick in for "fully planar" commands that force all points to be projected to their working plane like Rotate, and not to have it suppresed for "semi planar" ones like Move or Copy.

- Michael

You the man Michael.
MOI is the best modeler bar none.

This is Sparta!!