We have been using LumenRT for a while now, but with Revit 2019 now being used more widely, when can we expect the plugin to be updated/released?
It's in LumenRT Update 12 - out later this month
LumenRT Update 12 at C:\Program Files\Bentley\Bentley LumenRT CONNECT Edition - Update 12\LumenRT\Export\Revit doesnt have any dll file for Revit 2019.
I get this at launch of Revit 2019.2 once the missing rv_LumenRT2019.dll is place it the location of
C:\Program Files\Bentley\Bentley LumenRT CONNECT Edition - Update 12\LumenRT\Export\Revit\
Just for giggles I did try coping the 2018 dll and renamed it to 2019. It does load the plugin but lauching LumentRT from within Revit fails Miserably. But as least I do not get errors every time I open Revit. the Plugin loads but does not function
are you using 2019.2 version of Revit?
Yes using 2019.2 ver of Revit.
I'm using the same version and it works fine on the Autodesk Test Architectural file. Can you try it on this file and see if it works. Maybe it's something with the file
Sorry I have downloaded you zip file. extracted it and placed it in the correct fold. And get the External Tool Failure dialog. Also looking int registering the DLL file in windows. Some just coping a DLL does not work with windows. It must be put in place by the installer. hopefully Update 13 will have all the files and install them correctly.
You may be right about this. I think with an installer, the issue goes away.
Here is the production version of LumenRT Update 13. Can you try installing this and see if the Revit export works:
Any new developments on this. Tevit 2019 was loaded first and the I have loaded OpenBuildings w/ LumenRT v12 and the Connection Client has run the most recent update to LumentRT v13 and The add in still doen't show in Revit 2019. Thoughts?
rv_LumenRT2019.dll can be found in the following folder:
C:\Program Files\Bentley\Bentley LumenRT CONNECT Edition - Update 13\LumenRT\Export\Revit
However, I don't believe the DLL will not be loaded into Revit without a .addin file to act as a manifest file. The .addin file is written in XML and looks something like:
<?xml version="1.0" encoding="utf-8"?><RevitAddIns> <AddIn Type="Application"> <Name>Model Review</Name> <Assembly>C:\Program Files\Autodesk\Revit Model Review 2019\ModelReview.dll</Assembly> <AddInId>8e406bfc-b416-4ecb-b639-c290ca3181f2</AddInId> <FullClassName>BIMStandardsManager.ExternalApp</FullClassName> <VendorId>ADSK</VendorId> <VendorDescription>Autodesk, subscription.autodesk.com</VendorDescription> </AddIn></RevitAddIns>
OK, with a bit of reverse engineering, generating a GUID, and guess work on the namespaces in the rv_LumenRT2019.dll using Visual Studio to sleuth them.., my son and I created a working manifest file. the following text can be added/pasted into a .addin file to create a working manifest:
<?xml version="1.0" encoding="utf-8"?><RevitAddIns> <AddIn Type="Application"> <Name>Model Review</Name> <Assembly>C:\Program Files\Bentley\Bentley LumenRT CONNECT Edition - Update 13\LumenRT\Export\Revit\rv_LumenRT2019.dll</Assembly> <AddInId>d452173f-aad5-4062-8823-318474266d45</AddInId> <FullClassName>LumenRT.LumenRTApp</FullClassName> <VendorId>BSI</VendorId> <VendorDescription>Bentley Systems, Incorporated</VendorDescription> </AddIn></RevitAddIns>
I named my file LumenRTExport.addin and placed it in the following folder:
I should add one more thing...
The AddInId (GUID) is specific to the DLL. It is used to register each unique DLL in the Windows Registry. So if someone wanted to install the plugin for multiple version (years) of Revit, then each Bentley DLL for each Revit version would require a unique AddInId (GUID). To generate a unique GUID is quite easy using Windows PowerShell. The syntax is as follows: