Download Export fail Rhino 8 and on ShapeDiver (if > 1 sublayer level)

I have an issue with the Download Export feature for my model both in Shapediver and Rhino+GH.

I have 5 different download buttons with different settings.
When first loading the model, I can click through all 5 and I get the 5 files as requested.
Once I modify some parameters, some or all of the download options stop working and when pressed sort of freeze and nothing happens, with no error message appearing.

Additionally, the bug appears also in Rhino+GH. When first calculating the GH script, I can do local export for all 5. Once I modify parameters, I try export local again. It opens to let me chose save location. I click ok, but the file is not saved. However, if I do it again, then it will save the file correctly.

The disadvantage on Shapediver is that I can not immediately click download again as it is blocked in the loop. It appears to take 5minutes for the spinning circle to stop spinning before I can click again. However it does not work again after the 5min have elapsed.

Correction: After 5 minutes I get this pop-up:

Using the following:
Windows 11
Rhino Version 8 SR14
(8.14.24345.15001, 2024-12-10)
Shapediver v1.22.0
Using rhino 8 backend on the platform: sdr8euc1 (Rhino 8, shared Geometry Backend)

What’s interesting is the fact that the export fails in Rhino without anything happening. But then works again. I wonder if there is something specifically buggy in the “Download Export” component. I am feeding in data trees with controlled numbering, but since it works on the first attempt, I guess data trees are ok?

Thanks for your help!
Shapdiver user: dragos@mule.studio

I could replicate an issue with your model. Our team is investigating it, but since it is a very large model it will take a while. If you manage to replicate the issue on a minimal example, it would help us look for a solution. Otherwise, I will let you know once we identify and solve the issue.

1 Like

Hi @mathieu1

Thanks for the input. I have managed to narrow it down a little bit. It appears that when I use the “nestedlayer” attribute it seems to fail in Rhino as described. If I only use “name” and “material” it would download at every click.

However I have not yet replicated it in a smaller script. Will update when I know more.

A further update @mathieu1

When 1 sub-layer level is given (“Layer::SubLayer01”) as an attribute it works as expected.
When multiple sub-layer levels are given (“Layer::SubLayer01”::“SubLayer02”) it replicates the behaviour in my model. I did not test with more than 2 sub-layers.

See model exportTest on the platform.

PS The behaviour was the same in Rhino as well as on Shapediver.

For now, I am able to stick to Layer + 1 Sublayer to avoid the issue and the behaviour is correct in Rhino and Shapediver, for my larger models.

I guess this points to the Download Export component having an issue when multiple nested layers are injected into an object.

Thank you for taking the time to isolate the issue. I can confirm that exporting fails if more than one level of sublayers is specified as an attribute. I will let you know once we deploy a fix.

1 Like

Thanks @mathieu1 !

Best,
Dragos