Announcement

Collapse
No announcement yet.

Chaos Cloud preview error

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

  • Chaos Cloud preview error

    Hope someone can help here. I'm trying to preview my scene prior to submitting to Chaos Cloud. I get the attached error message but when I ignore it and submit to the cloud the render fails.
    Does anyone know what a vector definition is and why there is an error? I have multiple warnings regarding bitmap blur values....could this be it?
    is it Penry the mild manored janitor?

  • #2
    I have managed to copy the error from Chaos cloud which looks like the attached. Apparently it's a parsing vrscene issue.......I don't know what that means. I'm not new to Vray but I am new to the whole cloud rendering thing.
    is it Penry the mild manored janitor?

    Comment


    • #3
      For anyone interested it was some dodgy poly model I had downloaded off the internet. All working fine now. I must remember to check everything I download before importing into a scene!!!!!!!!
      is it Penry the mild manored janitor?

      Comment


      • #4
        Hey Marc! Happy you found it yourself. But dodgy model or not, this problem shouldn't happen and I want to get to the bottom of it. Do you still have the model laying around and will you be comfortable sharing a scene which exhibits this problem? I am personally focused on fixing problems like this one at the moment.

        I will try to explain what the "parsing vrscene" error means. In many cases V-Ray internally converts your scene to a format which it then uses for the actual rendering. This is the case for Chaos Cloud too. When you submit your scenes to Chaos Cloud they are in this format. When this representation of the scene is written on disk then it is stored in a ".vrscene" file. The error means that this file is incorrect when V-Ray tries to load it for rendering.

        So in the end V-Ray has failed to read a file it created for internal purposes. This is the problem I am trying to fix at the moment.

        Comment

        Working...
        X