AU Class
AU Class
class - AU

Getting Started with Model States

Share this class

Description

The new Model States functionality introduced in Inventor 2022 software has many uses within your Inventor design files. It was introduced as a replacement for the pre-2022 Level of Detail assembly functionality, and also provides an alternative to the iPart and iAssembly functionality. This class will begin by discussing the uses of Model States, from their role in creating component design configurations to improving retrieval times and performance when working with a large assembly. You will also learn how to create Model States in both part and assembly files, and then how to maximize these files in your drawings and presentation files to document their design.

Key Learnings

  • Learn about the uses for Model States in your Inventor designs
  • Learn how to create Model States in Part and Assembly Designs
  • Learn how to use Substitute Model States to simplify Assembly designs
  • Learn how to use Model States in drawing and presentation files

Speaker

  • Avatar for Jennifer MacMillan
    Jennifer MacMillan
    Jennifer MacMillan holds a mechanical engineering degree from Dalhousie University, Nova Scotia, Canada. For the past 25 years Jennifer has been writing and delivering training content for CAD as well as other technical software platforms. More recently, Jennifer has been enjoying working with clients to design and develop unique learning and documentation solutions to support their end-users with their unique combinations of software, standards, and workflow procedures. She works with the Rand Worldwide division, ASCENT-Center for Technical Knowledge, where she develops and manages the training curriculum used by Autodesk Authorized Training Centers. She also has her Autodesk Certified Instructor (ACI) certification.
Video Player is loading.
Current Time 0:00
Duration 43:28
Loaded: 0.38%
Stream Type LIVE
Remaining Time 43:28
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

JENNIFER MACMILAN: Hello, everyone and thanks for taking the time to join me today. My class is all about how we're going to get started using the new Inventor 2022 model state functionality. My name is Jennifer MacMilan, and I work as the manager for learning content development with Ascent. Many of you may already be familiar with Ascent having used our material in training classes, but we also partner with a lot of software resellers, schools, and corporate companies like yourselves to help develop custom learning content.

Personally, I'm a mechanical engineer, and I have focused my career on the software support, training, and curriculum development for many mechanical design softwares. The majority of my time is spent creating learning content for Inventor. However, I also love giving sessions like these. So with that, let's get started. So this presentation is going to focus on the following four learning objectives. I'm going to begin by introducing you to the uses of model states, show you how you can create them, how you can also create substitute model states, and then how you can leverage all of these model states in your drawings and your presentations.

The format of this class will be a combination of PowerPoint presentation and demonstrations directly in Inventor. So let's get started then with our first two objectives, and those are going to be on the why you're going to use model states and to how you can create them. So the model state functionality is brand new with Inventor 2022 and it has many different uses. First off, it's great for designing and configuring multiple versions of the part in assembly files.

For example, here in my images I have park files at the top of my screen, and I have some assemblies at the bottom. And you can see that model states have been used to create different product variations in the park. So some different material properties, some different lengths. And in the case of the assemblies, I've also controlled the component display of some of the components in the assembly. You can also use model states to document your manufacturing stages by controlling feature level of detail.

And then the final three bullets I have here are all focused around the assembly side of things, where model states can really benefit you when you're working with large assemblies. You can use them to help simplify what's being displayed to help improve your retrieval times, and then they also can be used as a basis for model simplification if you're going to go out and share any of your design IP. So there are a few other things about model states that I'd like to discuss before showing you how to create them, and these next few bullets are really aimed at those of you that have used Inventor prior to 2022 when the model state functionality did not exist.

So first off level of detail functionality no longer exists in Inventor 2022, and it's been replaced with model states. And this is providing an alternative to iParts and iAssemblies. So you can choose to either use model states or you can use the iPart and iAssembly functionality, but you cannot use both. With Inventor 2022, the model state functionality is enabled by default with all of the Autodesk templates. And then if you decide you don't want to use those and you actually want to go back and use iParts and the iAssemblies, you simply have to enable those commands directly on the Manage tab on your ribbon.

So the first question I always get from students is, how do I take my older models from older versions into 2022 and how do they get affected? So there's two scenarios you want to keep in mind here. The first is if you do not have any iParts or iAssemblies in those older models, what happens is that model states does get enabled in 2022, and if you had any levels of detail in those files, they get converted immediately to model states. So when you go into your file in 2022, you will actually have some default model states created.

In the second scenario, if your parts had iParts or iAssemblies, the model state functionality is not enabled, it immediately recognizes you're using iParts and iAssemblies, so that remains the functionality. And then if you had any levels of detail, instead of model states, they get converted into design views. So that's kind of the two scenarios. So next I guess, if you end up loving model states and you actually want to convert your old iParts and iAssemblies in the model states, how is this done? Unfortunately, this is a manual process right now. You have to go in and actually make the changes in the new file to create the model states.

I recently did this with a part file. And what I did was I opened the table in my file, had it for reference, and then I removed the table from my file and then I recreated it, just referencing it. You can also go back and forth and copy and paste from the table because there is spreadsheets as well in model states. However, you have to be really careful with that because the syntax is not quite the same. So you'll certainly want to become familiar with model states before you start doing that kind of large scale conversion.

