Could you explain how your application is implemented? Are you using the viewer API to export an image from model A and then using this URL as an input for model B using the API again?
In any case, the URL created by model A is a temporary one. If model A is not recomputed, after a while model B will stop showing it because the temporary URL will stop to function.
If you want to implement such a workflow, you will need to fetch the texture image from model A and store it somewhere, then use the URL of this location to input it in model B.
There might be a simpler way to structure your application, I can maybe suggest something if you give me some details about your setup.
Our workflow works since few years in production
Yes, we use the viewer API to export an image from model A and then using this URL as an input for model B using the API again
We know this url is temporary but that’s enough in our case.
This was working until few weeks.
We really need to find a solution, as this bug is in production and break all our shop process.
We would need access to the app to be able to reproduce and investigate the problem. Is it possible to get a link and a list of steps to reproduce?
Something that could help is to look at the “Network” tab of the console and get the exact error thrown by the API when trying to fetch the image (the console log is not specific). If you cannot give me a working link, this could already provide some helpful information.
Please go to Configurateur Garde-corps - Primo Gardex
Step 2, clic on “Changer de motif” and choose a pattern
In the console you’ll see : Error: Could not fetch image from…
Just a few more details: could you describe what the workflow is when choosing a new pattern?
At first, one sees a 3d model in the viewer. Do I understand correctly that, when clicking on the “Changer de motif” button, the following steps happen:
An export is triggered from the model and the temporary url is retrieved in the application.
The session to the first model is closed
A session to the second model is opened and a text input of the second model is filled with the temporary url. The second model should then be displayed in the App instead of the first one.
Maybe I am misunderstanding the issue, but without understanding exactly what your application is doing it is difficult for me to reproduce or understand the cause of the error. Would it be possible for you to include a minimal piece of code of what your application is doing when importing this last image into the application?
As a side note, I noticed the application is using a very old version of the viewer 3 (2.2.2). I would recommend upgrading the application to the latest version (3.15.12).
I tested with this version in Rhino 7 and it also works as expected for me. Could you please share a screenshot of the error you see? Which component throws an error, the material component or the display component?
We are almost there, if you could give me the link to this model, our team would be able to start investigating. If possible in a very minimal version only using the url, and the material and display components.
)
