Problem summary USD Objects won't remember to use their assigned default Variants after the first time they're imported.
Customer reported version Mari 7.0v2
Customer reported platform n/a
Steps to reproduce (test assets attached)
Create a Project using a USD assembly file. Alternatively, create a new Object in an existing Project using a USD assembly file.
Note what the default variants are in the Add Object Settings dialog.
Select which Variants you want to use and note them down.
In the same Project or in a different/new one, import the same USD assembly file.
Note the currently selected Variants in the Add Object Settings dialog.
Expected behaviour Mari should always open the Add Object Settings dialog with the same default USD Variants selected, regardless of the same file having been imported already using non-default Variant options.
This is the case as default Variants are defined within the assembly file, and as such should be respected.
Actual behaviour Mari uses the "last selected Variant" instead of the default one.
This can be a problem particularly for USD assemblies with "child-variants" that are shared across "parent-variants", as is the case with the test asset provided by the customer. For example, if parent-variant 1 uses child-variant A, and parent-variant 2 uses child-variant B, importing parent-variant 1 with its defualt child-variant A means that on the next import parent-variant 2 will also be set to child-variant A instead of B.
This issue even happens across Projects, so if a user wants to create two Projects using the same USD assembly file but different variant selections, he'll run into the same issues.
Workaround Once Mari is restarted, it forgets the last used variants, and returns to using the file's default options.
Reproduced by support This bug has been reproduced in: Mari 7.0v2 - Windows 10, Rocky 9 Mari 7.0v1 - Windows 10, Rocky 9
Earliest version tested Mari 7.0v1 - This feature (variant selection dropdown) did not exist before this version