Announcement

Collapse
No announcement yet.

"...unreadable render material"

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    "...unreadable render material"

    Hi. A coworker is getting an error message when opening my files on his machine. We are both running 3.0 v1.00 SR1 and Rhino 3 SR5. The message states:

    "(name of file) has an unreadable render material. Do you want to continue reading render materials from this file?"

    If you click yes the message persists. If you click no, you return to Rhino, but there are no objects.

    Any have this problem? Is this a bug?

    Thanks,
    Garrett
    Tags: None
  • #2
    Re: "...unreadable render material"

    is this happening when using a scene file that originates in another version of Rhino? Is V-Ray the only rendering engine you are using? Those are the only things I could think of...that message generally means there is either some kind of a version mistake or some error is happening while loading it.

    If you could send me the file I could verify whether its VfR that is choking on its materials.
    Best regards,
    Joe Bacigalupa
    Developer

    Chaos Group

    Comment

    • #3
      Re: "...unreadable render material"

      Hi Joe. Thanks.

      We are using V-Ray exclusively, though we have a third machine used for modeling which does not have V-Ray installed. It does not have Flamingo installed though I do. I am the only one with Flamingo, but do not use it.

      Run down:
      Computer 1: Vray and Flamingo installed
      Computter 2: Vray installed - error messages
      Computer 3: Rhino modeling only

      The only thing I can think of is that #3 does not have "rh30sr_en_20060331" installed yet. I'll try that now.

      I could send a file, though all files are giving #2 the error now.

      Comment

      • #4
        Re: "...unreadable render material"

        I checked out the file you sent me. When I ran it through Rhino3 I got no error messages although I have Rhino SR5b on my machine...maybe that made the difference?

        When I ran it through Rhino4 I got the following messages passed to my debug window...
        Code:
        openNURBS ERROR # 1 .\mesh_tri.cpp:851 BOGUS INCOMING EDGE
openNURBS ERROR # 2 .\mesh_tri.cpp:851 BOGUS INCOMING EDGE
openNURBS ERROR # 3 .\mesh_tri.cpp:851 BOGUS INCOMING EDGE
openNURBS ERROR # 4 .\mesh_tri.cpp:851 BOGUS INCOMING EDGE
openNURBS ERROR # 5 .\mesh_tri.cpp:851 BOGUS INCOMING EDGE
openNURBS ERROR # 6 .\mesh_tri.cpp:862 BOGUS OUTGOING EDGE
openNURBS ERROR # 7 .\mesh_tri.cpp:851 BOGUS INCOMING EDGE
openNURBS ERROR # 8 .\mesh_tri.cpp:862 BOGUS OUTGOING EDGE
openNURBS ERROR # 9 .\mesh_cul.cpp:565 bin values don't alternate
openNURBS ERROR # 10 .\mesh_cul.cpp:565 bin values don't alternate
openNURBS ERROR # 11 .\mesh_tri.cpp:313 Apex_TestVtx got a vertex below the edge!
openNURBS ERROR # 12 .\mesh_tri.cpp:313 Apex_TestVtx got a vertex below the edge!
openNURBS ERROR # 13 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 14 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 15 .\tl_mesh.cpp:4538 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 16 .\tl_mesh.cpp:4554 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 17 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 18 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 19 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 20 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 21 .\tl_mesh.cpp:4538 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 22 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 23 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 24 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 25 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 26 .\tl_mesh.cpp:4538 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 27 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 28 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 29 .\tl_mesh.cpp:4538 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 30 .\tl_mesh.cpp:4554 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 31 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 32 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 33 .\tl_mesh.cpp:4538 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 34 .\tl_mesh.cpp:4554 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 35 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 36 .\tl_mesh.cpp:4546 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
openNURBS ERROR # 37 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 38 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 39 .\tl_mesh.cpp:4538 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 40 .\tl_mesh.cpp:4530 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 41 .\tl_mesh.cpp:4538 ILLEGAL INPUT: (a0 <= t1 && t1 < t0 && t0 <= a1) failed
openNURBS ERROR # 42 .\tl_mesh.cpp:4554 ILLEGAL INPUT: (a0 <= t0 && t0 < t1 && t1 <= a1) failed
        I am not sure exactly what any of that stuff means - but it appears to be geometry-related. Maybe someone from McNeel could give you further direction on their meaning.

        I guess for now just try grabbing SR5b and see if that helps with your issue.
        Best regards,
        Joe Bacigalupa
        Developer

        Chaos Group

        Comment

        • #5
          Re: &quot;...unreadable render material&quot;

          Yea, those are all geometry errors. Anything relating to OpenNURBS is going to be relating back to the McNeel/Rhino Geometry kernel. It all seams to be mesh related, however, so I would recommend using the SaveSmall command, which should save out just the nurbs information and not the render mesh. My train of thought is that the issue may be relating to the rendermesh itself.
          Damien Alomar<br />Generally Cool Dude

          Comment

          • #6
            Re: &quot;...unreadable render material&quot;

            Thanks guys. I'll look into this. Could be some good news.

            Gotta love "BOGUS INCOMING EDGE".

            Comment

            • #7
              Re: &quot;...unreadable render material&quot;

              I typically save small just to save space. That doesn't fix the problem on the other computer.

              Can you tell me whether or not "unreadable render material" is a Rhino or V-Ray error message? Googling that exact phrase gives me nothing.

              Comment

              • #8
                Re: &quot;...unreadable render material&quot;



                FYI, Here's the error. Sorry it's so small.

                Comment

                • #9
                  Re: &quot;...unreadable render material&quot;

                  Thanks for your help.

                  Conclusion: not a V-Ray issue.

                  Comment

                  Previous template Next
                  Working...
                  X