And then the iParts and iAssemblies get stored in vault as separate part files, and this is actually not the case with model states. They are all stored as separate files within vault. So what you need to do if you actually want vault to recognize all of the unique properties or parameters that gets put into your model states, you're going to want to make sure your Vault Professional implementation leverages items. Without this, you're not going to be able to see all of that data. You're only going to be reading the master data on that file. I'm certainly not a vault expert but I have added a little bit of information on this in my handout.

So before I slip into Inventor, I have one more slide on how you can create your model states that I'd like to just talk through. It's actually really easy and intuitive and really in just simply involves you configuring parameters, features, iProperties. And it's all done directly in the model geometry or using the Inventor interface. So unlike iParts and iAssemblies where you actually had a separate dialog box, you don't have to do that for model states. However, as I mentioned previously, you can leverage the use of spreadsheets.

So to do that, to actually create model states, you simply are going through and you're suppressing or unsuppressing features or components, you're making modifications to iProperties, to parameter values, constraint offset values. And then in the case of part files, you can also assign unique materials. So that's something that can be customized with that. In the model browser I have shown here on the right, you can see I've got a big area circled at the top. And that's my model state node. That's the new node that gets added in 2022.

The very first one is simply the master, that's the default configuration of your model. And then all the others are unique ones that I've created. And you can see that right now I have vise-short enabled. So that's the active one right now. You can see the check mark adjacent to that. And then the last thing I just wanted to quickly draw your attention to is the naming scheme. Really want to make sure that you name your model states to be clear, easy to understand.

And then also if you remember the level of detail functionality, there was a productivity tool called link levels of detail. There's also one now for link model state. So this is where having a consistent naming scheme between all of your sub-components and an assembly are really valuable. And I'll actually show you that in my demonstration. So with that, I want to flip into Inventor now, and we're going to show you a little bit about how you can create these. So I've got just an assembly on my screen here. And you can see that it's a pretty simple straightforward assembly. I have a number of different components, and then I have a sub assembly as well.

So I'm going to go through this and actually create my model states. So before I got started here I did create one. And I did that to show you that your naming scheme of the top level, the assembly, actually always shows in brackets the name of the active model state. So if I was to go back and here now and change back the master, you can see how the name has changed. So I'm going to just leave this for now because what I want to do is I want to start in my part file.

So I have a one part file here, and I have it open already. So I'm going to flip into this part file. And again, you can see the model state node is right at the top, I can expand that out, and I have my master. And right now what I want to do is I actually want to go through and create my model states. So to do that, I'm simply going to go New, and it's going to launch and create it. And now that it's created that, you can see model state one here. I'm going to click New again and New again.

Now I mentioned both the naming scheme so I'm going to show you just-- I'm going to be super original here and we name each of these vise-short, vise-medium, and vise-long. And what we'll do is we'll be varying the length of each of these. So you can see it's a very descriptive naming convention that I'm going to be using throughout my demonstration. So I've got three model states created. I can switch over into the second one that I created then also up to vise-short.

And as you notice, when I flipped between these, nothing happened to my model. And that's completely as expected because I haven't actually customized anything yet. So what I want to do now is actually customize the length of my short model state. And to do that I'm going to go into the parameters dialog box, I have a custom named parameter here called length, and I'm just going to modify that value. It's a really straightforward, it's all intuitive, because it's using the same dialog box that you would make parameter changes in.

And then when I click Done there, it updated to the smaller size. Now if I flip the vise-medium, you can see it's gotten a little bit longer. That's the original size and I'm going to keep that original size, but I'm going to make a change in this third model state. And to do that, instead of going into the parameters dialog box, I actually want to go in and show you how I can make modifications directly in my graphics window. So I'm going to show dimensions, and here instead, I am going to just modify the value here. And this is quite handy if you hadn't renamed any of the parameters. So you might not know what dimension value or parameter name it is. So this is a really easy way for you to know which parameters you're changing.

So I've just modified that. I'm going to update my model, and now you can see I have three different sizes. I have the long, the medium, and the short. So now I have those three versions and what I want to do is actually make another change to the model. And in this, I'm going to actually affect some of the features. So first off though, I do want to show you one little thing here, if you've noticed that this pencil icon is adjacent right now to the vise-short. So that's the active model state. And this pencil is identifying that it's the current model state that's being edited.

I'm going to click on this Toggle at its scope button. And when I do so, it's telling me that I've enabled my factory scope. And now you can see I have pencils beside all of the model states. And what this means is that if I make any kind of change to my model at this point, it's going to change all of the model states. So you just have to be really aware of what your intention is with the change you're making and make sure your model state scope is set properly. So for my change, I actually only want to make it in the vise-short. So I'm going to toggle off that button so I know I'm only editing the short version.

