How do I turn of highlighting when moving an object?

[waltersandmeyerNYVLH]

Hi there,

Sorry if this has been asked before, but I don't see a solution to this, and am not sure if there is one. 

I want to move a part point-to-point, but when the part is selected, it totally obscures the point I want to move it to.  The visibility of the component that's blocking the point is already turned off, but it still highlights and obscures the view.

I know I can move the part far away, clear the view, and then move it to the point I want to select, but I encounter this issue a lot and would love a way to just turn off, or turn down the opacity of the highlighting.  Is there a setting for this that I haven't found?

[TrippyLighting]

Please share the model. Export it as as .f3d file and attach it to a post.

In general, unless you are in direct modeling mode I would stay away from the move command!

[patryk_anton]

I top up this question as there is no solution for it. How to disable this highlighting? It blocks the view of the component to be move e.g. with point-to-point feature. 

[Drewpan]

Hi,

There are a number of ways to turn visibility on and off, including when moving objects. Why are you moving the

object? It is an important question because fusion treats moving in a particular way, and as @TrippyLighting has

suggested it should be avoided. Under normal circumstances, the only reason you would move objects around would

be to position them to join them in some way and this should be done with the Joint command where possible.

If you are moving objects around so that you can see what you are doing with your model then you are not using the

visibility in the browser tree correctly. If you can attach your model and give us a little more information in regards

to what you are trying to achieve then we might be able to help you better. It may just be a simple workflow issue

that we can help you become a better modeller with.

Cheers

Andrew

[patryk_anton]

Hi,

Unfortunately I can not share the model I am working with as they are under NDA. I work with models of customer parts and models of supplier equipment (e.g. welder) - all imported from STEP files. I need to position the parts in relation to the equipment to check for collisions/interference and then design an intermediary part which will hold the customer part in place during process.

Often the part needs to be in multiple orientations so joining them makes thins more difficult (break previous joint and make a new one). Also when joining I get the issue that only one component of the customer part assembly is moved instead of the whole part (due to import from STEP the subcomponents of the part assembly are not joined together).

Except the highlight issue the move option where i can change the pivot point or use the move point-to-point feature is perfect for what i am doing.

[Drewpan]

Hi,

In this case it sounds like you would benefit greatly from using configurations so that you can set up your initial

conditions and then move the actual part design around inside. Moving parts is rarely a good thing because of the

way fusion calculates things. A move typically causes fusion to do a full recalculation of EVERYTHING up until the

point of the move, and then regardless of what else you do, if you move something again it will force another full

recalculation. This hammers performance often.

In terms of visibility of components, I think you may be stuck with the visibility and the browser tree.

Cheers

Andrew

[youngro8]

This is so frustrating how is there not an option to turn off highlighting when moving parts its ridiculous?  Sometimes I want to move imported mesh objects around other parametric bodies or components approximately to get an idea of how something will fit or how I'm going to design something.  The highlighting makes this pretty impossible to see where I'm moving anything!!!

[tnash4ZUH3]

Moving complex objects shouldn't be dismissed as being bad practice, I often move objects prior to joining and use the reset position button once I am done. Sue me. Sometimes designs are simply a 5 minute endeavour to hack together a 3D print, and that should be okay.
Where a capture position has been performed, clicking that item in the timeline can sometimes cause a terrible user experience on both performance and visual appeal. Some people just wish to use the move or capture position feature without having an aneurysm.

[Drewpan]

Hi,

The Move command exists for a very good reason and used correctly it isn't a problem.

The problem typically pops up with beginners who move things around because they

cannot see some part of their design instead of using the eye icon on the browser tree.

The other major reason Move pops up is because, again often beginners, think that if

they move something in their design it is Joined to another whatever instead of using

one of the Joint commands.

I have never said don't use Move, just use it correctly. I have used move in some of my

designs because it was the only way I could achieve whatever I was doing. I will say

however that when I need to move something for aesthetic reasons I would typically

set the default position of a joint and not just move it around.

The recalculate issue is well known and has been around for years. This is more about

educating people of the problem and tying to recommend good workflows.

I fully understand hacking together something but the thing about hacking is that it

works because you have learned to avoid the pitfalls and create something that may

have issues but it does the job.

Cheers

Andrew

[tnash4ZUH3]

I appreciate your polite reply, but I still believe the visual degradation described by Youngro8 hinders the command's utility. Unless I’m mistaken, they’re referring to how moving a component, regardless of its sub-component visibility settings, turns the entire component’s contents solid blue, obscuring all visual context. In components with hidden bodies, components, or sketches, this can create confusing visuals. In my opinion, moving a component should visualize only the visible elements as blue. If this were an option in a settings menu, I wouldn’t complain.
Tom