[Autodesk Revit 2020.2 LT X64 2018
Luther Lazaro
Hi. I have a revit 2020 and bim 360 subscription and we are a team of 3, with me working remotely. I am trying to access the cloud shared model, I can see the files but they are greyed out and I am unable to access them. I checked my team members' autodesk account and they are exactly the same as mine but its just me who is facing this issue. It would be great if someone could help me solve this as I have already spent 2 days trying to make this work with no positive result. Thanks
I am new to using Revit and I am just trying to figure out how it works to be honest. I have made a 2 floor building in ACAD ARCH 13 and when I import the DWG files into Revit, they just show the 2D line drawings even when I look in 3D mode. Do I have to re make all of the walls and such in Revit or am I missing a step to import all of the windows, doors, and wall heights?
Doesn't that defeat the purpose of them selling two different softwares that are supposed to play well togeather? I guess I will need to learn Revit eventually, but I have been using ACAD since R12 when my mom showed me how to draft. I am a mechanical engineer by trade and use Solidworks for that, this is more of a hobby for me since I get the student versions for free because I am a doctoral student. Thank you for your quick reply though.
Autocad and Revit are to each other like a horse and buggy and the Ford Model T. You cannot make the Model T work by feeding it oats. I don't recall any promise made by Autodesk that Acad and Revit would work together seamlessly. Revit is not even a product of Autodesk. Revit was an independent system like Microstation. They were bought out by Autodesk and added to the Autodesk product line. Revit existed for years before Autodesk, and the founding principle of Revit was to create a completely new, state of the art system that was not encumbered by maintaining compatibility with the past. Having been taken over by their former competitor, the focus on that principle has blurred somewhat, but the two have many inherent incompatibilities.
Well I wasn't asking for Revit to be more like ACAD, that would be silly. Perhaps I miss understood how Revit fits into the world of design. This week was the first time I had ever heard of Revit. So is Revit essentially a new way to produce drawings in a more 3D representitive way?
Well, in Revit you model the project, from scratch. It does not start by importing a model from another program. As it was said in a previous post, Revit was developed by another company, using a completely different approach, and then that company was adquired by Autodesk.
The goal of Building Information Management (BIM) is to eliminate drawings altogether. In Revit, drawings are a by-product of the modeling process. It is a database of building parts. Drawings are merely a report of the contents of the database, the same way your checking statement from the bank is a report on the status of your finances.
One of the first things new users discover is the ease of creating sections. In the past, sections were difficult drawings to produce and most architects rationed their use in the drawing set. With Revit, you could have a building section every six inches if you want!
Hello guy's, your articles are eye opening for me. I see now why I can't get things done the autocad way. I'm new to revit, old to architectural desktop 2005. Trying to get a plan view of a project I am modeling. It seem to be stuck in 3D view (top). I want it have it back in a plan view that shows windows & doors so that I can continue to draws lines & symbols to represent things like electrical outlets etc. and then place a plan on a drawing sheet to be printed out for the client. Where can i go to get help with this?
What you have done is rotate the 3D to orthogonal. Your eye is way up in the air and you are seeing a bird's eye plan-view of the roof. What you really want is a horizontal plan-section through the model.
Go to the browser and click on level 1 or level 2. This will get you back to an interior floor plan. I am assuming you made your file using the default Revit template. This template creates a level 1 and a level 2 floor plan. After that you are on your own. You can make additional levels, but you will have to go to view/plan and actually make a floor plan view in order for you to see it in plan.
When you look at a building section, the levels will show as annotation. They will be either black or blue. One color means a plan was created and the other means no plan was created. (I forget which is which)
sir/mam I have a question a have a problem with my revit I don't know what to do to appear the 4 arrows on the revit screen so I can work on elevation grids and I can add floors to my drawings.thats my problem as of now.thanks for the reply.
I set up a project months ago from the template we use but I wasn't signed into Autodesk at the time. (M&E Consultants) Now, I need to be signed into Autodesk to use A360, however my username in Revit has changed. There is now LBZJZ after my mane. I've now returned to work on this particular project and since then my username is different. I cannot edit particular elements and views until I re-save and Relinquish as my previous username... I've tried to return my Autodesk username to the original name however it is taken, hence the letters after my name.I can't edit or delete anything until I synchronize as the original user. Has anyone ever come across this before?
Cheers for the reply. I'll keep this in mind for future. I did figure out the issue though. A few weeks back I logged onto a colleagues computer for a student to use (which I forgot about). The student was then logged in as me, but without being logged into Autodesk, hence the reason revit was recognising two different names. To solve this I just logged my colleagues computer again. Syncronised and closed the model, then deleted the local file from my colleagues computer and logged off their computer again. Took a bit of head scratching but it's sorted now.
in the early days I thought that ElementId was a stable way of finding elements in a document, then I learned that UniqueId was the proper way.
But I havent been able to find enough coherent information about it to really understand it and I've been reading lately that we should use the uniqueId as a identifier in multifile projects (multiple centralfiles), because its only guaranteed to be unique in one centralfile.
This is what I've learned so far (From Jeremy Tammiks Blog among others):
The UniqueId 40 characters long and is made up from 2 parts, the first is internally called the EpisodeId and the second is the hexadecimal representation of the elementId. I've read that people complain about the fact that two revit files from the same template will have the same UniqueIds for the elements that are created in the template. So I guess that the EpisodeId cannot be used as a "file guid".
However, its stated by Arnost Lobel that the UniqueIds purpose (one of many?) is to have a stable way of identifying elements in a workshared environment, because the elementId of an element can change.
Sigh.. I truly believe we have made a disservice to our Revit users when we named UniqueId the way we did, for it seems to keep on being misunderstood in spite of many of us trying to shed more light into the problems with identifying model elements. I'll try again to straighten up some of the confusion, and my hope is that I'll make it better, not worse.
The most important part of the sentence is the "a" in "a document", since the purpose of both kinds of IDs is to identify elements in a single model, not in a bunch of models. In other words: none of the IDs can uniquely identify elements across unrelated documents in spite of the name it was given to the UniqueID class. Universal uniqueness of identifiers is simply something that cannot be done. If one takes an existing file and makes a copy of it, no one would probably expect elements change their Ids in that copied file.
Regular Ids (integers) can identify elements in a model uniquely as long as the model is not work-shared. It is because Revit does not change the Ids after they were issued, and it also always increments the Ids before assigning them to new elements. That means Ids are never reused. If an element is deleted, its Id will not be used for anything else.
Consider two users, UA, and UB. One creates an empty central file. Then both users create their respective local files from it. Now, say UA creates a wall. It will be assigned Id = 1005 (for example). If UB also creates one wall it will also be given Id = 1005, since both users started off with the same file and Revit increments element Ids linearly. Let's continue: UA saves to central, thus her wall gets there first with its original Id (1005). If UB then syncs, first the wall from the other user will be brought in with it's original Id. Revit will notice that the same Id already exist locally. Since all elements must have unique Ids within a file, something's got to give; Revit takes the UB's wall and assigns it a new Id, say 1006 and uploads that wall to the central file. After UA gets the latest too, both users and the central file as well will have two walls with Ids 1005 and 1006, respectively.
Unique Ids (strings) can identify elements uniquely even in a work-shared file. What this basically means is that, unlike regular Ids which may collide when two local versions are merged together and thus one (or more) of the Ids must be re-issued (as I illustrated in the aforementioned example), Unique Ids do not collide, therefore they do not have to be reissued; they merge with no problem.
An external application creates a new Beam element in a local file. It takes and stores its unique Id - say is "ABCD-1234" (a string!!). Then the user goes on making more changes while his co-workers make even more changes in their local files. At some point they all sync with the central file. If, after that point in time the external application operating on the first user's computer asks for an element to be fetched by providing its UniqueId = "ABCD-1234", the application will obtain the very same Beam element, providing it still exists.
795a8134c1