There are some frequent notifications which I am getting after installing some custom node packages - BIMMorph or SynthesizeToolkit and some IO errors. How do i handle these ? Are they critical or can be ignored ?
Looks like either the Bluebeam addin or Bimorph are targetting different builds of the autodesk.extensions library.
Know how hard the Bimorph author works, I suspect it’s like coming from the bluebeam addin. The two routes to fix this are ensure both addins/packages are latest and beyond that let them know they may be out of date with their references if they are and the error persists.
Will try that. Let’s see.
So, I have removed BImMorph and Synthezise Toolkit and others like Iron Python 3.0 which was giving conflict. Also some more plugins. Also dropped a ticket to Bluebeam.
Some remaining errors:
The question is do these errors create any significant functional issues or could they be ignored. Since if the node package is required but doesn’t have a compatible version, what’s the solution ?
Also, is there a way to know whether a package is compatible before hand ? Uninstalling them later is a pain since Revit needs to be restarted for every step.
Sometimes they can be ignored, but generally this is why packages need to be tested before depending on them at company level in my experience. This will typically happen for zero touch based packages given they need to be built against specific package versions.
Archilab is typically maintained but i dont think the grimshaw one is as Konrad moved on from there a while ago I believe. Not sure if archilab net is the same as archilab grimshaw.
2 Likes
Archi-Lab shouldn’t be an issue if the latest version is installed for the particular Revit release. The link should clarify.
1 Like
Generally speaking these can be ignored until you have something break - could be a week, could be a month, could be a decade.
Get the right Archi-Lab version and that should go away.
Bigger issue will be the bluebeam conflict. That is more likely to cause breaking issues which cause inspected behavior when it does cause a problem. The fix is to first make sure you are on the latest version of the add-in, and then remove it if the latest version is still in conflict.
1 Like
Yes, thanks for the Archi-Lab link there. Got it ! Bluebeam issue still waiting on that team to resolve.
1 Like