And I'm going to go to the whole feature down here, and I'm going to suppress it. So for this short version, I don't need those mounting holes, so I've just removed them in that version. If I flip to vise-medium, you can see those holes still exist, they're still available there. And also in vise-long, I also have the holes. And I can actually make another change to these holes. And what I want to do is show dimensions here. And I'm going to change this again just to a different dimension value, update my value. And you can see just with that longer version, it just created a little bit larger mounting holes. So now I have the three different versions of holes through each of my model states.

So back at my short now, what I want to do is I want to show you how in the park model you can actually change up the material type. So right now, you can see Castile is set, that was the material that was set with the master. So I'm going to go in and choose copper cast for this version, and you can see how the material is updated. For my vise-medium I'm going to activate that and change that one to cast iron. And then with the vise-long, I'm actually just going to leave that as the default, which is just that Castile. I'm fine with that one.

Then I'm going to return back up into vise-short here. I'm always just going to the top just to keep track of where I am. There's no need to do this. You can flip around as much as you want to make your customizations. And what I want to change here is my iProperty value. Right now, each of the model states relies on the master for its iProperties. So I can actually go in and customize the properties.

So with it active, so I have an active right now, I can go into iProperties, and I can go let's change the part number. And right now you can see it's reading base, that was the value for the master. And again, with my very original naming convention, I'm just going to name that vise-short, then click OK. So now there's a custom iProperty assigned to that short one. Now I could go into each individual model state here, double click, right click on the top, going to iProperties and make those changes. But I want to show you the spreadsheet at this point.

So I'm going to right click on the node , click Edit spreadsheet, it's going to open up the spreadsheet. And if you've used iParts before, you can see it's very similar. Like I said, the convention is a little different in some situations so you want to really be careful with the copy and paste. But I'm going to draw your attention to each column is all of the unique properties that I've assigned throughout this part file.

And in this last one you can see that I have the iProperty set here for my part number, and I'm just going to change up these others to modify them here. So you can see in some situations it actually might be a little bit more efficient to go through. And once you've signed the very first one and it gets added into the Excel spreadsheet, you can go in and manually do the remaining customizations. I could also create unique model states directly in here. So using row 6 here, I could customize a brand new model state as well. I'm not going to do that right now. I'm just going to hit Save and Close this up, and go back to my model.

So now you can see if I was to go into vise-long here, take a peek at my properties, you can see that that customized version that I just modified in the spreadsheet has been updated here. So now what I want to do is just save this part file. And I'm going to return back up to my top level assembly, and you can see immediately that I need an update. So that's fine, I expected that. So now I have this part file, and if I expand out this node, you can see that all of those unique model states that I just created are all visible now in my part file.

So to actually control them at the top level, I have to go in and create model states at the top level nodes. So I've already got one here. It hasn't been customized at all yet but I'll create two additional ones as well, and I'll go through and name these again. And again, with the consistent naming scheme-- and then the third one here, vise-long. So I'm not going to change anything at the component level right now. What I want to do, though, is I want to show you how-- right now, I have vise-short actives at the top level, what I have to do is actually enable the model state out my component level as well.

So all I have to do that is ensure that the right one is active at the assembly, and then I just have to activate the one at the at the park level. And you can see that it's done because now you can see that I have that other material type now that color has changed on my model. So I did that so it would be really obvious to show that it's been updated. Again, vise-medium, I would match that up with my vise-medium down at the park level, and I'll do the same thing for vise-long.

So I mentioned about the naming scheme and about that productivity tool linked model states, I'm going to use that in a moment to show you how you can use this, but I also want to show how you could manually do it. And in this situation where I only have one sub-component that has model states, I find myself that just the manual activation is just as quick. So that's what I wanted to just quickly show you there. So the other thing to keep an eye on is I just compressed that component node there. You can see how-- you know that the correct model state is active because of the brackets at the end of the part file. If I switch to vise-medium, you can see how the right name is there. So it's a good double check for you to make sure that everything's good.

So with this vise-long active, I just want to draw your attention to the model, because we actually have a bit of an interference going on here. So this sub assembly right here, you can see is interfering with that base model. So what's really happening is that that sub-component, this vise screw component is not long enough for the change that I made in that base file. So prior to this demo, I actually went in and actually created these just to kind of speed things up because really we just created a part file and model state. So I did the exact same thing here.

So I created three different model states, each of them with a little bit longer component length. Now what I want to draw your attention to here is really important. It might be hard to see but these are all grayed out, which means I actually can't activate them at this level. And this is intended functionality with model states. And the same holds true for right clicking inside of a sub assembly. You can see here I've right clicked, I don't have any access to that new functionality. I can't create a new model state.

So when you're in a park file, you can activate those, but when you're in a sub assembly, you need actually to create them. You need to go outside the file and create those. So what I've actually done to speed this demonstration up a little bit is I have actually already created this sub assembly with all of the proper model states. So I'm just going to go in here and quickly replace the components. So now I've just replaced it with another version of it. And in this version, you can see that I now have those three model states and they would link up with the model states in this bottom version. Sorry, this [INAUDIBLE] part. So that's what I wanted to show you there.

Now I'm going to go back up to this top level, so you can see vise-long right now it's activated the right one here, but you can see that it hasn't done it here. So manually, if you go through and do those things, this is where I really want to show you the benefits of that link functionality. So with that, this is why the naming scheme is important. So vise-long, I want to connect with any other model states throughout my design that also have the same name. So I'm going to click OK here, it's basically saying that it's going to change my model state. And now you can see that there's no more interference, it's actually pulled in the right version of that assembly as well as the right version of that part file. And it did that simply with that linking.

Vise-medium, I'm going to do the exact same thing. So this is where you can see the benefit. When there's multiple levels of components, this link model states is a very handy functionality. So now you can see I've got very short actives, you can see the naming conventions in the model browser, how it all works there. So lastly, before I go back to the presentation, I just want to make one more change here. So we've changed features within parts, but I also want to actually just suppress a few components here. So with the vise-short active, I'm going to right click on this and just suppress some features here. And you get this dialog box that comes up. And really it's just telling you that it's going to recognize that the bill of materials is going to reflect the fact that you're actually suppressing those components. So I'm going to click OK, and with vise-short active, I'm actually going to open my bill of materials and confirm that you can see here that there are zero quantity of those components showing. If I go over in device medium and run my bill of materials as well, you can see now I have all four components visible.

So the bill of materials always reflects what's happening in your model state. So it's an active representation of your assembly. So with that, I'm going to go back over into my presentation, and what we're going to do is we're going to focus now on the third objective, which is with respect to using the substitute model states within your assemblies. And you can use these to help you simplify your designs.

So a substitute model state enables you to swap out a complex component or assembly for a simpler part file that represents it. The substitute still contains all of the bill material information that's normally associated with the assembly as well as any physical information like the center of gravity, or your mass, those types of things. Using substitute parts reduces the amount of components that get loaded into memory. So it's a great tool for working with large assemblies.

In the images I have here shown, you can see that on the left I have a master model here, where I have some fan blades at the front, and then on the right hand side, I've actually just created a really straightforward substitute model state, where I've replaced those blades with a new part file. And you can see how that's-- now it's still giving me the space claim for the extent of those blades but it's not giving me all the detail. So quite simple example there.

So in terms of creating a substitute model state, this is all done at the assembly level. And it's done by right clicking on the model state node as I have shown here. And instead of clicking New, you click New substitute, and then you have three different options that you can use to create that substitute. Just before I go to the next slide though, I just want to draw your attention to step 2 in my list there. There is an optional step that you can create a model state as well in there. And in the demonstration, I'll show you why that can be really beneficial for you in working with substitute model states.

So on this slide, I have screen captures of those three options that we just mentioned. The derive assembly option simplifies the assembly using the pre-existing derive functionality that you might already be very familiar with. And the result is simply it generates a park file that is then used in the substitution. And the Select part file option enables you to actually just replace the components with an existing part file. So something you already have on your hard drive. And you basically are given the option to navigate to that file and insert it to create your substitute model state.

And then that third option here, this property's panel, this is called the simplify command. This is a new name for what was previously called shrink wrap. So now in Inventor 2022, shrink wrap has been moved into this property's panel. And it has a lot of the same functionality, but I want to use this example in my demonstration to show you a little bit about that and how we can use the simplified command to create that substitute.

So now again, I'm going to go back over into Inventor, and we're going to move on to the next assembly. So I'm going to flip just to my next window here. Again, I like to keep it simple. This is a really straight forward assembly file, has a bunch of different parts, and also one sub assembly down here. So I'm to open this sub assembly, and this sub assembly is pretty straightforward, it's only got three simple little parts. And then I'm going to open up this part file as well. So this is what I want to highlight and show you what you can do to simplify it.

This is certainly not a large assembly. You wouldn't get any kind of benefit from doing this in terms of resources, that type of thing, but it's making it simple so that you can see how this functionality works. So I'm going to begin by creating a new model state directly up the part level, and I'm going to rename this to suppressed grip features. So again I'm being really original. I find it really the best thing is to make it obvious what your model state is. So that if anyone is going to be grabbing this file downstream that they'd be able to figure out and know what you have done.

And with this, I'm going to suppress some geometry. So I'm going to basically simplify this model and I'm going to suppress this just so I've removed kind of the cross cuts in this. So you can see that it's just a little bit more visually different than the first master model state. I'm going to click-- I've return master just to be sure you see the difference between the two, so the master and the suppressed. We're going to click Save on this file, close it up. And now at the housing level, again, if I was to extend the grip, you can see that there is a model state down here, but I need to create it another model state at this top level so that I can actually control it.

And this what I'm doing here is actually that optional step 2. I'm creating the model state for leverage when I create the substitute actually. So with that, I'm going to just double click down here. So I'm manually going to activate it. So now I have a master model state and the suppressed grip features model state. I'm going to return to the master for continuing here and you'll see what I'm doing in a moment here. So there's another folder in here, this is the substituents folder. And it is simply a folder, it's simply to help identify the differences between the substituent model states and the other regular type model states.

