Skip to main content

CLO Help Center

How can we help you?

Issues with importing OBJ from Rhino into CLO3D as Scenes/Props

Comments

  • ottoline

    The object export looks like it may have been set incorrectly within Rhino when they exported it. The base plinth mesh looks very wobbly on the edge corner  ? surface when you compare it to the fbx exports base. That simply should never happen. So I would suggest they try that object format export again and change the default settings in Rhino. Looks like they have triangulated the entire mesh (why?) as it looks like it would be best as quads. 

    Try showing a temporary wire-frame preview in CLO3D of the object model and post that as it's hard to see the quality of their mesh modelling. (import the mesh as an avatar instead of a prop and set the mesh view in the 3D window (avatar) to wireframe so you can post a wireframe screen capture). When you import as prop you won't get a wire-frame view only solids surface view. 

     

    The fbx looks okay so that makes me suspect it's simply an export setup fault when doing the object file from rhino - resolved in a few clicks.

    0
  • drudgls

    Thanks so much for the response. Re the wobby edge corner, sorry I think that was because i resized the image after i screenshotted it. The edges are straight when the OBJ was imported as shown below: 

    I'l ask them to try different export settings to see if that makes a difference. But just wanted to ask you how you show "temporary wire-frame preview" in CLO3D? I couldn't figure out how to do that. Thanks (:

    0
  • ottoline

    You can import the object model as an avatar item instead of a prop > and then select the > avatar view in the 3D window > to render as wireframe.

    0
  • drudgls

    Oh thank you! i tried that and got this:

    0
  • pabloquintana

    What about converting the FBX to the OBJ, given the FBX seems to be correctly exported from Rhino. Plenty of options to do that, for instance Blender.

    0
  • ottoline

    That object file looks like the it wasn't exported correctly from Rhino. It looks like there are some double edges that describe some of the modelling operations (usually boolean cuts do this) on faces for all the arches - so they maybe need to check their export settings when they export the object file so it's clean.

    0
Please sign in to leave a comment.