Does anyone know what’s going on here?
This is a sign of a DLL conflict, usually from Revit addins. Check your Revit journal for API_Error codes as they will likely give some clearer indication as to what is in conflict. If you can’t find the issue there, disable all Revit add-in and Dynamo customizations, restart your CPU and then launch Dynamo and see if that clears it up. Then start addin back Revit add-ins in small groups until you the issue comes back, knowing that the group you added caused the conflict to return and then narrow it down to the one which needs an update.
Hmm ok thanks i’ll check that out.
I do remember installing Bimorph package half an hour before this started…
If i figure out what’s caused this ill report back,
Thanks Jacob!
It stopped after uninstalling Bimorph
Edit, after Jacob’s response perhaps i was too quick to assume this was caused by Bimorph, as my log shows a ton of errors.
99% of the for that package I lean towards an add-in conflict as the author is quite skilled and the package is rather well built and maintained, but things happen.
Check to make sure there isn’t a Revit add-in in conflict before looking to BiMorph particularly (search your Revit journal for API_Error as a tip - DLL conflicts will show up here). After that make sure you have a compatible version of BiMorph for your Revit environment - you might need a newer or older verison of the package for your Revit release (i.e. the latest won’t work in Revit 2014). Finally reach out to the package author to report the issue.
Welp, i just checked the logs
I have a TON of errors heh…
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Revit.Config.Client assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.PnIDModeler.Client assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.API assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.CNC assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.CNCExport assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.Commands assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.Geometry assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.RevitGeometry assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.RevitUI assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.ShopDrawings assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.Slab assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Precast.Wall assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.ResultsBuilder.DBApplication.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.ResultsExplorer.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.StructuralRibbon.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.EnergyAnalysis.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.Practices.Prism assembly
' 0:< API_ERROR { : Assembly version conflict in some references in AIT.Common.API assembly
' 0:< API_ERROR { : Assembly version conflict in some references in AIT.ModelChecker.API assembly
' 0:< API_ERROR { : Assembly version conflict in some references in AIT.ModelChecker.Core assembly
' 0:< API_ERROR { : Assembly version conflict in some references in RD.Data.Common assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.ValidationTool.Client assembly
' 0:< API_ERROR { : Assembly version conflict in some references in AIT.COBie.App assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.AdvanceSteelLink.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.AdvanceSteelLink.Mapping assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.AdvanceSteelLink.Synchronization assembly
' 0:< API_ERROR { : Assembly version conflict in some references in DrxCommon.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in AreaCalculation.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.BatchPrint.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Bim360.Revit.Issues.Addin.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Bim360.DesktopConnector.Issues assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Bim360.SSONETUI.Adapters assembly
' 0:< API_ERROR { : Assembly version conflict in some references in BrxCommon.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in BuildingBook.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Collaborate.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in CollaborateBrowser.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in eTransmitForRevit.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.IWExportToRevit.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.LightingAnalysis.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in RevitDBLink.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.RobotStructuralAnalysysLink.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in RrxCommon.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in RoomBookInternational.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in RrxRoomQuantities assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.SolarAnalysis.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.WorksharingMonitor.Application.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.WorksharingMonitor.Utilities.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in BbRevitAddin2024.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Autodesk.Bim360.Revit.Publish.Nwc.Addin.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevitLoader.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevitRunner assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.WindowsAPICodePack assembly
' 0:< API_ERROR { : Assembly version conflict in some references in MadMilkman.Ini assembly
' 0:< API_ERROR { : Assembly version conflict in some references in System.Memory assembly
' 0:< API_ERROR { : Assembly version conflict in some references in System.Reflection.Metadata assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.CodeAnalysis assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.CodeAnalysis.CSharp assembly
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevitLabs.Common assembly
' 0:< API_ERROR { : Assembly version conflict in some references in Microsoft.CodeAnalysis.VisualBasic assembly
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevit_2024_dcaccc945b5d10a6_PyRevitLabs.PyRevit.Runtime.dll assembly
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevit_2024_aee515db5fce0b56_pyRevitBundlesCreatorExtension assembly
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevit_2024_2bb6f381f45cd585_pyRevitCore assembly
' 0:< API_ERROR { : Assembly version conflict in some references in pyRevit_2024_c631356fba98c5d2_pyRevitTools assembly
' 1:< API_ERROR { : Assembly version conflict in some references in Autodesk.C4R.Client assembly
' 1:< API_ERROR { : Assembly version conflict in some references in Autodesk.Http assembly
' 1:< API_ERROR { : Assembly version conflict in some references in Autodesk.JsonApi assembly
' 1:< API_ERROR { : Assembly version conflict in some references in System.Web.Http assembly
' 2:< API_ERROR { : Assembly version conflict in some references in Pubnub assembly
' 3:< API_ERROR { System.ArgumentNullException exception(Value cannot be null.
' 3:< API_ERROR { : Assembly version conflict in some references in Autodesk.ResultsManager.Application assembly
' 3:< API_ERROR { : Assembly version conflict in some references in Autodesk.LightingAnalysis.Utility assembly
' 3:< API_ERROR { : Assembly version conflict in some references in RevitRaaS assembly
' 3:< API_ERROR { : Assembly version conflict in some references in ClimateData assembly
' 3:< API_ERROR { : Assembly version conflict in some references in Bluebeam.Core.Client assembly
' 1:< API_ERROR { : Assembly version conflict in some references in Bluebeam.Plugin.Types.Core assembly
' 1:< API_ERROR { : Assembly version conflict in some references in Bluebeam.Core.BB3D assembly
' 2:< API_ERROR { Autodesk.Revit.Proxy.Exceptions.InvalidObjectExceptionProxy exception(The referenced object is not valid, possibly because it has been deleted from the database, or its creation was undone.) was thrown from a handler of Autodesk.Revit.Proxy.UI.Events.ViewActivatedEventArgsProxy event. The API event handler was registered by application Revit 2024 BIM 360 Issues Addin (bea1df91-34ec-4296-af6d-81d1d7a9d606). Changes made by this handler are going to be discarded. }
' 1:< API_ERROR { Autodesk.Revit.Proxy.Exceptions.InvalidObjectExceptionProxy exception(The referenced object is not valid, possibly because it has been deleted from the database, or its creation was undone.) was thrown from a handler of Autodesk.Revit.Proxy.UI.Events.ViewActivatingEventArgsProxy event. The API event handler was registered by application Revit 2024 BIM 360 Issues Addin (bea1df91-34ec-4296-af6d-81d1d7a9d606). Changes made by this handler are going to be discarded. }
' 2:< API_ERROR { Autodesk.Revit.Proxy.Exceptions.InvalidObjectExceptionProxy exception(The referenced object is not valid, possibly because it has been deleted from the database, or its creation was undone.) was thrown from a handler of Autodesk.Revit.Proxy.UI.Events.ViewActivatedEventArgsProxy event. The API event handler was registered by application Revit 2024 BIM 360 Issues Addin (bea1df91-34ec-4296-af6d-81d1d7a9d606). Changes made by this handler are going to be discarded. }
' 1:< API_ERROR { Autodesk.Revit.Proxy.Exceptions.InvalidObjectExceptionProxy exception(The referenced object is not valid, possibly because it has been deleted from the database, or its creation was undone.) was thrown from a handler of Autodesk.Revit.Proxy.UI.Events.ViewActivatingEventArgsProxy event. The API event handler was registered by application Revit 2024 BIM 360 Issues Addin (bea1df91-34ec-4296-af6d-81d1d7a9d606). Changes made by this handler are going to be discarded. }
Multiple tools in there which have had to issue updates to resolve conflicts in the past, so safe bet that missing one (or many) of those updates are at fault here.
Disable them all, and enable via a binary search until you narrow in on the issue. This will confirm which is playing poorly with Dynamo/bimorph.
An example of applied binary search
Binary search above means to always test half the total remaining set. An example which assumes only one add-in is in conflict.
Say you have 128 add-ins.
First test 1-64. If the issue occurs you know one of those is dirty, so 65-128 are ‘clean’.
Now test 1-32. If the issue reoccurs your know that 33-64 are clean.
Now test 1-16. If the issue reoccurs you know 17-32 is clean.
Now test 1-8. If it reoccurs 9-16 are clean.
Now 1-4. If it reoccurs 5-8 are clean.
Now 1-2. If it reoccurs 3-4 are clean.
Now 1. If it reoccurs 2 is clean and 1 is in need of an update.
Now enable 2-128 and repeat the halving process until no issues are found.
And since it is a true false test, with only 7 tests you can find the one failure point by testing the first half of the previously untested set.