Move project to origin point

Anonymous

Move project to origin point

Anonymous
Not applicable

I am having issues with my template for few months and I can't find the cause of the problem.

 

I am coming from the thread below

 

https://forums.autodesk.com/t5/revit-architecture-forum/template-corrupted-with-graphic-issues/td-p/...

 

Today, I have learn that apart of the project base point, and survey point, the revit files have also a origin point hidden. I thought that the 20km rule was between the model and the project base point, but apparently it is between the origin point of the revit file, and the model (I don't know if it is different rule, I had just misunderstood the rule at the beginning).


I have seen the issue with the hatch contour is resolved once you move the hatch close to the origin point (It was already in the project base point, but the project base point was like 12km away of the origin point), so in order to make another test and see if that is the cause of all the problems in the template, I want to move the whole project, model, details, everything, close to the origin.

Does anybody know how to do it? how to move a model close the origin point??

 

Regards

 

0 Likes
Reply
Accepted solutions (1)
29,454 Views
98 Replies
Replies (98)

barthbradley
Consultant
Consultant

@ToanDN wrote:
If your statement reads : “You can move the Revit Project Base Point and Survey Point away from the "WCS" Origin and later find the Origin by Linking a CAD Origin to Origin.” then everyone is on the same page.

Autodesk’s equates the Project Coordinate System (of which the Project Base Point is the origin) to the World Coordinate System (WCS). That’s what I mean by “WCS”. By “Origin”, I mean the “Internal Origin”; also known as the Project Base Point’s “Startup Location”.  I am not meaning Survey Point at all.

 

https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2018/EN...

 

https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2018/EN...

0 Likes

ToanDN
Consultant
Consultant
Sounds reasonable.

So your statement can read: “You can move the Revit Project Base Point Symbol away from its Startup Location and later find the Startup Location by Linking a CAD Origin to Origin.”
0 Likes

barthbradley
Consultant
Consultant

@ToanDN wrote:
Sounds reasonable.

So your statement can read: “You can move the Revit Project Base Point Symbol away from its Startup Location and later find the Startup Location by Linking a CAD Origin to Origin.”

Careful @ToanDN: our wavelength's are dangerously close to each other. I'm in agreement with that statement. 

0 Likes

SteveKStafford
Mentor
Mentor

Quote: "You sound frustrated when you say that you “keep harping on”.

Nah, not really. I'm more curious why I haven't been able to get my points across to you.

If you're still game, how about a series of questions (based on using a stock template) to see if we are on the same page?

True or False...

...moving either the PBP or the SP while the symbols are unclipped does not move the their related coordinate systems?
...moving either the PBP or the SP while the symbols are clipped does move their related coordinate system too?
...the project coordinate system and survey coordinate systems are not connected, moving one does not alter or affect the other?
...the internal origin (Revit's documentation calls it that now) cannot be moved.
...moving the PBP while unclipped 50' west does not change the Project Coordinate System origin location?
...after moving the PBP 50' west, while clipped, placing a spot coordinate (assigned to Relative) will report N=0 and E = 50' at the SP?
...after moving the PBP 50' west, while clipped, placing a spot coordinate (assigned to Relative) will report N=0 and E = 0' at the PBP?
...after moving the PBP 50' west, while clipped, the PBP reports E/W -50'?
...after moving the PBP 50' west, while clipped, the SP reports E/W 0?
...the PBP (when selected) reports coordinate values related to the Survey Coordinates origin when it has been moved whether clipped or not?
...the PBP cannot be moved away from the Internal Origin location while clipped?
...if someone moves the PBP and SP 50 miles from their original location while unclipped both coordinates system origin's remain where they started?
...Linking a DWG using Auto - Origin to Origin, the WCS origin of the DWG lands at the PBP location, if it has not been moved while unclipped?
...Linking a DWG using Auto - Origin to Origin, the WCS origin of the DWG lands away from the PBP if it has been moved while unclipped?
...Linking a DWG using By Shared Coordinates will place the WCS origin of the DWG at the Origin of the Shared Coordinate system?

Oh, did you mean to show me my own screencast? At this point I don't even remember recording it, or why I did. Was it relevant to all this?


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

0 Likes

SteveKStafford
Mentor
Mentor

@ToanDN wrote:
So your statement can read: “You can move the Revit Project Base Point Symbol away from its Startup Location and later find the Startup Location by Linking a CAD Origin to Origin.”

Why is the CAD file necessary to the conversation? The Move to Start Up location option is sufficient to return the PBP to the internal origin, to "find it", assuming someone thought it is/was lost?


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

0 Likes

ToanDN
Consultant
Consultant
It is a simple method in case someone needs to know where the Startup location is without moving the PBP back to it.
0 Likes

barthbradley
Consultant
Consultant

Really, Steve? True/False? I thought we already established we’re not of like minds. I would think you would want to understand where I’m coming from, especially if my answers differ from yours. But, I’ll play along. I’m curious to know where you’re going with this.

 

PEN UP. BEGIN TEST:

 

  1. Moving either the PBP or the SP while the symbols are unclipped does not move their related coordinate systems?

True and False.

 

I know the “textbook” says False; that moving the PBP while it is unclipped, “repositions the Project Coordinate System” – but I don’t see it that way. I consider the PBP Startup Location to be the center of the Project Coordinate System universe, and it does not move. Both markers are traveling freely over their respective systems when unclipped; so my final answer is: True.

 

  1. Moving either the PBP or the SP while the symbols are clipped does move their related coordinate system too?

Again: True and False.

 

While their respective coordinate systems appear not to be moving, the Project coordinate system is actually moving in the opposite direction when the Survey point is moved? I mean, if the “fixed” internal point is always located at the SP’s zero origin; how else would describe what’s happening behind the scene?  

 

  1. The project coordinate system and survey coordinate systems are not connected, moving one does not alter or affect the other?

False.

 

They are connected at the hip.

 

  1. The internal origin (Revit's documentation calls it that now) cannot be moved.

 Ha! So we’re back on this one, huh? The answer could be True or False, depending on what you’re considering the “Internal Point”. Are you referring to that “Mathematical Center” you spoke of before (the fixed one that seems to move, but actually doesn’t) – or, are you referring to the Startup Location/Internal Point which can be moved relative to that fixed “Mathematical Center”?

                                                                                                 

  1. Moving the PBP while unclipped 50' west does not change the Project Coordinate System origin location?

True; it doesn’t change the PBP Startup Location.

 

  1. After moving the PBP 50' west, while clipped, placing a spot coordinate (assigned to Relative) will report N=0 and E = 50' at the SP?

 Depends; but yes, it’s “relatively” True.  

 

  1. After moving the PBP 50' west, while clipped, placing a spot coordinate (assigned to Relative) will report N=0 and E = 0' at the PBP?

 Depends; but if moving from default startup position: then True.

 

  1. After moving the PBP 50' west, while clipped, the PBP reports E/W -50'?

Depends; but if moving from default startup position: then True.

 

  1. Afer moving the PBP 50' west, while clipped, the SP reports E/W 0?

Depends; but if moving from default startup position: then True.

 

  1. The PBP (when selected) reports coordinate values related to the Survey Coordinates origin when it has been moved whether clipped or not?

True.

 

  1. The PBP cannot be moved away from the Internal Origin location while clipped?

 True.

 

  1. If someone moves the PBP and SP 50 miles from their original location while unclipped both coordinates system origin's remain where they started?

 True. Einstein’s Theory of Relativity proves it so.  

 

  1. Linking a DWG using Auto - Origin to Origin, the WCS origin of the DWG lands at the PBP location, if it has not been moved while unclipped?

 True. It lands on the PBP Startup Location.  

 

  1. Linking a DWG using Auto - Origin to Origin, the WCS origin of the DWG lands away from the PBP if it has been moved while unclipped?

 Huh? It lands on the PBP Startup Location.  

 

  1. Linking a DWG using By Shared Coordinates will place the WCS origin of the DWG at the Origin of the Shared Coordinate system?

 Now, this one sounds like a trick question. But, my short and sweet answer is: False.

 

END TEST. PEN DOWN.

0 Likes

barthbradley
Consultant
Consultant

Correction: #11 should read TRUE OR FALSE.  TRUE if "Internal Origin" means the "Startup Location/Internal Origin" like I thought. But, FALSE if "Internal Origin" means the fixed "Internal Origin" located at Survey Point 0,0,0. 

0 Likes

barthbradley
Consultant
Consultant

Clarification on #2:  The wording: ”appear not to be moving” should read “appear to be moving”. So, yes: moving either the PBP or the SP while the symbols are clipped does move their related coordinate systems too.

 

But is that really TRUE?

 

The point I was making, which I think is important to understand; is that the fixed Internal Origin – which is located at the SP’s zero origin – never moves.  So, for example: if the Survey Point is reading 0,0,0 and it is moved while clipped to a different on the screen; it is the Project Coordinate System’s relationship to the fixed Internal Origin that is changed – not the Survey Point’s, which still reads 0,0,0.

 

That is the reason why I believe your #2 question could be answered both TRUE and FALSE.   

0 Likes

SteveKStafford
Mentor
Mentor

@barthbradley I wrote each intending them to be a True statement.

 

I fully understand that when someone understands a subject well such questions can be exceptioned by anticipating conditions or exceptions that affect the True/False dichotomy. At their root, with the stated conditions, in my view they are all true statements.

 

I have tried, am trying, to understand what you've been writing. I did your exercises. I think at the root of it all we probably agree, it's our choice of words that pulls us in different directions. It is just more evidence that the process/experience Revit provides is too opaque still. FWIW, whether we agree on everything or anything isn't really why I've gone down this rabbit hole with you. It's as much for anyone else that is curious about it too.

 

Specifically...

 

I claim #1 is true because their coordinate systems are not moved while their symbol is unclipped, so says Revit help too. The subtle exception is that the alternate coordinate reference of Spot Coordinate Annotations that reference the PBP location does change when the PBP has been unclipped. The underlying Project Coordinate System does not change though. The origin remains intact, for either the SP or PBP as long as they are moved unclipped...the whole point of clipping and unclipping these symbols to begin with.

 

If #1 is true then the opposite is true, #2...because clipping reattaches the symbol to the coordinate system. Technically speaking the Internal Origin (what Revit's documentation calls it now) never changes or moves. The PBP while clipped and moved gives the appearance of being moved but it is only moving relative to the survey coordinate system. I imagine each system as two planes that float above or below one another.

 

#3 is True technically, they are not connected. Philosophically they are connected because Revit's positioning tools involves them both. Changes to one does not change the other however. How Revit displays information in the PBP and SP implies otherwise but that is different from an actual connection. By using that word (connection), I mean connected like my wrist is connected to my forearm and upper arm. None can move with affecting the others. I can alter one coordinate system without changing the other at all.

 

#4 Internal Origin IS the Startup Location, when you move the PBP away unclipped that is the ONLY time you can move the PBP back to Startup Location.

 

No depends responses are necessary in my view, based on the info I provided, they are all true and easy to reproduce in a test. I was curious to see if asking you to examine the results of moving them might make my earlier remarks clearer; about the nature of the symbols versus their underlying coordinate systems.

 

#13 The PBP startup location IS the Internal Origin. The only way the PBP invokes an alternate coordinate system is when it has been moved unclipped and the only way it can be observed or used in a practical way is through Spot annotation.

 

#14 It lands at the Internal Origin (Startup Location) if the PBP has been move elsewhere while unclipped.

 

#15 True, when a DWG is linked By Shared Coordinates Revit looks for a shared status, finding none it aligns the WCS origin of the file with the Survey Coordinate system's origin. This is quite helpful when stacking DWG file's that share the same WCS origin but only one can have Acquire Coordinates used to align the Survey Coordinate system.

 

____________________________________________________________________________

All that aside: I make the fundamental recommendations to anyone who cares or asks.

 

Survey Coordinate system, and its related marker the Survey Point, are for survey positioning.

Project Coordinate System, and its related marker the Project Base Point, should not be moved unclipped, no good reason to do it.

Store both markers in their unclipped state, can't harm the project as easily in this state.

 

And...don't worry about True North while starting a project, just make it easy to draw the building. Once a reliable Survey arrives then worry about True North. That's how Revit is designed at the outset.

 

Oh, you need to take the test again. You didn't put a start time and end time...thus invalidating your results. Speak to your school counselor about rescheduling the test. I'm sorry but we can only give you 80% credit for a test taken again. Thanks, the mgmt.  Smiley Happy

 

 

 

 

 

 


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

0 Likes

ToanDN
Consultant
Consultant

@SteveKStafford wrote:

____________________________________________________________________________

All that aside: I make the fundamental recommendations to anyone who cares or asks.

 

Survey Coordinate system, and its related marker the Survey Point, are for survey positioning.

Project Coordinate System, and its related marker the Project Base Point, should not be moved unclipped, no good reason to do it.

Store both markers in their unclipped state, can't harm the project as easily in this state.

 

 

 

  

 


Did you mean "CAN harm"?

0 Likes

SteveKStafford
Mentor
Mentor

No it is written as I meant it. Unclipped the symbols cannot harm the configuration of their related coordinate systems. It is far riskier to leave them clipped. Accidental or intentional but ill advised changes to their position will harm any position work that has been done already.

 

Technically a PBP moved while unclipped will affect any Spot annotation that has been used and referencing the PBP itself, not using the Survey Point or Relative options. That would be negatively affecting a project too.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

0 Likes

barthbradley
Consultant
Consultant

@Anonymous wrote:

 

 

#4 Internal Origin IS the Startup Location

 

 


The Internal Origin is NOT the same as the Startup Location.

 

There are two distinct hidden Origin Points in Revit; both defined in Autodesk documentation: 1) the System’s “Internal Origin”, which is fixed and never moves, and 2) the Project Base Point “Startup Location”, which Autodesk describes as the Origin Point of the Project Coordinate System, and equates it to AutoCAD’s WCS.  More importantly, that Origin Point (a.k.a. Startup Location) is ALWAYS relative to the Internal Origin Point. When the Project Base Point is moved while clipped (either manually or by using the Relocate Project tool), the Startup Location moves as well – and changes its relationship to the Internal Origin Point. Additionally, when you move the Survey Point while clipped, it too, changes the PBP Startup Location’s relationship to the Internal Origin.

 

This is all very easily confirmed by reading the Project Base Point’s coordinates at its Startup Location.

 

  1. Open a new template and go to the Site View.
  2. Move the clipped Project Base Point 100 feet East.
  3. Select the Project Base Point and note its E/W coordinates read: 100’-0”.
  4. Move the clipped Survey Point 100 feet West.
  5. Select the Project Base Point again and note its E/W coordinates now read: 200’-0”.

This is very important to understand, especially for @Anonymous, if he is to prevent what happened to him from happening again.  

0 Likes

SteveKStafford
Mentor
Mentor

Maybe we are getting somewhere, your steps done.

 

After moving 100' East, the Project Base Point (and any model that has been created) is in the same location it was before, it is still at the Internal Origin aka Startup Location. Move to Startup Option is disabled, unclip and it remains disabled. The PBP is still at the startup location, Internal Origin.

 

What happens when the PBP is moved East 100' is that the Project Coordinate system is shifted 100 East of the Shared Coordinate system. The Internal Origin (Startup Location) did not shift, the Survey Point and Shared Coordinate system did. The value you see in the PBP is a reference value, note the label: Shared Site. The 100' value references the origin of the SP/Shared Coordinate system. It's my opinion that this fact contributes to the confusion.

 

Then moving the SP clipped 100' West just shifts the Shared Coordinate system further way and the reference value of the PBP increases to 200'. All completely expected. Linked a DWG origin file again and it lands at the PBP.

 

There is no circumstance where we can move the PBP away from the Internal Origin while it is clipped.

 

The reason the original poster ran into trouble is that the PBP and SP were both moved very from from their origins while unclipped. This left their origins at the Startup Location and the symbols as far apart as whatever source survey or DWG file was that they were using influenced that action.

 

That's my take on it.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

0 Likes

ToanDN
Consultant
Consultant

@SteveKStafford wrote:

Maybe we are getting somewhere, your steps done.

 

After moving 100' East, the Project Base Point (and any model that has been created) is in the same location it was before, it is still at the Internal Origin aka Startup Location. Move to Startup Option is disabled, unclip and it remains disabled. The PBP is still at the startup location, Internal Origin. 

 


This is exactly what I have been saying from the very beginning.  

0 Likes

SteveKStafford
Mentor
Mentor

@ToanDN wrote:
This is exactly what I have been saying from the very beginning.  

Yes, I understand.

 

The PBP reporting a value that references the shared coordinate system's origin is, in my opinion, an unfortunate misdirection and unnecessarily confusing. It is also my opinion that it should report zero as long as it is at the Internal Origin/Startup Location and only report offset values relative to that location, not the shared coordinate system, when it has been moved unclipped.

 

In other words, moving the PBP unclipped East 100' should report 100' east not because it is east of the shared coordinate system but because the symbol has been moved 100' east of the internal origin/startup location. If it is moved East 100' while clipped it should still report zero for its offset, it hasn't actually moved. The only thing that changed is the project's position relative to the shared coordinate system lying underneath, it is 100' offset from that system...and only relevant in that context.

 

That critique written, I believe I understand why they did what they did though. Moving the Project Base Point while clipped does allow us to adjust the position the building relative to the survey coordinate system by merely interacting with the PBP (clipped) instead of moving the survey and then re-acquire coordinates from the survey, assuming the survey is brought to the building. The fact that it is possible to alter these things bi-directionally is quite Revity but makes it more difficult to contend with at the end of the day...again, my opinion.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

barthbradley
Consultant
Consultant

@SteveKStafford: Your deduction is flawed, because your premise is invalid. You’re starting with the premise that System’s Internal Origin is the same as the Project Coordinate System’s Origin (a.k.a. Startup Location). They are not.

 

Sorry, but at this point, I think we are going to have to agree to disagree.  But, it’s been fun. Thanks for the ride.  

 

Respectfully,

 

Barth

 

P.S. I remain a big fan of yours. 

0 Likes

SteveKStafford
Mentor
Mentor

I guess so, keep in mind the evidence you offered to prove your assertion doesn't.

 

Can you demonstrate a circumstance that you can separate the Internal Origin from the Startup Location? The last one doesn't.

 

  • Using Project Internal as the Coordinate System Basis for the following:
  • Start with a stock file draw four walls with one corner at the PBP. Export to DWG as file 1.
  • Move the PBP clipped 100' east, export to DWG. Save as File 2
  • Move the PBP unclipped 50' north, export to DWG. Save as File 3.
  • In AutoCAD attach all three files as External References and place them at the WCS origin.

They all land in the same location. If your steps resulted in shifting the Startup Location then the second file would land elsewhere.  The only way the File 2 (or 3) will land elsewhere is if the Coordinate System Basis is assigned to Shared during the Export to DWG.

 

I maintain that this bit is the crux of the misunderstanding...emphasis added...

 


@Anonymous wrote:

This is all very easily confirmed by reading the Project Base Point’s coordinates at its Startup Location


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

0 Likes

barthbradley
Consultant
Consultant

@SteveKStafford: I’m not seeing how that last exercise proves your premise valid; or mine invalid. All three exports are done with the Revit model in exactly the same spot: on the PBP Startup Location.  So consequently, they will all land in the same spot in AutoCAD. I would expect that. No surprises here.

 

 

But that aside, Steve, let’s say I agree with both your premises. 1) The System’s Internal Origin Point IS the Project Coordinate System’s Origin (a.k.a. Startup Location) and, 2) the System’s Internal Origin Point CANNOT be moved.

 

So, does that mean when you Relocate the Project, the Shared Coordinate System moves; NOT the Project Coordinate System?

 

If yes, then we’re fundamentally on the same page. You may be wired for AC, and I may be wired for DC– but, we’re both electrifying.  Ha!  But, seriously – you’ve broken through.  Congrats!  All your “harping” has paid off. I get where you’re coming from now. 

 

 

0 Likes

SteveKStafford
Mentor
Mentor

@Anonymous wrote:

So, does that mean when you Relocate the Project, the Shared Coordinate System moves; NOT the Project Coordinate System?


Yes, precisely. The Project Coordinate System and its Internal Origin/Startup Location never really moves. Only it's Project Base Point symbol can be moved, while un-clipped, away from the Internal Origin/Startup Location.

 

I'd considered creating a video explanation using props some time ago. This morning I noticed our cutting boards were suitable as metaphorical coordinate planes. Maybe this video will be useful?

 


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

Type a product name

______
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.