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
They should be namespaced or otherwise boxed so we don't have issues with global variables but there definitely should be a way to share parameters across designs.
I am using Fusion 360 at two places I am working at now and my job is to create a library of parts that can be modified with user parameters and then assembled. Not having shared parameters means that the best way to do this now is to have the full assembly in one file driven by over 150 user parameters. If the parameters were shared then I would not have to recreate and continuously update user parameters in other files. Please incorporate this ASAP.
This would be a huge help. I can see many applications where company design standards can be set with parameters and spread accross multiple designs. That said, such a parameter may need a way to lock itself to prevent inadvertant or unauthorized changes.
It would be very helpful when designing a large assembly with multiple imported components from vendors : this could let us replace a component and its interface to other elements would update automatically (e.g : holes that receive the fixtures used to bolt things together). Many errors could be designed out, saving a great deal down the prototyping / production process.
To keep the component in read-only mode, parameters could be displayed into the assembly's parameters list so that they could be used in formulas; but not edited.
I just want to reiterate how useful this feature would be. Currently, its useless to build a collection of variable sized parts to include in other assemblies. For example, I regularly use rectangular T-slot extrusions. I thought I'd be able to create a single file that defines an extrusion profile then use an exposed user parameter to vary its length when needed. Unfortunately, this seems impossible.
If you do finally create this feature, please make it so that the parameter can be varied for each instance of the linked component. For example, in a single assembly I may need the above referenced extrusion in lengths of 500mm, 1000mm, & 10,000mm. I shouldn't need to create three different components when the only difference is the length.
Well "global" as in project-global, but yes! I'd need this right now with one project actually since there are many parts that need to fit together to certain rectangular pipes and the pipe size might have changed a few times...
Having something like an import file to define project parameters would be very helpful when the component details need to be based on project-wide criteria.
I would just be happy with Project Parameters. As each new design is generally in a project. so being able to have a Project parameters so i don't need to try and create all the parameters i am going to use in a single design and then save that as a template for everything else i do. As each time i find i need a new parameter i have to go back to the template and create the new parameter in there as well so then next design has the new parameter. Parameter.
Maybe, instead of having a dedicated doc to host the parameters, we could simply cascade the parameters from one design to the next : from the Parameters in design B, I could use an option to go and pick a parameter P in design A. P would stay linked to design A, i.e it is read-only in design B, and any change done on P in design A would be reflected in design B.
The problem with project parameters is that the majority of components that I see myself using this for would be for really generic components like extrusions and screws where I'd only want to model them once but may use lots of different lengths in lots of different projects.
We also have to keep in mind that we may have multiple imported instances of the same part which may have dependencies on each other. For example, suppose I have several instances of the same extrusion inside a part and the length of one is dependent on the length of another. So, I should also be able to use formulas within the parent part to determine the parameter values of the child parts. Since you could also use parameters from your parent part in the formula for the child part, this essentially gives us unlimited flexibility in mapping parameters and the project level parameters are no longer necessary to solve this problem. However, I can see some uses for project level parameters. Just not as the ultimate solution to this problem.
Ok so say I am using parameters to model a Bench for instance and I want to model each component of that bench individually. But some of part B's dimensions are a formula of Part A and C. If I wanted to model as such I currently would have to make a template as I do, or re enter the dimensions from Part A and C again. To which human error comes into play which could cause me to make mistakes on parts F to ZZ because Part B was calculated wrong and they are all referenced from Part B and I made an error having to enter the same parameters an additional time. Having the option for Project parameters gives me the option to reference parameters from any part within that project. So as Fusion would like you to work. You make a project folder and populare it with parts from that project and then once finished move onto your next Project.
It's not the same as parametricly moddeling in Inventor but it would make designing a large project that re uses and or references parts from the same project much easier and make it a better workflow.
> it would make designing a large project that re uses and or references parts from the same project much easier and make it a better workflow.
I'd agree with that. might actually be better to have all shared parameters within a Project in a distinct doc than cascading them like I suggested earlier. Some formulas could be built based on shared parameters, either on the Project level (same doc than shared parameters) or inside a specific design. A change in one shared parameter would be reflected wherever it is used... I'd love that !
It seems that we are discussing two different things here, i.e one that addresses the need to have several parts easily derived from a single generic parent, and another one where we need to share parameters across different designs within a project.
For case #1, wouldn't it be possible to simply duplicate the generic design and have an instance of it in each place where it's needed ? Of course, if there is a change in the generic design, this wouldn't be reflected in the children designs, which is of course a limitation.
