Announcement

Collapse
No announcement yet.

Mapping changes when inserting file as block

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

  • Mapping changes when inserting file as block

    To present different designs in the same place and setting, I often use a single scene (room with lights) with several linked blocks which I then can turn on an off per layer. I can then work on each of the linked files to adjust designs and so on.

    The trouble is that the placement as well as the size of the texture mapping changes, when I insert the files as blocks. This is quite an issue, since I work with bitmaps simulaitng user interfaces with displays, digits and LED signals.

    I have found a clumsy workaround that is to explode the block, apply new mapping to the objects in question, and then export the revised objects back overwriting the original block file.

    Is there another solution to this or am I missing a point here?

  • #2
    Re: Mapping changes when inserting file as block

    Blocks are a pain. Most of the problem lies within Rhino itself and not V-Ray. We have a few support requests in with McNeel to add more functionality for blocks.

    Comment


    • #3
      Re: Mapping changes when inserting file as block

      Yes, I realise that it is a Rhino related problem, however I could not find a similar forum on the Rhino site - maybe I should try the Rhino newsgroup.

      Comment


      • #4
        Re: Mapping changes when inserting file as block

        I feel your pain. blocks for rendering are currently a no-go. The mapping widget does not move with the block : McNeel should put a developer full time on this mapping issue if you ask me.
        You can contact StudioGijs for 3D visualization and 3D modeling related services and on-site training.

        Comment


        • #5
          Re: Mapping changes when inserting file as block

          Gijs, so it's not a VfR bug? I reported this bug some weeks befor, but so the McNeel team should get it.
          www.simulacrum.de - visualization for designer and architects

          Comment


          • #6
            Re: Mapping changes when inserting file as block

            As far as I can tell, this is a rdk bug. As simple example is a cylinder with a cylindrical map. Make a block out of it, insert it in a file and move the block. Then turn on the map widget and you will see it's at its original location :-\
            You can contact StudioGijs for 3D visualization and 3D modeling related services and on-site training.

            Comment


            • #7
              Re: Mapping changes when inserting file as block

              Yeah, this is an old old rhino problem. We had this same problem with Flamingo as well. It's been this way since blocks first came about.

              When you do get them to render with the occasional Rhino SR, mirroring them causes them to render incorrectly. The list goes on and on. Currently I don't think there are any Rhino Texture Mapping options available for a block until you explode it which defeats the point in having the block to begin with.

              Comment


              • #8
                Re: Mapping changes when inserting file as block

                Workaround: apply mapping -> export as OBJ mesh -> reimport ... the mapping is fixed to the mesh object and ready to use as block. I'm not sure it will work for more than one mapping channel.
                www.simulacrum.de - visualization for designer and architects

                Comment

                Working...
                X