Serious bug in the translate/rotate tool

[Kaare Baekgaard]

I love the new design of the tool, but it has a serious bug.

 

I include a video, that demonstrates the bug:

 

 

 

[line-weight]

It looks to me like you are grabbing the node itself rather than grabbing the green arrow, which I think is what you are supposed to do if you want it constrained along that axis? It should then display a light blue dashed line (or at least that's what happens when I try it).

 

You are getting a red dashed line which suggests it's found some kind of snap point, and is projecting a line out from that instead.

[rDesign]

I think @line-weight is correct, you’re probably grabbing the wrong part of the 3D Dragger for the operation you are wanting.

See this YouTube video:

 

[line-weight]

The 3d dragger changes in 2024 don't seem to have received much attention but I think are quite significant and a big move in the right direction.

 

It seems now to be usable in more object types than I had realised. For example, structural members. This will be very useful I think.

 

I need to spend some more time exploring what's changed and how it works. What I would like is if this dragger could somehow become available whenever I select a 3d object (not just when I want to reshape it), because it seems like we ought to be able to use it to reposition, scale and rotate whole objects as well as nodes. Would this not save quite a few clicks on working plane, rotate tools and so on?

 

 

[Kaare Baekgaard]

I am sorry if it seems rude, but kindly consider to remove your comments as they muddle the message - that there is a serious bug in play here. I have included a second video to demonstrate the workings of the 3D grabber in relation to the bug. Please notice that I do not at any point click the gray point in the center of the 3D grabber, but the small, square part of the arrow, which enables snapping to other points.

Edited September 19, 2023 by Kaare Baekgaard
clarity

[line-weight]

 

Ok - I see now what @Kaare Baekgaard means and am able to replicate it. There does indeed seem to be a problem.

 

(It may look like the dragger is being grabbed by the main node rather than the little square - this is because as soon as you click on the little square, the cursor does a kind of jump to the side.)

 

Edited September 19, 2023 by line-weight

[line-weight]

I think that it maybe happens in top/plan view but not in an orthogonal "top" view.

 

In top view though, I seem able to provoke a different kind of jankiness -

 

 

 

[zoomer]

Hmmh, I should play with the new Gizmo ....

 

Usually that mid point is meant to reposition the Gizmo itself.

 

The arrows are of course for moving - locked to only along that single axis

and the small Dot between Center Dot and Arrow - I would have expected to be

Scaling instead of Moving.

The rectangular Area, to move in 2D Axis.

 

If the middle Dot is not for Gizmo repositioning - then I would expect it to move

in all 3 axes ......

[line-weight]

7 minutes ago, zoomer said:

Hmmh, I should play with the new Gizmo ....

 

Usually that mid point is meant to reposition the Gizmo itself.

 

The arrows are of course for moving - locked to only along that single axis

and the small Dot between Center Dot and Arrow - I would have expected to be

Scaling instead of Moving.

The rectangular Area, to move in 2D Axis.

 

If the middle Dot is not for Gizmo repositioning - then I would expect it to move

in all 3 axes ......

 

It gets explained in the video @rDesign posted up above. To reposition or switch to scaling mode, all happens in the options in the toolbar -

 

[line-weight]

@Kaare Baekgaard did you manage to get this recognised as a bug?

[Senthil Prabu]

@Kaare Baekgaard Thanks for pointing this out and taking so much effort to explain this.  I can be able to reproduce it and it is happening only in Top/Plan view, top and 3d views works fine.  Created a bug VB-200243 and I will look into that.

 

Thanks,

Senthil Prabu

[Senthil Prabu]

@Kaare Baekgaard Fixed the issue (VB-200243) in Update 2.

 

fyi: @Hugues