Did you remove the SML component from v3.2.0 to v3.3.0?
Now I can’t push anything to Speckle anymore.
@Nikos, nope. It is not there. And now I downgraded to v3.2.0 and the component is not there. This is weird!
can you check please what Rhino version you have? They are bundle together, when you install Rhino you install also Grasshopper.
Something is weird in my system. I will try to restart and reinstall the v3.3.0.
I have Rhino 7, Rhino 8 and RhinoInside installed.
When I upgraded to v3.3.0 on Tuesday, the component was missing but I thought you deprecated it. Now I see It should be there.
I will suggest to turn of all Rhino instances and do a clean install again. Check from the task manager to make sure that no rhino is running.
I will also first uninstall speckle from the settings>installed apps
then install fresh the latest version.
Note: If there is any component that fails to load there should be a notification/error when you start Grasshopper.
I did all you mentioned and I found the errors when starting grasshopper. See image below. Do you think this is a conflict with other apps or plugins?
This happened only when installing v3.3.0 because with v3.2.0 all was okay.
I removed the other components that I know were giving errors and leave only speckle. This is the error text:
Object: SpeckleSelectModelComponent (level 1)
{
Exception has been thrown by the target of an invocation.
TargetInvocationException
}
Object: SpeckleSelectModelComponent (level 2)
{
Account 0CD23FA429CC8470B9F5E227B1F86C0C not found
SpeckleAccountManagerException
}
@Nikos, Is there a way to bypass that component as it was before?
We recently changed company name and now I have 2 different accounts in the speckle manager. As it says Account not found, it may be pointing to our old server (we were RHDHV and now we are Haskoning)
Ah do you need Speckle Manager for any legacy connectors? If not, I’d recommend uninstalling, and making sure that only our Desktop Services is running for account management
In any case, the component shouldn’t fail to load even when accounts are not found - I’ll file this as a bug to investigate
Okay released a hotfix 3.3.3 that should resolve the missing node: this was happening in saved scripts where the url node had an account stored that was either deleted or migrated to a different server address.
With 3.3.3, you should get an error on the node instead, and can resolve this by re-adding the URL node to reset the stored account.
1 Like
Thank you @clrkng!
1 Like