Announcement

Collapse
No announcement yet.

OBJ model with maps/textures?

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

    OBJ model with maps/textures?

    Can anyone help us get a model exported from Revit 2011 to OBJ format with maps/materials/textures applied?

    We have tried the following steps:

    1. Export to FBX from Revit 2011
    2. Import/link FBX into 3dsMax Design 2011 ( latest FBX plug-in installed )
    3. Save in Max; then export to OBJ ( using various combinations of checkboxes to try to get maps exported.)
    4. Open OBJ in Max; no maps applied. :banghead:

    Any help appreciated.

    ( not telling why we need OBJ as it is "classified" info..........
    Cliff B. Collins
    Registered Architect
    The Lamar Johnson Collaborative Architects, St. Louis, MO
    Autodesk Expert Elite

    #2
    While trying to help Ian getting the Revit file to Octane standalone, I learned that Autodesk Materials are NOT supported in the obj exporter in Max - Only way around it is to convert all the materials to Standard materials within max, prior to exporting to obj. :banghead:

    Believe the process could be rather easy with a 49,- Euro tool like this: Autodesk Material Converter

    Anyone knows of other scripts to convert Autodesk Materials to Standard materials ?
    Klaus Munkholm
    "Do. Or do not. There is no try."

    Comment


      #3
      Further testing shows that maps will even follow the obj, and also be usable in Octane... There must be a easy way to translate Autodesk Materials to Standard Materials, and to preserve the maps etc. at the same time...?

      And Ian, maybe you should kindly ask the Dev. Team at Octane, to make the Max2Octane script support Autodesk Materials? It's a paramount feature for every Revit user who wants to use the Standalone Octane render...
      Klaus Munkholm
      "Do. Or do not. There is no try."

      Comment


        #4
        Getting closer.... Using this script, I've translated all the Autodesk (FBX) Materials (In Max) to standard (Scanline) materials, and exported to OBJ - At a first glance, it sure looks like all the materials are there... Or at least the nodes are... We'll still need to manually apply real Octane materials though.
        Klaus Munkholm
        "Do. Or do not. There is no try."

        Comment


          #5
          Yep--so close, but yet so far. OBJ is an ancient file format leftover from Lightwave days, as I understand it. So it makes sense that the new Adesk/Protein Materials
          which are used in Mental Ray don't play well with OBJ.
          Cliff B. Collins
          Registered Architect
          The Lamar Johnson Collaborative Architects, St. Louis, MO
          Autodesk Expert Elite

          Comment


            #6
            Cliff, if you still need obj files, which I suppose you do for Lumion, I'd highly recommend that you take the above script for a spin... With a little playing around, you'll get beyond "close"
            Klaus Munkholm
            "Do. Or do not. There is no try."

            Comment


              #7
              Nope. Don't need OBJ for Lumion. It has a Revit plug-in which exports Collada files for import into Lumion.

              The OBJ requirement was for a halographic imaging experiment. (seriously!)
              Cliff B. Collins
              Registered Architect
              The Lamar Johnson Collaborative Architects, St. Louis, MO
              Autodesk Expert Elite

              Comment


                #8
                Originally posted by Munkholm View Post
                Getting closer.... Using this script, I've translated all the Autodesk (FBX) Materials (In Max) to standard (Scanline) materials, and exported to OBJ - At a first glance, it sure looks like all the materials are there... Or at least the nodes are... We'll still need to manually apply real Octane materials though.
                The multyconvertor does a very good job at converting all materials in a max scene and applying them to an obj.

                If the program you are using is not CUDA based then it may well be an ideal solution. CUDA based rendering engines such as Iray / Octane have a maximum 64 separate material which can be used in any one scene. My tests of multyconvetor five or six months back hit this limit often when converting the revit files which had been imported into max via fbx.

                Thanks for the reminder though Klaus, I will test again - maybe a judicious bit of editing in Max is all that is needed to make it the best way of getting a revit model to Octane via fbx and max.
                Ian Kidston
                http://allextensions.com.au

                Comment

                Related Topics

                Collapse

                Working...
                X