So I'm going to right click here, and I'm going to show you the difference in terms of creating. So we're not going to click New, we're going to click New substitute, and here are those three options that I just talked about, and we're going to click simplify. And this is that dialog box that you're going to use, and this is the replacement for the shrink wrap functionality. If you just wanted to use what was previously called shrink wrap, you can absolutely do that outside of substitute model states. It's using this simplified command up here on the ribbon. So it's on the simplification panel. So you can access the exact same commands.

So when you create your substitute model state using simplify, you want to work from top down. So I'm going to expand out this input area. And this is where that optional model state really comes in handy here. So I am going to actually leverage the use of that model state in the creation of my substitute. So now what it's doing is it's going to leverage that as the starting point geometry. I could also have customized a design view or a positional representation, but right now I'm just sticking with the model state.

Just like shrink wrap, you can replace with envelopes. I'm not going to do that at this point, you can exclude components. So if you had a really large assembly, you could certainly go through and remove any maybe internal components, things that you don't need to show to help you simplify the geometry that's going to be created. Now the next one is this remove features. And this is where creating that model state prior to doing the simplification is really important. You can see the list of feature types here, the holes fillets chamfers. It's really allowing you to customize certain types of features and certain types of geometry shapes. However, it doesn't give you the ability to actually go through and say, well, I'm going to turn off this extrusion and this circular pattern.

And if you remember, that's what I did in suppressing the features in that model state I created. So instead of customizing the remove features there, I did the exact same thing with more flexibility, with the geometry types by creating this model state. So that's why it's optional. You don't have to do it, but it is a nice way if you wanted to remove features that don't get grouped in with the remove features area. I'm not going to remove any features so I'm just going to close that up. And then finally the output area, and this is really where you're going to create the file.

So I'm going to go in here and I'm just going to quickly select the default template. I'm going to leave the default name, location, but keep the bomb structure as normal. And I'm just going to generate this as surface geometry. So you'll be able to see the difference in the icons when I create this. Then click OK, and you can see how it's generating that substitute. Now you can see over in the browser again, lots of stuff happened. The substitute folder now has a substitute model state, and that's that default name that I just used when I created it. And more importantly, what you can see here is I have a single part file now.

So this housing simplify is actually a part file that was created and exists now on my hard drive. It's a service model as you can see from the icon. If I was to flip back up into master, you can see that it goes back to those three components. So that's what that optional is really valuable for is that when you're to simplify and remove some of the features that don't get grouped inside the remove features area. So I hope that explains it for you. So now I'm just going to save this and return back up into the top level pencil. And here now you can see that I have all those model states existing. I have this substitute down there, everything is happening within here. But again to control it from the top level I'm going to have to create a new model state up here.

I'm not going to rename that just for sake of getting through this. But what I can do here is I could use the link model states to activate the right simplification, or I can just double click on it. So now you can see that with this model state-- maybe I'll just quickly rename it housing simplified, --you can see that this housing gets brought in. And you can see by the icons it's a single part file instead of all of the components. If I go back to master, you can see how the icon changes and it's showing that it's a sub assembly again with multiple components.

So this is how you can use the substitute model states to help work with large assemblies in your company setting. So now again, I'm going to flip back over into my presentation, and we'll continue on with our next objective, and this is actually the final objective. Now that we have learned how to create parts in assembly design model states, I want to show you how you can leverage those inside of your drawings and your presentations.

So in terms of a drawing, you can use model states to create drawing views simply by selecting the name of the drawing view in the drawing view dialog box. So you can see on the left hand side here, I have a pull down list active, it highlights all the model states that I have existed. So your drawing view can represent any one of those model states. And then additionally, if you then use one of those drawing views to create a parts list, that parts list accurately reflects the information from that parent view.

So in the image I have here, I have a couple of different parts lists here. And you can see one of them has four vises assemble. One of them has only one vise and the parts list update. And that was both done with model states. In terms of a part file, so if you actually are representing a part file inside of your model, you can also leverage the use of general tables to create a table that actually details all of the information that was customized in the different model states.

So I've shown a little example here. You can see the three different sizes of vise base that I brought in here. And you can see the different material types that have been assigned, as well as the different links, whether the holes have been suppressed and then if they exist what size the holes are. And that's all. I'm done with general tables. And then finally, the last one here, how to use model states in a presentation. You can absolutely create every scene in your presentation with a unique model state. So if you already have an assembly open, you'll want to activate the model state, and then if you simply right click to Create the presentation, it automatically will create that first scene with the active model state.

Now if you're actually creating your presentation using the file new option and then selecting the presentation template, you can select the model that you want, and then you can go into the Options dialog box and actually select the actual model state that you want to use in this scene. In addition, as you want to add more scenes to your presentation, you can also leverage picking different model states. So it's a great way maybe to show different design variations on manufacturing stages, that type of thing.

