When uploading some scripts, the errors from shapediver are not specific, and we would like more transparency into exactly what the issue is in the script or which line in the script has that issue. e.g of a current issue - unsupported plugin. we would like to immediately know which plugin is in the script that is not supported by shapediver. I know the documentation gives a list of plugins that shapediver does and does not support but there is no time to go over all of them and decide on the script. We are prototyping with generating grasshopper scripts using an AI model. We have trained it with a number of valid shapediver compatible scripts but the model is outputting scripts that shapediver rejects but grasshopper accepts.
So, programmatically - what do we need to do inorder to get more transparency on the errors that show up only on shapediver but not on grasshopper. Let me know if there might be a resource or an api we can use to further develop inorder to enable this transparency.
Could you copy here the error you are getting regarding the unsupported plugin? The error should show you precisely which plugin you are using that is not supported, including (if relevant) the versions of the plugin we support.
Besides this specific error, please let me know if you are getting any other non-specific errors that you would like to see improved.
Edit: I misread your message and realize you want insights about supported plugins (and potentially other compatibility issues) directly in Grasshopper. This is something we will improve in the future, as part of making it possible to upload and profile definitions directly from Grasshopper. I will let you know when we make progress about this topic.
Thanks for the suggestion, we were training for grasshopper compatibility only - not shapediver but we should since we want to share these script outputs online
yes, that file is from an AI model. All of our AI generated files are not working with shapediver yet, but a few have started to work in grasshopper. By work, I mean just seeing the components and their wires connected after script loads - some wires needs to be manually connected to the nodes.
Thanks for checking in. So, there is a small struggle with ai-generated scripts that can open on grasshopper… they are not editable.I haven’t been able to try your suggestion yet because there there save option is deactivate. I am still investigating what is missing with these ai generated outcomes. See an example of 1 script:
Ok I see. If you can’t save the model using Grasshopper, that means that there is obviously something wrong with the xml schema of these AI-generated models. You will have to make sure to stick to the precise XML schema used by Grasshopper (which won’t work well).
