I saved out a portion of my SketchUp file as a component so I can focus on that one area in a large file. When I opened that SKP file, all of the Cosmos proxies seemed to have lost their properties and are now just geometry of the blobs. If I open the original file, they render as expected.
Hello @Matthew_Valero ,
Thank you for your report. Could you please describe your workflow of saving the component? Also, which is the SketchUp and V-Ray versions you exported your component with?
I am not able to reproduce the issue so far. My workflow is I create a geometry, add some Cosmos Assets (merge some of them to test the behavior with merged Cosmos Assets), select all and make a component from them. Then I save by right click on the component > Save Out > To Device and choose a file path. When I open or import the .skp the Cosmos Assets are preserved.
Kind regards,
Iva
I looked a little deeper into this issue this morning. The file is just a grouping of Cosmos assets that were turned into a SketchUp component and then saved out for working on outside the main file. This seems to be affecting several Cosmos assets. These models were placed in this file was rendering fine back in June of this year. It looks like some of the assets that are not rendering have a different naming convention that in Cosmos currently, so I don’t know if that might be the issue. Here is a file
Hello @Matthew_Valero ,
Thank you for sending the file!
I looked into it and the naming of the Assets in the .skp file corresponds to how duplicated Cosmos Assets are named (when an instance of a Cosmos has been made unique). This doesn’t seem to cause issues with new files, after saving out components with duplicated Cosmos Assets there is no data loss.
The wiping of V-Ray data happens when you save out a V-Ray object — for example a Cosmos Asset’s own component definition. When you then open the saved-out .skp and open the Asset Editor, a warning appears saying the serialized V-Ray data will be removed from the model if you proceed. This is expected behavior.
Since the original file still renders correctly, could you please repeat the save-out from it now, using the same steps as before, and let me know whether the newly saved .skp has the same problem when you open it?
Kind regards,
Iva
When I open my original file and start V-Ray I get a dialog saying that some V-Ray components need to be updated. I choose OK, test render works fine even with the Entity Info window showing the name with a hashtag in the name. If I copy and paste into a new file, some Cosmos components work as expected and some do not. I have also tried grabbing a grouping of Cosmos assets, making them a component and saving that out as a new file and rendering that file, but the same thing happens with some of these components. Here is a screen capture Recording #31
Would it be possible to send us the original file? I did more tests and I am still not able to reproduce the issue.
Thank you in advance!
I cannot. This project has a strict NDA