Default FeatureScript version for new Feature Studios in old documents

jacob_kingery

I have a document that was created when the FeatureScript version was 275.  Since then, version 293 came out and my Part Studios automatically updated to 293, so I also changed my Feature Studio to version 293.  However, if I create a new Feature Studio now, it automatically puts 275 as the version.  Since everything else in the document is version 293, shouldn't that be the default version when I make a new Feature Studio?

ilya_baran

This is a bug that we fixed -- the fix should be in the next time we deploy.

jacob_kingery

Awesome, great to hear!

phil_gauthier

I have a similar situation. I recently branched a part that has an old version inside my part studio. When I go to update a derived part I receive the following error.

I also have lost the updated functionality of "up to vertex" for extrudes within that branch only. I assume the issue is some where along the lines that the new branch is missing the latest update because it was created from a version that did not have the update in it. I am curious if I can force a featurescript update on the branch/entire document.

ilya_baran

@phil_gauthier
Please share the document with support -- we can upgrade it.  We're working on ways to give you more control in the workflow.

phil_gauthier

Thank you @ilya_baran. Just shared with support.