So now again, want to go back into Inventor and just finish up this presentation. And what we're going to do here is we're going to focus on the drawing side of things. I'm going to go back up into the vise assembly, and I'm going to open up the vise short model state. And doing that, I'm just going to right click Create drawing view, and I'm just going to use the default template here. And I'm just going to add a couple of quick views here. And you can see here, the model state because I created the drawing with that model state active, it automatically defaults to this.

I can certainly choose a different one if I wanted to. For now I'm just going to leave the default there and click OK. And now you can see some views have been added. I'm also going to add my parts list in here, and I'm just going to choose that base, view and place my view. And you can see how the parts list reflects accurately what's going on. So if you see here this quantity is zero, if you remember back when I created the model states at that assembly level, I suppressed some of those components, those internal screw components in that vise-short.

Now if I maintain in the drawing here and I want to go over and modify this, I'm going to change this over to vise-medium, you'll see the view got a little bigger, material properties changed, yes I want to replace things. Now if I Zoom in here, you can see that I actually have the four components again. So as I mentioned in the presentation, the parts list always accurately reflects the information in the model state.

And then lastly, I'm going to just flip over into a drawing. I've already created the views on, and you can see this is just the three model states for that base. And here what I want to do is just show you that general table functionality. So I'm going to just click General table, select one of these as the parent view, I'm going to go in and decide and assign what my columns are going to be. So add them all for now.

To customize my table, click OK, and then place my table, and now you can see how the table has come in with that information, with everything that I wanted to see. Just like any general table, I can go in and customize this, and customize the headers. I could rename things, change them to some kind of custom. Instead of hole four, I might want to say mounting holes. I can make all those changes. I can go in, remove one of the columns if I wanted to simplify things. So that same functionality that's always been available inside general tables is available when you're leveraging the data from your model states. So with that, I'm going to flip over and finish things up.

So the final presentation there ended kind of-- brought everything together with how we could leverage the model states into drawing. So we went through and we talked about how you create them both in parts and assemblies. We talked about the nuances of if you're going to be creating model states within a sub assembly, how you actually have to go and specifically open that sub-assembly in another window and create the model states there. We talked about the linking. So manually linking them by simply double clicking or more importantly, the linked model states, which is super valuable if you have lots of model states and multiple levels of your assemblies.

And then we also focused on the substitute model states, and we specifically focused on the simplify functionality that replaced shrink wrap. So a really nice functionality there. The other two options that derive assembly and the select part file, those two functionalities were also there as well for levels of detail. So there's no differences there, really it was the simplify that's changed up with the fact that shrink wrap has been removed. So I certainly want to spend time on that.

So with that, I hope that we covered everything you wanted to learn. And thank you so much for taking the time to watch my presentation, and I hope it really gives you a better understanding of this new functionality of model states. As a reminder, please take a look at my [INAUDIBLE] handout. There's lots of great information in there for you to review and it's available on my class page. And thanks again, and I really hope that I get to see you in person next year.

______
icon-svg-close-thick

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

icon-svg-close-thick

THIRD PARTY SERVICES

Learn more about the Third-Party Services we use in each category, and how we use the data we collect from you online.

icon-svg-hide-thick

icon-svg-show-thick

Strictly necessary – required for our site to work and to provide services to you

Qualtrics
We use Qualtrics to let you give us feedback via surveys or online forms. You may be randomly selected to participate in a survey, or you can actively decide to give us feedback. We collect data to better understand what actions you took before filling out a survey. This helps us troubleshoot issues you may have experienced. Qualtrics Privacy Policy
Akamai mPulse
We use Akamai mPulse to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Akamai mPulse Privacy Policy
Digital River
We use Digital River to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Digital River Privacy Policy
Dynatrace
We use Dynatrace to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Dynatrace Privacy Policy
Khoros
We use Khoros to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Khoros Privacy Policy
Launch Darkly
We use Launch Darkly to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Launch Darkly Privacy Policy
New Relic
We use New Relic to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. New Relic Privacy Policy
Salesforce Live Agent
We use Salesforce Live Agent to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Salesforce Live Agent Privacy Policy
Wistia
We use Wistia to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Wistia Privacy Policy
Tealium
We use Tealium to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Tealium Privacy Policy
Upsellit
We use Upsellit to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Upsellit Privacy Policy
CJ Affiliates
We use CJ Affiliates to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. CJ Affiliates Privacy Policy
Commission Factory
We use Commission Factory to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Commission Factory Privacy Policy
Google Analytics (Strictly Necessary)
We use Google Analytics (Strictly Necessary) to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Google Analytics (Strictly Necessary) Privacy Policy
Typepad Stats
We use Typepad Stats to collect data about your behaviour on our sites. This may include pages you’ve visited. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our platform to provide the most relevant content. This allows us to enhance your overall user experience. Typepad Stats Privacy Policy
Geo Targetly
We use Geo Targetly to direct website visitors to the most appropriate web page and/or serve tailored content based on their location. Geo Targetly uses the IP address of a website visitor to determine the approximate location of the visitor’s device. This helps ensure that the visitor views content in their (most likely) local language.Geo Targetly Privacy Policy
SpeedCurve
We use SpeedCurve to monitor and measure the performance of your website experience by measuring web page load times as well as the responsiveness of subsequent elements such as images, scripts, and text.SpeedCurve Privacy Policy
Qualified
Qualified is the Autodesk Live Chat agent platform. This platform provides services to allow our customers to communicate in real-time with Autodesk support. We may collect unique ID for specific browser sessions during a chat. Qualified Privacy Policy

