Why are input user parameters sometimes not captured with a feature (e.g. Box)

[richardlawler]

Sometimes parameters are not captured with a feature when they are used as inputs.

In this trivial example I have created three user parameters: width, depth and height. I then create a Box using the parameter names as inputs, but only the values for the first two of three inputs are recorded with the feature. I can subsequently change the values for the feature to reference the parameters and everything is as I would expect it.

The obvious consequence is that I expect when I have input a parameter name then the parameter not the value should be retained. I should not have to double-check Fusion's work.

Is this just a bug in Box creation, or am I missing something fundamental about user parameter expansion.

[richardlawler]

It happens with other features like Cylinder and Torus, but it doesn't happen with Sphere. Sphere only has one input where the others (Box, Cylinder and Torus) have multiple inputs. The parameter for the last input is retained in each case but the earlier inputs are converted to values.

[jeff_strater]

I am not able to reproduce this behavior.  Box seems to capture all 3 parameters for me.  See the screencast below.  Can you record a screencast of what you are doing, or point out where your workflow differs from mine?  Thanks

[jeff_strater]

OK, hang on.  I read " but only the values for the first two of three inputs are recorded with the feature", so I only checked the third input (height), and it seemed to work OK.  Going back and looking, I see the opposite - the first two are not captured, but the 3rd is.  That is, indeed, wrong behavior.  We will investigate it.

The relevant Fusion bug is FUS-19028

[richardlawler]

This is my screencast. I thought I attached it to my original post, but I guess it didn't happen.