I’m having an issue with Import Geometry / file upload inputs in ShapeDiver and I’m trying to understand if this is a bug, a limitation, or a configuration problem.
We have two very similar configurators:
Configurator A (previous version) → works fine
Configurator B (latest version) → it still runs, but it does not work correctly due to an issue with Import Geometry inputs.
The Grasshopper definition is almost identical in both cases. The only relevant change in the latest version is that we added one new Import Geometry input.
After uploading this updated definition, ShapeDiver no longer shows/recognizes some of the Import Geometry inputs in the parameters list (not hidden — they simply don’t appear). In addition, not only the new Import input is affected, but also some existing Import inputs that were working before.
We already tried:
Clear cache
Reload default parameters
Re-uploading the model
But the missing Import inputs still don’t appear in ShapeDiver.
Has anyone experienced something similar?
Is there any known limit on the number of Import Geometry components / file upload inputs, or something that would cause ShapeDiver to ignore them? Any debugging tips would be greatly appreciated.
Quick update with more findings — we managed to reproduce the issue and we found a temporary workaround, but it’s not ideal.
What we found
In ShapeDiver, some Import Geometry inputs sometimes don’t show up in the parameter list (they are not hidden — they simply don’t appear).
We tried reproducing this in a very minimal Grasshopper file (only an Import Geometry component + a simple setup), and the problem still happens.
Strangely, an older Grasshopper file from last week works fine, even though it is more complex.
Temporary workaround
We noticed that the Import Geometry input only appears in ShapeDiver if we connect a Data primitive / “Data” parameter into the setup (basically forcing the component / data flow to be evaluated).
However:
This Data component must remain enabled; if we disable it, the Import Geometry stops working / disappears again.
Also, the workaround is problematic because it makes the imported data/geometry visible in the scene, which we don’t want.
It is correct that, if your Import Geometry component is not connected to any dependency in your definition, it will be ignored as it does not influence the outputs. This is a standard behaviour in ShapeDiver, in order to avoid unnecessary computations.
Could you explain further why you would need to import geometry in your Apps while doing nothing further with the imported geometry?
If the “Import Geometry” has an influence on this “2nd layer detailed geometry”, it should be displayed in the App. Are you sure that it is correctly connected to all the pdf outputs in your App? If so, could you provide a minimal example that can help me reproduce the issue?
I cannot reproduce this issue at the moment. Could you try again and let me know if it happens again? If so, could you let me know which steps you are taking after the model is uploaded and before you click on “Save”? Maybe a specific setting you are updating is causing the issue.