icon-svg-hide-thick

icon-svg-show-thick

Improve your experience – allows us to show you what is relevant to you

Google Optimize
We use Google Optimize to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Google Optimize Privacy Policy
ClickTale
We use ClickTale to better understand where you may encounter difficulties with our sites. We use session recording to help us see how you interact with our sites, including any elements on our pages. Your Personally Identifiable Information is masked and is not collected. ClickTale Privacy Policy
OneSignal
We use OneSignal to deploy digital advertising on sites supported by OneSignal. Ads are based on both OneSignal data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that OneSignal has collected from you. We use the data that we provide to OneSignal to better customize your digital advertising experience and present you with more relevant ads. OneSignal Privacy Policy
Optimizely
We use Optimizely to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Optimizely Privacy Policy
Amplitude
We use Amplitude to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Amplitude Privacy Policy
Snowplow
We use Snowplow to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Snowplow Privacy Policy
UserVoice
We use UserVoice to collect data about your behaviour on our sites. This may include pages you’ve visited. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our platform to provide the most relevant content. This allows us to enhance your overall user experience. UserVoice Privacy Policy
Clearbit
Clearbit allows real-time data enrichment to provide a personalized and relevant experience to our customers. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID.Clearbit Privacy Policy
YouTube
YouTube is a video sharing platform which allows users to view and share embedded videos on our websites. YouTube provides viewership metrics on video performance. YouTube Privacy Policy

icon-svg-hide-thick

icon-svg-show-thick

Customize your advertising – permits us to offer targeted advertising to you

