Hello,
I found a new bug relating to User Objects built with the new Script Editor component.
-Create a User Object from an older WIP build pre-Beta
-Save it as a User Object
-Drag said User Object onto the canvas of a current WIP build post-Beta
-It fails to load and gives the following error dialogue:
If the user object was already added to a document it opens and runs just fine.
I just can’t instantiate a new instance of it anymore.
Thank you!
Seems like something changed between WIP and Beta that broke this. It doesn’t happen between beta versions does it?
Hi @eirannejad , thanks for checking in on this!
I don’t believe it still occurs and as a result probably isn’t even something that is currently fixable traceable.
As you pointed out it was likely something between versions.
I’ll open old scripts that had the user objects populated, replace my User Objects with those and confirm that it works now.
I’ll report back if it doesn’t for some reason.
Thanks!
Thanks a lot Michael. Let me know if you still see errors in that. We also fixed the icon quality and size on the User Objects to they should behave themselves now 
Thank you, I saw those changes in a recent build! Do you anticipate support for custom icons for user objects coming again soon?
It should be already there. You can pick an icon when creating the user object and it would retain the icon
Oh excellent! This isn’t the case currently (on my end) but I’ll check today’s build for this feature! Thank you!
Hi Ehsan, just tested and I can confirm that User Object custom icons are in fact showing again.
Thank you very much!
Thanks so much for testing this
Thank you!
Hi @michaelvollrath and @eirannejad. I found this Forum thread after installing the Euglena Plug-in where I ran into the same “User Object Failed to Deserialize” issue. I’m on Rhino 8 SR2 and as far as I understood the issue happens because the User object was created in Rhino 8 WIP. Is the only way to make this work to install the old WIP version as I do not have an older script to open to replace the new User Objects? Thanks for your help 
I don’t know the answer to this one but I’m curious as well. Thankfully I have older grasshopper files that have the user objects on the canvas and I was able to rip the code out of those and paste into the latest builds versions of the scripting components, then resave to user objects but in the event that you don’t have that opportunity I don’t know what the work around is outside of what you mentioned, installing that WIP version, putting all the userobjects you want to “convert” onto the canvas, saving the .gh file then reinstalling a newer R8 version and creating the new user objects from the older versions code.
@eirannejad do you have any magic solutions?
@Michael_Wieser Things changed quite a bit in the last few months. DM me your old Rhino WIP user objects and I can update them to the new and see where the bug is so this is fixed in 8.3
Thanks for your response @michaelvollrath
Hi @eirannejad thanks for your response. Unfortunately, I don’t have Rhino WIP user objects as I just recently started to use Rhino after a few years of not owning a license. So I purchased Rhino 8. I was informed by the developer of the Plug-In that the issue is caused because of differences between versions as you also mentioned and that they will update the Plug-In. Will wait for that. But thanks for your help and your quick response! Much appreciated
