Announcement

Collapse
No announcement yet.

V-Ray Next crashes during Rhino autosave

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

  • V-Ray Next crashes during Rhino autosave

    Every time Rhino makes a backup, V-ray crashes while rendering in RT.

  • #2
    Thank you for reporting this!
    Could you please provide some additional info?
    • full version number of Rhino
    • OS version
    • list of 3rd-party plugins used (beside V-Ray)
    • confirmation whether the issue occurs only with specific projects or is reproducible even with new scenes
    Kind regards,
    Peter
    Peter Chaushev
    V-Ray for SketchUp | V-Ray for Rhino | Product Specialist
    www.chaos.com

    Comment


    • #3
      Hello,
      Version 5 SR14 64-bit
      (5.14.522.8390, 22/05/2017)

      Win 7 Pro 64
      Maxwell Render not in use.

      It occurs more when working on heavy files.
      When we stop the Render process, V-Ray unloads something and when Rhino makes the autosave in the same time, it crashes without notice.

      BEst,
      Alban

      Comment


      • #4
        Further Problems occured:

        - In V-Ray interactive mode, doing changes in texture mapping(UVW) Vray makes rhino crash.
        - When pausing Int.-Mode, and making UVW changes, then restarting the Int.-Mode Rendering, changes are not applied.
        - Setting the object display mode to rendered does show a black surface instead of the mapped texture.

        I attach some screenshots of the mapping problem.

        Comment


        • #5
          Thank you for your reply! I will look into the mapping issue right away.

          Regarding your initial report, Rhino 5 becomes unresponsive during autosaving and this period depends on the size of the project file. We were not able to reproduce any crash using a variety of heavy scenes.
          Does the crash you described occurs every time during autosave while rendering Interactively or only on certain occasions?
          Furthermore, could you please confirm whether the crash is reproducible while V-Ray is disabled? Simply open a particularly heavy project and use the _Autosave command.

          Kind regards,
          Peter
          Peter Chaushev
          V-Ray for SketchUp | V-Ray for Rhino | Product Specialist
          www.chaos.com

          Comment


          • #6
            Was not able to reproduce the mapping issues. The dark appearance demonstrated in your 3rd screenshot is due to the material's bump map. Our dev team is already onto it.
            To further investigate the crashes you have described we can offer you live assistance. If this is alright, please send me a PM or an email at support@chaosgroup.com with your preferred time and date. My colleagues are available Mon-Fri, between 11:00-18:00 EET (https://www.timeanddate.com/time/zones/eet).

            Kind regards,
            Peter
            Peter Chaushev
            V-Ray for SketchUp | V-Ray for Rhino | Product Specialist
            www.chaos.com

            Comment


            • #7
              We will have to rollback to the previous version of rhino. As different projects on different machines are anything but stable. No support contact from chaosgroup.

              Comment


              • #8
                Hi W_Alban

                I have replied to the support email you have sent us. Please follow-up on it.

                Comment


                • #9
                  Another one for the list.

                  When I copy paste a VRMesh of a Tree that worked fine in 3.6, to a new version of Vray Next, it crashes. If I copy the exact tree as a mesh it is fine.

                  Comment


                  • #10
                    I also had this problem but in the beta version. (autosave crashes)
                    I think it works well now, but maybe it depends on the size of the file you're working on.

                    Best,
                    Krystian

                    Comment


                    • #11
                      the "autosave -> crash" did somehow develop in an "autosave -> restart render progress" in progressive mode. also when I save manually V-Ray restarts rendering. Anyone same problem and solved it?

                      Comment


                      • #12

                        Originally posted by W_Alban View Post
                        Another one for the list.
                        When I copy paste a VRMesh of a Tree that worked fine in 3.6, to a new version of Vray Next, it crashes. If I copy the exact tree as a mesh it is fine.
                        I was informed by our Support team that this only occurs with specific .vrmesh file. Are you able to confirm this?
                        Originally posted by W_Alban View Post
                        the "autosave -> crash" did somehow develop in an "autosave -> restart render progress" in progressive mode. also when I save manually V-Ray restarts rendering. Anyone same problem and solved it?
                        The render process restart upon autosaving is currently being investigated by our developers. We hope to have it fixed soon!

                        Kind regards,
                        Peter

                        Peter Chaushev
                        V-Ray for SketchUp | V-Ray for Rhino | Product Specialist
                        www.chaos.com

                        Comment


                        • #13
                          Same problem here: vray causes rhino to crash during interactive rendering while rhino is autosaving. Costed me half an hour....

                          Comment


                          • #14
                            I'm trialling Next at the moment and have had a couple of occasions where Rhino hangs. It seems to happen when I start an interactive render, I haven't noticed if autosave is involved. Rhino doesn't crash as such, it just won't do anything. Save doesn't work, even trying to Exit doesn't work. I've had to use Windows Task Manager to force Rhino to shut down. The file I'm working on it very simple, just a simple box with a ground plane (I was experimenting with the Metallic shader).

                            Rhino Version 6 SR13 (6.13.19058.371, 27/02/2019), Windows 10 Pro 1803 (17134.706).

                            Comment


                            • #15
                              Iain ,

                              Could you please advise how the rendering was initiated? Are you using the vrayRender or _Render command? Please be informed using Rhino's render command locks the interface and it is expected that if another command is executed, Rhino will be in a non-responsive state.

                              toniboni


                              Could you please advise if you are able to reproduce the issue consistently and whether this happens only with a specific project? Our dev team is interested in scenarios, such as the one you described. If you continuously experience this behavior, you could submit a report to support@chaosgroup.com

                              Comment

                              Working...
                              X