There is a bug during import viewer settings on the Shapediver platform.
If you import some settings, then delete a light, then import the settings again, the light does not re-appear, meaning your only option is to Cancel and upload it again.
I also noticed that the setting for Groundplane Shadow is always off when I import viewer settings, even though it is always on in the models I import from.
Thanks for checking and fixing!
While you are in the viewer settings, I see you added a few options like environment rotation. What I noticed is that there should be a way to increase either the environment intensity and/or Tone Mapping Exposure to above 1 (say up to 2). Otherwise there is really no way I can see to increase the exposure or brightness of the scene without adding any lights.
Thanks for considering!
Last thing related to this I just found out. If you have a file upload parameter and have set a new file in one model and you then copy the parameter settings from that model to another, then the file upload parameter is not set at all. That means it does not take the fallback from the Grasshopper file and neither does it take the uploaded file from the model I am copying the settings from.
It would be nice if it would do either of those things. From a UX point I would say it should then simply use the fallback, because no filename is shown in the file upload parameter and it would be weird to set something there that is not visible.
That said and I think you agreed on that yourself, the state of the file upload parameter needs to be more clear, so we can tell if a file is actually set or not.
Thanks!
If you import some settings, then delete a light, then import the settings again, the light does not re-appear, meaning your only option is to Cancel and upload it again.
I also noticed that the setting for Groundplane Shadow is always off when I import viewer settings, even though it is always on in the models I import from.
Thank you for reporting these. I could reproduce them and filed bugs for our team. I will let you know when a fix is released.
What I noticed is that there should be a way to increase either the environment intensity and/or Tone Mapping Exposure to above 1 (say up to 2).
Thank you for the suggestion. We will review this and if it makes sense also release an update (likely at the same time as the bug fixes).
If you have a file upload parameter and have set a new file in one model and you then copy the parameter settings from that model to another, then the file upload parameter is not set at all.
It is not possible to copy a file input parameter from one model to the other, because uploaded inputs files become assets associated with a specific model. Here we need to improve the feedback, which we are aware of. What do you call exactly the fallback from the Grasshopper file? Internalized geometry that you use in case no file is sent? Or the files downloaded from an input URL?
Maybe fallback is the wrong word. It’s more the default that get’s used unless I upload something. It’s the input to the file upload field:
From what I can tell it works like this:
I would say that the file upload field in the backend needs some way to display an effective link that is being used, so that I can tell if it is using what I specify in GH, something I uploaded or no file is set at all. If I delete the file I uploaded in the Shapediver Backend, it should fall back to the file I specify in GH. At no point should it be possible to have NO file in the component (unless I did not specify anything in GH).
Lastly I think it should be possible to import the parameter settings of one model to another and if a file is specified there, that link should get copied over. Otherwise there should be some warning that it did not do that.
Thanks for considering the other improvements as well.
We could reproduce an issue when loading parameters from a model to another. The issue is that the platform then tries to reference the id of the imported file but cannot access it as it is linked to another model. We will in general improve the file import component and the feedback it gives in the near future.
For the rest, please have a look at this page which should give you a good overview about the way the file import functionality works: File parameters (inputs)
