Announcement

Collapse
No announcement yet.

Not able to open rhino file after update

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

  • Not able to open rhino file after update

    Hi,

    this happens several times already. I prepare the project for render, save it and update my Rhino5. Next time I open the project- Rhino crashes.

    The problem comes from Vray

    Luckily my work mate has no Vray installed on her Rhino, so she converts the model for me to Rhino4 version which I can open after and restart my materials and rendering scene settings

    Please take this bug into consideration, it causes big discomfort

    Thank you

  • #2
    I'm not sure I fully understand what you're saying. What do you mean by "update my Rhino5"? Do you mean you're updating Rhino to the latest Rhino 5 beta version? I don't understand how Rhino 4 is involved with this, why does your co-worker need to modify the scene to work with Rhino 4, if you're using Rhino 5? Maybe what you are saying is that you are opening a Rhino 4 scene file, then you modify or save it with Rhino 5, and then you try to open it with Rhino 4 again?
    Best regards,
    Devin Kendig
    Developer

    Chaos Group

    Comment


    • #3
      Hi,

      As you know Rhino5 is still beta version, and frequently new builds are available for download. I tried to explain that few times after updating my Rhino5 Beta, I was not able to open the same file I worked on just before the update.
      There is no way to open the file as Rhino5 crashes.

      The other computer around me has no Vray installed on Rhino5, and it opens the file (which I can't) without any problems.

      This is the problem. Please, let me know how it can be avoid. I hope description is clear enough this time.

      thanks

      Comment


      • #4
        I think what he means,is that after updating rhino 5 beta ,(there is a new beta each week),he can't reopen a drawing that was done in the previous beta.So to solve that he open it ,on a rhino 5 where vray is not installed,and save it as a rhino 4 file to be able to open it again in a rhino5 where vray is installed.
        I had a similar problem,where importing a file, could be only a piece of furniture from my library or anything else that was setup in vray 1.0529,to rhino5 1.5 adv,would make the drawing crash almost every time.When it did not crash ,it would work until I closed Rhino and try to reopen,and it would not.My solution was to do what I explained ,at the top.


        looks familiar to bug report 7840,which Fernando told me is being worked on.

        Renee

        Comment


        • #5
          Renee - case 7840 has been marked resolved and closed. I think we were assuming that you were referring to 1.05.29 rather than an old version of the Rhino 5 beta in that bug report, which was another issue that was resolved.

          We have never seen this behavior as far as I am aware, and without a scene file to reproduce the issue, we will likely never be able to pinpoint the cause of the crash. If anyone has a scene that demonstrates this issue, please send us a bug report and include the scene file. I don't know why upgrading your version of Rhino 5 beta would interfere with our plugin, so I am interested to see what's going on here.

          edit
          I do see another case that is related to being unable to open a scene file, that could potentially be related to this. We believed the issue to be possibly resolved, because we were unable to reproduce it after some changes were made. We were unable to get any users to test out a new beta build that had reported the issue previously, so the bug is still in the pending testing stage. The proposed fix for the issue was added to our build around May 15th, so if you are using a nightly build that was created after that date, and you are encountering this issue, we would like to test whatever scene file is causing you trouble.

          Also, can anyone confirm whether or not the scene files that are having this trouble, were ever touched by our old 1.05.29 plugin, or if they were only created/used in the 1.5 version of our plugin? Knowing whether or not this could potentially be linked to a 1.05.29 upgrade issue, would help us narrow down the cause of this bug a little more.
          Last edited by dkendig; 04-06-2012, 11:17 AM.
          Best regards,
          Devin Kendig
          Developer

          Chaos Group

          Comment


          • #6
            Just sent a file and a bug report # 7946

            Comment


            • #7
              fantastic! That was fast work, much appreciated!
              Best regards,
              Devin Kendig
              Developer

              Chaos Group

              Comment


              • #8
                you are welcome

                Comment

                Working...
                X