Wince Friday EOD all our models stopped working properly.
All the volumes/textures are not visible anymore. Basically all elements that are dynamically generated based on the parameters are broken.
Only some static element are rendered.
Cached versions of the rendering were working fine and the issue was faced every time I parameter was changed. By removing the cache data of one of the model we confirmed that everything was broken now which means that the issue is caused by a fresh new render done by the servers.
But we have the same on all models which means that something has changed on the ShapeDiver side that is causing this issue.
I know that a server patch has been deployed last week because of some issues we had with rendering textures. After the patch our models were working fine but maybe there was another patch right after ?
It’s pretty urgent for us to fix that as our app is totally broken right now.
Is your model using JSwan? We deployed a new version of the plugin (1.2.1 instead of 1.2.0) and it seems that there are some backwards incompatibility issues we have not caught when we tested. We will try to revert to the previous version of JSwan, but in the meantime you could try to upgrade the plugin locally to the latest version and see if your models are broken locally. Another user reported issues with the Deserialize component.
yes we are using JSwan to read the JSON parameters.
We’re going to try locally to upgrade to the last version of the plugin in order to confirm the issue.
Please let me know about your findings. Note that if we confirm backwards compatibility issues, we will have to revert to the previous version of JSwan, so it might be safer to keep the versions you built using 1.2.0 separate from the potential changes you will make using the new version.
We have rolled back the version of JSwan on the servers to the previous 1.2.0. You models should be working as expected again, although the cache might need to be emptied for failed computations that happened when the newer version was installed.
All good now after clearing our models cache.
Thanks for the quick action on this. Appreciated.
How do you guys want to tackle this plugin update in the future ?
Are we going to need to update something on our models ?
Keep us updated when you have more news on that.
On our side, we are working on handling better this type of issues, and display the model anyway without the texture, instead of throwing a 500 error. In the meanwhile, you should be able to solve the issue by making sure the texture URLs you are using are accessible.
At the moment, we will not update JSwan again. We will investigate further where the issue comes from and hopefully it will be solved in a later version. For the time being, the safest solution is to stay with version 1.2.0.
You’re right for the url, sorry for that. I was able to display it because I was logged in to our backoffice but your server couldn’t load it anymore.
Thanks for pointing that out.
Regarding JSwan we’ll stay with the current version yes.
Is there a way to be notified in advance about your next releases ?
I haven’t found any details regarding this on your website.
We are working on a way to notify users about new releases through the platform notification system. At the moment, you can refer to the release notes of the platform, plugin and viewer here: ShapeDiver Help Center
We will add a new section for updates related to 3rd-party plugins.
