Announcement

Collapse
No announcement yet.

Relinking Cosmos Assets

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Relinking Cosmos Assets

    I have been working back and forth between my office workstation and my home workstation. Somewhere in the switching between the two, I am not able to render some of the Cosmos assets, especially one that was merged. Where are the Cosmos files saved, so that I can remap them?
    Matthew Valero, ASAI

  • #2
    Answered my own question, but just in case someone else needs this info - they are saved in C:\Users\[User]\Documents\Chaos Cosmos\Package
    Matthew Valero, ASAI

    Comment


    • #3
      So I relinked the files that were missing the File Path Editor but I still have 2 Cosmos assets that are not rendering even though when I check them out in the VRay Asset Editor, it is not showing the Cosmos asset as missing.
      Click image for larger version

Name:	Missing.JPG
Views:	399
Size:	229.4 KB
ID:	1135532
      Matthew Valero, ASAI

      Comment


      • #4
        Just to further update, I had to delete the SketchUp component, purge my file, then re-insert and it seemed to work then. I wonder if it was referencing the location on my other computer. There doesn't seem to be a way to update the path for Cosmos assets in the Asset Editor or the File Path editor. This could cause problems for those, like myself, that are working in multiple locations these days.
        Matthew Valero, ASAI

        Comment


        • #5
          Hi ValeroStudio,

          What you've described should not be happening.
          The 'blackbox' Cosmos assets are handled by V-Ray 100% and when they appear resolved (with a blue checkbox) in the asset editor they should just work.
          Can you please share the file from the screenshot so that I can take a look.
          Maybe we've missed something.

          Regards,
          Konstantin

          Comment


          • #6
            Hi ValeroStudio,

            Excuse me for the delayed response.

            We have been testing your scene quite a bit here in the office and we identified a couple of issues on our side.
            The first one is that there is an error popping up when a missing Cosmos asset is selected. It has been fixed already and will make it in the next update.
            There was yet another issue with the names of specific Cosmos assets you had in the model. The Cosmos team will soon fix this.

            On the other hand I was not able to reproduce the issue you described.
            Are you still able to reproduce it?
            If so, can you try to list the exacts steps you take to get there?

            There doesn't seem to be a way to update the path for Cosmos assets in the Asset Editor or the File Path editor.
            This should not be a problem.
            If the Cosmos asset is missing on the second computer you should be able to download it (a button is supposed to appear next to the asset in the Outliner).
            If the Cosmos asset has been downloaded (in the Cosmos database) on the second computer it'll just work.
            If you pack the project with the Cosmos assets included, then it doesn't matter if you have the same items downloaded on the second system. The asset will work as expected with the only difference that the file references it uses will point to the unpacked scene folder and not the Cosmos repository. The checkbox in the asset editor should be orange in this case.

            Regards,
            Konstantin

            Comment


            • #7
              I just quickly created a test file at the office using Cosmos assets and then saved the file and opened it on a remote workstation. The missing assets showed the download arrow, I clicked that and they loaded properly and rendered, so that worked well. I still am left wondering about HDRIs from Cosmos. There has got to be a better way to manage them, no? Are we just supposed to redownload and remap them? What is the workflow for loading a missing HDRI?

              This is an example of what I need to do in this scenario - redownload and then make a duplicate. It gets messy when you have multiple HDRIs and are working back and forth between machines many times.

              Click image for larger version

Name:	Capture.JPG
Views:	371
Size:	24.5 KB
ID:	1136357
              Last edited by ValeroStudio; 11-01-2022, 10:15 AM.
              Matthew Valero, ASAI

              Comment


              • #8
                Is it possible to VRay to just look inside of whatever folder that machine is set up to download Cosmos assets into and find the HDRI textures automatically? For example, when I open a file on my home machine, that I have been working at work, VRay will looking in the folder that Cosmos saves into and try to find any missing assets, including HDRIs. If the HDRI is missing, maybe we either get a message to download the missing HDRIs from Cosmos or we get a download icon similar to the models.

                This probably doesn't come up much because I bet very few people are working back and forth, but these days with remote working, it is more and more common for me.

                I guess it would just be nice is VRay did all of the relinking for me when I open a file on another machine.
                Matthew Valero, ASAI

                Comment


                • #9
                  Hi,

                  There has got to be a better way to manage them, no? Are we just supposed to redownload and remap them? What is the workflow for loading a missing HDRI?
                  For now Cosmos HDRIs are handled like regular textures.
                  There is no additional logic handling them.
                  We can't even identify them being Cosmos textures after import.

                  For example, when I open a file on my home machine, that I have been working at work, VRay will looking in the folder that Cosmos saves into and try to find any missing assets
                  This is actually what we do with the material library folder.
                  Missing textures are auto-resolvet to it, if their global path is not valid.
                  I guess we can use a similar logic and search in the Cosmos repository but I have to make sure this will not cause any issues.
                  I'll also look into alternative solutions to the described inconvenience.

                  Konstantin

                  Comment


                  • #10
                    Thank you Konstantin, this is great information.
                    Matthew Valero, ASAI

                    Comment

                    Working...
                    X