I recently had several conversations with customers regarding Revit LT vs Revit (follow link for exhaustive list), and why they might consider Revit instead of Revit LT on mostly architectural projects (it is generally understood that MEP and Structural disciplines need Revit, not Revit LT).
There is a large price difference, and Revit LT comes with AutoCAD LT thrown in, so it is a compelling (albeit technologically limited) purchase. Sometimes it may pay a practice to invest in mix between Revit and Revit LT in the office. If Revit LT can do the job, then the number and allocation of licenses is the overriding concern. Revit LT can open any Revit file, but the MEP and Structural modelling capability is removed or limited.
Visibility Graphics View Filters for Council Submission
We use visibility graphics view filters in Revit for a variety of reasons. One of the more important reasons is for overriding the visibility of walls on plans to indicate their status for council submission.
Revit LT does not have the ability to create visibility graphics view filters. If you were to achieve the same result as with Revit, you would have to use many wall families leveraging different materials or you would have to override eh graphics of every element in every view.
Visibility Graphics Override Revit Link Customization
Visibility Graphic Override limitations also play a role in another scenario where you may choose Revit over Revit LT. When coordinated views are printed, we often need to hide categories in the Linked file’s Visibility Graphics Overrides.
Revit LT does not have this capability. If one wanted to hide a category in a view, one would have to tab to every element in the category and hide the element in view. Hiding the category is not even an option.
Worksets
We use worksets in Revit for a variety of reasons, but on large projects they are indispensable. Revit files blow up 20 times their normal size in the computer’s ram (they are compressed files). We place a logical selection of elements on worksets so that we can selectively choose what data is switched on in not only our own model, but also the models that are linked into our models.
While it is possible to open a Revit central file in Revit LT (so long as one is working on one’s own) there is no way to manage the size of the file using worksets. The full size of the central file and the full size of the incoming links will blow up in your computer’s ram. If it is a large model, this federated model may be more than 5GB file size, meaning that you would need at least 100GB ram simply to work on the model without using your hard drive as virtual ram and slowing your computer to a crawl. Even worse, if you are dealing with a large skyscraper, each floor is generally generated as a model and are placed on their own worksets. You will have no control over which links come into your project when you open it, and the file with its links will almost certainly crash your computer.
Cloud Workshared Models
Cloud models are special because they can be linked easily and upgraded every year on the cloud by clicking a button.
While you can open a Revit central file using Revit LT, you can not do so as a cloud workshared model. At best you can save the file in a directory that is synchronized as a non-cloud workshared file (this is done automatically when you try to open it from the Autodesk Desktop Connector). These files cannot be accessed as a co-authoring team until it is re-initiated. There will also be issues linking them into other models (the link paths will be broken for other users). Someone with a full Revit license will therefore have to manage the process.
If you want to use Revit LT to save a Revit LT model as a cloud model, it must be as a non-workshared file.
Rendering
Revit can render still images and walkthroughs. It uses your processor to render and will max out the processor while it is rendering, effectively taking your computer off the production line. You also get a license of Twinmotion for free with your Revit license. You can use this for advanced renderings and movies. Alternatively, you have the option to purchase cloud tokens and to render online with Autodesk instead. You can also run the Add-ons for other rendering packages you may have purchased and use. These include Lumion, Enscape and V-Ray.
Revit LT can not render except of in the cloud. You can, at best, set a view to realistic mode. Beyond that you have the option to render in the cloud if you have cloud tokens and export a 3D DWG for render in something like Lumion. You cloud also open the Revit LT file in Twinmotion if you have a mix of Revit and Revit LT in the office.
Add-ons
The typical add-ons our users may find limiting include the Lumion add-on. It allows for a real time render vile a live link or the export of .DAE files. These allow Lumion to recognize the painted surfaces in the Revit model.
Revit LT can export a 3D DWG that Lumion can insert, but this is generated by mapping Revit categories and Revit sub-categories onto AutoCAD Layers. Hence, the nuance of painted surfaces is lost. We usually only model the brick and block layers in walls, then paint on the texture. That will all be lost. Imagine creating different walls for every painted surface! Sure, it is possible, but very time consuming.
Add-ons can be crucial to Revit users. Revit LT cannot run Add-ons, except for:
Trusses
Revit can model roof trusses. These are often needed in general architectural models.
Revit LT cannot model trusses, instead there is a lot of work that must be done to model individual beams in truss arrangements then then to group and array them.
Model In-place
In Revit you can easily model items in-place. It is a practice that most BIM managers discourage, preferring loadable families to be modelled instead, but sometimes it is convenient.
In Revit LT you can only model walls in place. Anything else must be modelled on in a family. You can work around the limitation of context by exporting the part of the model that serves as context as a 3D DWG after isolating it in a section box, and then import that temporarily into a family to serve as context.
Automation and Dynamo
Revit LT does not expose the Revit API. You cannot use a compiler to reference the Revit API and so any development you would like to leverage against Revit is not possible. Any macros that you may have that you need to run will not run either.
Dynamo is not installed with Revit LT. Dynamo player is not installed with Revit LT. That means that any Dynamo graphs that you may have liked to run against your models cannot be done. If you are running a mix of Revit and Revit LT, however, you can always open the Revit LT models in Revit and then run the Dynamo graphs.
AutoCAD LT Included
Revit LT comes bundled with AutoCAD LT and Revit has no AutoCAD bundled with it.
Conclusion
In conclusion, Revi LT is very limited on larger or complex projects or where rendering and automation are of concern. If you are trying to keep costs down in your office, running a mix of Revit and Revit LT may be the solution, but then you need to understand the limitations and scenarios where they are modest relevant, and you must buy the right proportion of Revit to Revit LT.
If you need help adopting the AEC Collection or the Autodesk Construction Cloud in your practice or if you are looking to invest in hardware, please contact Micrographics so that we may be of assistance.
Still looking for answers? Start a discussion with other professionals in your industry!
People, Systems and Businesses Perform better with Micrographics.
Our highly experienced Application Engineers can assist you with:
Autodesk Support, Implementation & Training | Consulting | Troubleshooting | Custom App Development For Revit, Inventor, Fusion & Vault
Check out our Micrographics Industry developed Tools: https://mgfx.co.za/software/tools-for-inventor/
For all queries info@mgfx.co.za.
