After the recent update ‘pipe’ component, there’s a problem with the geometry display. It’s not visible
test oczka.gh (9.8 KB)
at all.
The Service Release 25 seems to introduce a backwards compatibility issue. The problem will be fixed once we update the servers to SR25 (currently, they are on SR23). This will happen next week.
@Dave18 We have now updated the Rhino 8 servers to SR25 and this issue seems to be resolved.
It works now, but it seems like I have to re-upload all the models. Will this happen every time?
You should not have to re-upload models, but you need to clear the cache of your previous models, because they were cached with the previous version.
I am not sure what you mean by this. You will not have to reupload (or clear the cache) every time we deploy a new service release. Most of them will not affect your models. However, once in a while, McNeel introduces breaking changes between releases, in which case you might need to wait until we deploy the service release you are using locally also to our servers.
Ok, I clear the cache but nothing changes.
In that case, the component was modified with new inputs, so it might be needed to reupload your models.
I understand, so it works like this: if a components iis new and the server hasn’t bedd updated yet, the definition loads without that component, not the older version?\
Als, please explain how materials work, in the definition I uploaded here, the rounded objects have a mettalic factor set to 1, yet the displayed object is matte.
It depends on which changes were done to the component. But as a general rule, older versions of definitions will work in newer service releases. The opposite is not necessarily true (definitions created in newer service releases might break on older ones). Again, this type of breaking changes does not happen frequently.
The roughness factor of your material is set to 1, which results in a matte object. You need to both adapt metalness and roughness to achieve the desired outcome.