Adobe Analytics
We use Adobe Analytics to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Adobe Analytics Privacy Policy
Google Analytics (Web Analytics)
We use Google Analytics (Web Analytics) to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Google Analytics (Web Analytics) Privacy Policy
AdWords
We use AdWords to deploy digital advertising on sites supported by AdWords. Ads are based on both AdWords data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that AdWords has collected from you. We use the data that we provide to AdWords to better customize your digital advertising experience and present you with more relevant ads. AdWords Privacy Policy
Marketo
We use Marketo to send you more timely and relevant email content. To do this, we collect data about your online behavior and your interaction with the emails we send. Data collected may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, email open rates, links clicked, and others. We may combine this data with data collected from other sources to offer you improved sales or customer service experiences, as well as more relevant content based on advanced analytics processing. Marketo Privacy Policy
Doubleclick
We use Doubleclick to deploy digital advertising on sites supported by Doubleclick. Ads are based on both Doubleclick data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Doubleclick has collected from you. We use the data that we provide to Doubleclick to better customize your digital advertising experience and present you with more relevant ads. Doubleclick Privacy Policy
HubSpot
We use HubSpot to send you more timely and relevant email content. To do this, we collect data about your online behavior and your interaction with the emails we send. Data collected may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, email open rates, links clicked, and others. HubSpot Privacy Policy
Twitter
We use Twitter to deploy digital advertising on sites supported by Twitter. Ads are based on both Twitter data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Twitter has collected from you. We use the data that we provide to Twitter to better customize your digital advertising experience and present you with more relevant ads. Twitter Privacy Policy
Facebook
We use Facebook to deploy digital advertising on sites supported by Facebook. Ads are based on both Facebook data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Facebook has collected from you. We use the data that we provide to Facebook to better customize your digital advertising experience and present you with more relevant ads. Facebook Privacy Policy
LinkedIn
We use LinkedIn to deploy digital advertising on sites supported by LinkedIn. Ads are based on both LinkedIn data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that LinkedIn has collected from you. We use the data that we provide to LinkedIn to better customize your digital advertising experience and present you with more relevant ads. LinkedIn Privacy Policy
Yahoo! Japan
We use Yahoo! Japan to deploy digital advertising on sites supported by Yahoo! Japan. Ads are based on both Yahoo! Japan data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Yahoo! Japan has collected from you. We use the data that we provide to Yahoo! Japan to better customize your digital advertising experience and present you with more relevant ads. Yahoo! Japan Privacy Policy
Naver
We use Naver to deploy digital advertising on sites supported by Naver. Ads are based on both Naver data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Naver has collected from you. We use the data that we provide to Naver to better customize your digital advertising experience and present you with more relevant ads. Naver Privacy Policy
Quantcast
We use Quantcast to deploy digital advertising on sites supported by Quantcast. Ads are based on both Quantcast data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Quantcast has collected from you. We use the data that we provide to Quantcast to better customize your digital advertising experience and present you with more relevant ads. Quantcast Privacy Policy
Call Tracking
We use Call Tracking to provide customized phone numbers for our campaigns. This gives you faster access to our agents and helps us more accurately evaluate our performance. We may collect data about your behavior on our sites based on the phone number provided. Call Tracking Privacy Policy
Wunderkind
We use Wunderkind to deploy digital advertising on sites supported by Wunderkind. Ads are based on both Wunderkind data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Wunderkind has collected from you. We use the data that we provide to Wunderkind to better customize your digital advertising experience and present you with more relevant ads. Wunderkind Privacy Policy
ADC Media
We use ADC Media to deploy digital advertising on sites supported by ADC Media. Ads are based on both ADC Media data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that ADC Media has collected from you. We use the data that we provide to ADC Media to better customize your digital advertising experience and present you with more relevant ads. ADC Media Privacy Policy
AgrantSEM
We use AgrantSEM to deploy digital advertising on sites supported by AgrantSEM. Ads are based on both AgrantSEM data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that AgrantSEM has collected from you. We use the data that we provide to AgrantSEM to better customize your digital advertising experience and present you with more relevant ads. AgrantSEM Privacy Policy
Bidtellect
We use Bidtellect to deploy digital advertising on sites supported by Bidtellect. Ads are based on both Bidtellect data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Bidtellect has collected from you. We use the data that we provide to Bidtellect to better customize your digital advertising experience and present you with more relevant ads. Bidtellect Privacy Policy
Bing
We use Bing to deploy digital advertising on sites supported by Bing. Ads are based on both Bing data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Bing has collected from you. We use the data that we provide to Bing to better customize your digital advertising experience and present you with more relevant ads. Bing Privacy Policy
G2Crowd
We use G2Crowd to deploy digital advertising on sites supported by G2Crowd. Ads are based on both G2Crowd data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that G2Crowd has collected from you. We use the data that we provide to G2Crowd to better customize your digital advertising experience and present you with more relevant ads. G2Crowd Privacy Policy
NMPI Display
We use NMPI Display to deploy digital advertising on sites supported by NMPI Display. Ads are based on both NMPI Display data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that NMPI Display has collected from you. We use the data that we provide to NMPI Display to better customize your digital advertising experience and present you with more relevant ads. NMPI Display Privacy Policy
VK
We use VK to deploy digital advertising on sites supported by VK. Ads are based on both VK data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that VK has collected from you. We use the data that we provide to VK to better customize your digital advertising experience and present you with more relevant ads. VK Privacy Policy
Adobe Target
We use Adobe Target to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Adobe Target Privacy Policy
Google Analytics (Advertising)
We use Google Analytics (Advertising) to deploy digital advertising on sites supported by Google Analytics (Advertising). Ads are based on both Google Analytics (Advertising) data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Google Analytics (Advertising) has collected from you. We use the data that we provide to Google Analytics (Advertising) to better customize your digital advertising experience and present you with more relevant ads. Google Analytics (Advertising) Privacy Policy
Trendkite
We use Trendkite to deploy digital advertising on sites supported by Trendkite. Ads are based on both Trendkite data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Trendkite has collected from you. We use the data that we provide to Trendkite to better customize your digital advertising experience and present you with more relevant ads. Trendkite Privacy Policy
Hotjar
We use Hotjar to deploy digital advertising on sites supported by Hotjar. Ads are based on both Hotjar data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Hotjar has collected from you. We use the data that we provide to Hotjar to better customize your digital advertising experience and present you with more relevant ads. Hotjar Privacy Policy
6 Sense
We use 6 Sense to deploy digital advertising on sites supported by 6 Sense. Ads are based on both 6 Sense data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that 6 Sense has collected from you. We use the data that we provide to 6 Sense to better customize your digital advertising experience and present you with more relevant ads. 6 Sense Privacy Policy
Terminus
We use Terminus to deploy digital advertising on sites supported by Terminus. Ads are based on both Terminus data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Terminus has collected from you. We use the data that we provide to Terminus to better customize your digital advertising experience and present you with more relevant ads. Terminus Privacy Policy
StackAdapt
We use StackAdapt to deploy digital advertising on sites supported by StackAdapt. Ads are based on both StackAdapt data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that StackAdapt has collected from you. We use the data that we provide to StackAdapt to better customize your digital advertising experience and present you with more relevant ads. StackAdapt Privacy Policy
The Trade Desk
We use The Trade Desk to deploy digital advertising on sites supported by The Trade Desk. Ads are based on both The Trade Desk data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that The Trade Desk has collected from you. We use the data that we provide to The Trade Desk to better customize your digital advertising experience and present you with more relevant ads. The Trade Desk Privacy Policy
RollWorks
We use RollWorks to deploy digital advertising on sites supported by RollWorks. Ads are based on both RollWorks data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that RollWorks has collected from you. We use the data that we provide to RollWorks to better customize your digital advertising experience and present you with more relevant ads. RollWorks Privacy Policy

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.