Report issues, bugs, and or unexpected behaviors you’re seeing. Share Fusion (formerly Fusion 360) issues here and get support from the community as well as the Fusion team.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
In the design work space using the move/copy command on a component displays the move manipulator as well as the dialog box. In the past, picking a specific directional handle on the manipulator moves the component in the direction chosen, Currently this is now not responding in the manner expected, typically when selecting a rotation handle and expecting the component move rotationally it moves in an unexpected way, say along the x axis. Has there there been a change in the functionality that I am unaware of.
The only preference I could find was in Design/Assemblies/First component grounded to parent... this was checked, so I unchecked it. Upon restarting Fusion the problem appeared to go away, manipulators were working as expected. Unfortunately when I, as a test, grounded to parent the example box model, the problem came back, so I again restarted Fusion with a new box primitive with the preference still unchecked the problem still persisted. It all seems a bit flakey.
I think you are right regarding the Ground to Parent aspect as I have only encountered this problem since this upgrade was issued.
The only preference I could find was in Design/Assemblies/First component grounded to parent... this was checked, so I unchecked it. Upon restarting Fusion the problem appeared to go away, manipulators were working as expected. Unfortunately when I, as a test, grounded to parent the example box model, the problem came back, so I again restarted Fusion with a new box primitive with the preference still unchecked the problem still persisted. It all seems a bit flakey.
I think you are right regarding the Ground to Parent aspect as I have only encountered this problem since this upgrade was issued.
Fusion
